CLOUDY version 90 via the web

This is the current version, and this is best accessed via the web through
http://www.pa.uky.edu/~gary/cloudy


                  CLOUDY version 84 via ftp

Cloudy and its documentation live in an anonymous ftp account on 
a Sparcstation, asta.pa.uky.edu, internet number 128.163.160.1.  
Ftp to this machine, and use the id "anonymous" and your e-mail 
address as a password.  Then cd to subdirectory gary, where you 
may find several "read.me" files concerning changes to the code.  
The main files are kept in a subdirectory of gary called c84. 

All of the files in c84 have been compressed and uuencoded.  
These are standard UNIX commands that allow complicated files to 
be sent over the internet.  "Get" the files with the ftp command.  
Next uudecode each of the files. For instance, for the file hazy1 
you would type:

uudecode hazy1

which would create a second file named hazy1.eps.Z.  This file is 
uncompressed by typing

uncompress hazy1.eps

which will create an encapsulated postscript file called 
hazy1.eps.  This can be printed on any postscript printer with 
the standard Adobe fonts and several megabytes of memory.  

There are several main groups of files which should be copied 
from this ftp account.

a)  The FORTRAN source code c84xx.for, where xx are numbers 
indicating the sub-version.  Part III of Hazy describes how 
to compile this file on various computers.  This file will be 
called c84xx in the subdirectory.

b)  The three encapsulated postscript printer files which 
constitute the document Hazy.  These have names like hazyN in 
the subdirectory and expand into files with names like 
hazyN.eps. The number N indicates which of the three parts it 
is.

c)  The set of input files for test cases described in Part III 
of Hazy, contained in the file samples, which expands into 
samples.in.  All of the individual test cases have been 
concatenated together into this file.  Each individual test 
cases is a series of lines ending in a line giving the name 
of that test (i.e., "caseb.in") followed by two lines of 
asterisks.  An editor should be used to write these tests 
into individual files of the same name, and it is a good idea 
to actually run them to confirm that the code gives the same 
answer on you machine as in the output given in Part III of 
Hazy.

d)  The output generated for the test files given in samples.in.  
This is called "output" in the subdirectory, and expands into 
the file "output.prn".  This is a standard ascii file with 
FORTRAN carriage controls, and can be sent to any standard 
line printer.

e)  Two supplemental stellar atmosphere files, kurucz which 
expands into kurucz.asc and werner which expands into 
werner.asc.  These are only needed if realistic stellar 
atmospheres are to be used as part of the ionizing continuum.  
They were adapted for use in CLOUDY by Kevin Volk, who also 
wrote the code within CLOUDY which actually reads these 
files.  The files must be compiled before they can be used by 
Cloudy.  Part III of Hazy describes how to do this.

7)  The description of changes to the current sub-version of the 
code,  These are contained in changes.txt.  This is a plan 
ascii file which is kept in subdirectory gary.


                         PRINTING HAZY
The encapsulated postscript files which constitute HAZY must be 
treated with some care after they are expanded.  The files were 
created by a modern word processor, Word for Windows, and contain 
many embedded equations and figures.  Microsoft has not 
implemented encapsulated postscript in accordance with normal 
conventions.  In particular, many lines within these files are 
profoundly long (several thousand characters).  The files must 
never be edited (they will "break" if you try), and must be 
transferred as binary files after they are expanded.  The three 
hazy files can be printed directly to a postscript printer, with 
the UNIX command "lpr hazyN.eps".

If problems are encountered printing the Hazy documents, the 
usual reason is that the printer has too little memory , or does 
not have the usual Apple Laserwriter fonts.  The printer should 
have at least 2mb of memory, and the basic postscript fonts.  The 
first thing to try if Hazy does not print properly is to find a 
newer printer.  Most postscript printer now sold have far more 
memory and fonts than Hazy needs, but this was not true five 
years ago.  Problems may be encountered with older printers, or 
newer ones with minimal resources.

                        CLOUDY Updates
I correct problems with cloudy as soon as they are discovered.  
There are maintenance releases of the code, which are indicate by 
changes in the letter, or hundredth decimal place, of the code.  
These changes are corrections to the code, and do not involve 
changes to the commands which drive it.  Once you have a copy of 
the code, it is a good idea to check the changes.txt file at 
intervals of 3 to 6 months to see whether you have the current 
version.   When the version changes by a letter or hundredth of 
an integer, then it is only necessary to get a new copy of the 
code (not HAZY;  commands do not change in these maintenance 
releases).