by Steven Koonin and Dawn Meredith
Computational Physics is designed to provide direct experience
in the computer modeling of physical systems. Its scope includes
the essential numerical techniques needed to "do physics" on a
computer. Each of these is developed heuristically in the text,
with the aid of simple mathematical illustrations. However, the
real value of the book is in the eight Examples and Projects, where
the reader is guided in applying these techniques to substantial
problems in classical, quantum, or statistical mechanics. These
problems have been chosen to enrich the standard physics curriculum
at the advanced undergraduate or beginning graduate level. The
book will also be useful to physicists, engineers, and chemists
interested in computer modeling and numerical techniques. Although
the user-friendly and fully documented programs are written in
FORTRAN and BASIC, a casual familiarity with any other high-level language,
such as PASCAL, or C, is sufficient.
In late spring 2002, the book will be available in lightening print
mode. To see details about the book, go to
Perseus Books . You cannot order directly on the web, but you may place an
order one of the following three ways:
- over the phone (800.386.5656),
- via email (email@example.com),
- or via fax (720.406.7336 attn Customer Service).
The FORTRAN and BASIC source codes to accompany
Computational Physics Fortran Edition by Koonin and Meredith
can be obtained from this page in zip format.
Click here for FORTRAN source
codes or the BASIC source
codes . The files will automatically be
unzipped by whatever compression/expansion software you have.
Since the zip file is less than 200K in size, unzipping should
be a quick process.
If you do not have expansion software, you can obtain WinZip for Windows or Stuffit Expander
for either Windows and Mac, free on the net. Unix users should
have the command unzip to do the job.
These FORTRAN codes include the graphics subroutines
written in 1990 for graphics on a VAX. While these codes are not
useful as they stand because they rely on an outdated graphing
package, they can serve as templates for codes that interface to
your graphing package.