Cloudy 96 beta 4
Home Up C94.00 Revision history The future etcetera Acknowledgements Contacts, Mailing list Links Site map, search


Compiling C96
C96b4 downloads
Setting the path
Executing C96
Hazy for C96b3
Hotfixes to C96
Problems in C96
C96 revisions
Sample programs
Stars in C96
C96b4 test suite


Note:  The final version should be released towards the end of Spring 2003.

This is a beta of the next version of Cloudy.  Instructions for downloading the source and atomic data, setting up the executable, and compiling the ancillary files, are given on this page.  

Please help by letting me know of problems, differences with previous versions, or suggestions for making the code better, or improving these instructions.

The Cloudy 96 Revision History lists changes that have occurred in the upgrade from C94 to C96.  Corrections to the current source, called hot fixes, are here.

Known problems with this version are described here.

If you have trouble with accessing this site with your browser, you can still get the files by anonymous ftp.  The site is, and you should cd to pub/gary/c96.  Files are in subdirectories located there. gradj is a Linux box so use binary mode ftp transfer mode if you are using a Mac or Windows computer.

Do not bookmark this page if you are looking for the most recent version of Cloudy.  This page, and old versions of the code, will never go away, but will be kept on this web site as part of the record.  The main web page will always have links to both the most recent version of the code and older versions as well.

Setting up this version

  1. Get a copy of Hazy, the documentation for Cloudy.  
  2. Download the current version of the code and data.
  3. Edit path.c to tell the code where the data files live.
  4. Compile the code. 
  5. This explains how to execute the code.  This page shows some examples of calling Cloudy as a subprogram to compute grids of models.
  6. You must compile some stellar data files if you want to use the Atlas, CoStar, and Rauch stellar atmosphere continua.
  7. Run the test suite to confirm that all is well.
  8. Hot Fixes  A set of corrections to the source, which will be incorporated in the next incremental upgrade, are listed in the Hot Fixes page. It is very important that you edit the source to incorporate these Hot Fixes since they correct known problems. The source you obtain here does not have any of these these fixes included. (Reason: this is the source that created the output files that are downloaded with the test suite.  You can validate your system/compiler by confirming that this source reproduces that output.  This source and output constitute a reference for where the code was at a particular time.)

Hit Counter
Last changed 07/21/03.
Return to the Cloudy Home Page.
Copyright 1978-2003 Gary J. Ferland