... | ... | @@ -38,15 +38,13 @@ This describes the general procedure for setting up an individual stellar SED gr |
|
|
|
|
|
2) Download the files from the individual websites listed below. *It is OK to skip the grids you don't need* (or to skip all of them if you are not going to use stellar atmosphere files at all). Cloudy will work just fine without them as long as you are not explicitly requesting a stellar atmosphere from a missing grid. Some grids are on the original author's web site, while other files are located in the "stars" directory below the main Cloudy
|
|
|
[data site](https://data.nublado.org/).
|
|
|
Links are given at the top of each of the sections describing the grids below. Most files have names that end in ASCII. An example is *ostar2002_p03.ascii* (a file from the Tlusty web site). The downloaded grid files should be stored directly in the data directory. Most files have been compressed with gzip. Explode the ASCII files using the command *"gunzip *.gz"*. If you downloaded any of the Rauch grids, explode the tarballs with *"tar xfz *.tgz"*.
|
|
|
Links are given at the top of each of the sections describing the grids below. Most files have names that end in ASCII. An example is *ostar2002_p03.ascii* (a file from the Tlusty web site). The downloaded grid files should be stored directly in the data directory. Most files have been compressed with gzip. Explode the ASCII files using the command `gunzip *.gz`. If you downloaded any of the Rauch grids, explode the tarballs with `tar xfz *.tgz`.
|
|
|
|
|
|
3) Execute Cloudy with the single command *compile stars* in the data directory containing the downloaded ASCII files. I would do this by first creating a file *compile.in* containing only this command and then running the code as *cloudy.exe -r compile*, which directs its output to *compile.out*.
|
|
|
3) Execute Cloudy with the single command *compile stars* in the data directory containing the downloaded ASCII files. I would do this by first creating a file *compile.in* containing only this command and then running the code as `cloudy.exe -r compile`, which directs its output to *compile.out*.
|
|
|
|
|
|
4) One mod file will be created for each of the downloaded ASCII files.
|
|
|
An example is *ostar2002_p03.mod* which is created from the file *ostar2002_p03.ascii*.
|
|
|
Keep the original ASCII files as you will need them in the next major Cloudy release. If you decide to change the resolution of the Cloudy frequency grid, you will need to recompile the stellar atmosphere files. Alternatively, you can compress the ASCII files after compilation to save disk space. If you downloaded any of the Rauch grids you will probably want to remove the individual SED files with the command
|
|
|
'''"\
|
|
|
m -f *0.1"'''.
|
|
|
Keep the original ASCII files as you will need them in the next major Cloudy release. If you decide to change the resolution of the Cloudy frequency grid, you will need to recompile the stellar atmosphere files. Alternatively, you can compress the ASCII files after compilation to save disk space. If you downloaded any of the Rauch grids you will probably want to remove the individual SED files with the command ```rm -f *0.1```.
|
|
|
There may be a great many of them, and they are still contained in the tarballs you downloaded.
|
|
|
|
|
|
5) You can add grids later (if newer ones become available, or if you change your mind about grids you initially skipped). Download the new files, place them in the data directory and simply go through the same procedure outlined above. Cloudy will skip any grids for which it finds a valid mod file in the data directory (i.e., it will skip any grids that are already compiled).
|
... | ... | |