Instructions are now totally web-based since this insures the most up-to-date advice.
Instructions for downloading the files, and an overview of setting things up, are located at http://nimbus.pa.uky.edu/cloudy/cloudy_94.htm
Next incorporate any hot fixes. Hot fixes are a set of corrections that must be made to the distributed source. They are listed on the hot fixes page of the web site, http://nimbus.pa.uky.edu/cloudy/hotfix.htm . The downloaded source was used to generate the test output on the web site, and did not include these hotfixes.
Compile the code using an ANSI standard C compiler. Instructions are at http://nimbus.pa.uky.edu/Cloudy/setting_up_c94.htm
Set up the stellar atmosphere grids if they will be used. Several sets of stellar atmospheres can be automatically accessed by the code. See Stellar Atmospheres in C94 for more details.
Run the test cases. The code uses extensive self-checking to insure that the results are valid. Many of these tests include assert commands in the input stream or the source code. If anything goes wrong the code will announce this at the end of the calculation. Details are given at the main C94 site, http://nimbus.pa.uky.edu/cloudy/cloudy_94.htm
From the command line the code would be executed as follows, if the executable is called cloudy.exe:
cloudy.exe < input_file > output_file
Commands are read in from the file input_file, and results are sent to output_file A typical input file is the series of commands written one per line in free format:
title typical input stream
blackbody 120,000K
luminosity 37
radius 17
hden 4
Often the most insight is gained from producing a large number of models with various input parameters changing, to see how predicted quantities change. To do this you want to write your own main program, and delete the one that comes with the distribution.
In the distribution this is the file maincl.c. Delete this file (or rename it to something like maincl.old) , and also delete maincl.o if you compiled the entire distribution.
This is done with the compile options described above. You will need to compile all the rest of the code, generating *.o files, then compile the new main program, and link it all together. Note that in C the main program must be called main, but it can live in a file with any name. All of the routines you need to access are declared in the header file cddrive.h. Include this file with your main. That header also describes how the various driving routines should be called.
This file c84.ini contains a series of commands that will make C90 behave more like C84. Initialization files are new to C90. The contents of c84.ini will be entered into the command stream when the command init file=c84.ini is entered. This is described in Part I of Hazy. This file can be placed anywhere on the system if the path is set with the set path command.
This is maintained in the web site, http://nimbus.pa.uky.edu/cloudy/cloudy_94_revision_history.htm . This is a complete history of changes to the active version of the code.
To be placed on the Cloudy mailing list and be notified of updates to the code, please send a request to garyl@cloud9.pa.uky.edu The Cloudy home page http://www.pa.uky.edu/~gary/cloudy also has an option to place yourself on the mailing list. It is important to be on this list and that the current version of the code, with hot fixes included, be used. Anything as complex as Cloudy must contain bugs. These are fixed as soon as they are found.
Please send comments or suggestions to Gary Ferland at gary@cloud9.pa.uky.edu