... | ... | @@ -18,15 +18,16 @@ The page below describes the situation as it exists for C17. The changes describ |
|
|
|
|
|
## Introduction
|
|
|
|
|
|
This page describes how to set up the grids of stellar spectral energy distributions (SEDs) in versions C07 and later of Cloudy. The ability to read in tables of stellar atmospheres was originally introduced into Cloudy by Kevin Volk around 1990. The current versions use [Peter van Hoof](http://homepage.oma.be/pvh/)'s unified treatment with a single code base and many more stellar SEDs. The StellaratmosphereOld page describes the stellar atmospheres used in Cloudy versions C06.02 and before.
|
|
|
This page describes how to set up the grids of stellar spectral energy distributions (SEDs) in versions C07 and later of Cloudy. The ability to read in tables of stellar atmospheres was originally introduced into Cloudy by Kevin Volk around 1990. The current versions use [Peter van Hoof](http://homepage.oma.be/pvh/)'s unified treatment with a single code base and many more stellar SEDs. The [StellaratmosphereOld](StellaratmosphereOld) page describes the stellar atmospheres used in Cloudy versions C06.02 and before.
|
|
|
|
|
|
[Peter van Hoof](http://homepage.oma.be/pvh/) wrote this part of Cloudy and is the maintainer. Please post questions, comments, and suggestions for new stellar atmosphere grids on the [Cloudy discussion board](http://tech.groups.yahoo.com/group/cloudy_simulations/).
|
|
|
[Peter van Hoof](http://homepage.oma.be/pvh/) wrote this part of Cloudy and is the maintainer. Please post questions, comments, and suggestions for new stellar atmosphere grids on the
|
|
|
[Cloudy discussion board](https://cloudyastrophysics.groups.io/g/Main).
|
|
|
|
|
|
This page outlines the general method for setting up individual stellar atmosphere grids. Some of the grids are very large and accessing them as ascii files would be slow. They are "compiled" to create direct access binary files. These files, with names ending in "mod", are the files that Cloudy actually uses. These files are hardware dependent, so if you plan to use the code on more than one platform you may need to create separate binary files for each platform. An important exception would be 32-bit and 64-bit versions of the same hardware, for those platforms the binary files are compatible. Most importantly for IA32 and AMD64/EM64T platforms the binary files are compatible.
|
|
|
This page outlines the general method for setting up individual stellar atmosphere grids. Some of the grids are very large and accessing them as ascii files would be slow. They are "compiled" to create direct access binary files. These files, with names ending in "mod", are the files that Cloudy actually uses. These files are hardware-dependent, so if you plan to use the code on more than one platform you may need to create separate binary files for each platform. An important exception would be 32-bit and 64-bit versions of the same hardware, for those platforms the binary files are compatible. Most importantly for IA32 and AMD64/EM64T platforms, the binary files are compatible.
|
|
|
|
|
|
The following sections describes how to download the original ascii stellar SED files. These files should be placed in the Cloudy data directory.
|
|
|
The following sections describe how to download the original ASCII stellar SED files. These files should be placed in the Cloudy data directory.
|
|
|
|
|
|
Each grid of stellar SEDs, along with a link to the paper or web site describing it, is given below. _If you use one of these grids in a publication it is very important that you properly cite the original paper describing that grid!_ It is intellectually lazy, and deprives the original authors of their proper citation, to simply state that you used an SED that was available in Cloudy.
|
|
|
Each grid of stellar SEDs, along with a link to the paper or web site describing it, is given below. *If you use one of these grids in a publication it is very important that you properly cite the original paper describing that grid!* It is intellectually lazy, and deprives the original authors of their proper citation, to simply state that you used an SED that was available in Cloudy.
|
|
|
|
|
|
|
|
|
## Procedure for setting up a stellar SED grid
|
... | ... | @@ -35,22 +36,30 @@ This describes the general procedure for setting up an individual stellar SED gr |
|
|
|
|
|
1) Cloudy should already have been set up if you got to this page by following the usual steps. I assume you used the recommended directory structure and that the atomic data files are located in a directory *data* and that Cloudy can be run from any directory.
|
|
|
|
|
|
2) Download the files from the individual web sites 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"*.
|
|
|
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"*.
|
|
|
|
|
|
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"'''. There may be a great many of them, and they are still contained in the tarballs you downloaded.
|
|
|
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"'''.
|
|
|
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).
|
|
|
|
|
|
|
|
|
## Installing Starburst99 grids
|
|
|
|
|
|
The Starburst99 web page is [here](http://www.stsci.edu/science/starburst99/). This uses the common code base for stellar atmosphere grids and therefore need to be compiled just like any other grid. The first step is to take the spectrum that was generated by Starburst99 (called *_xxx.spectrum*_) and give it a name that ends in *_.stb99*_. An example of the Starburst99 format that Cloudy expects is given [here](https://data.nublado.org/stars/starburst99.stb99.gz). You can compile the file by giving the single Cloudy command *_compile stars "<yourname.stb99>"*_. You should replace *_<yourname.stb99>*_ by the name you chose and make sure it is surrounded by double quotes (as is always the case when you include filenames in Cloudy input). Cloudy will then create two files: *_yourname.ascii*_ and *_yourname.mod*_. Keep the ascii file as you will need it in the next version of Cloudy. To use the Starburst99 grid in a simulation, simply include the command *_table star "<yourname.mod>" <age>*_.
|
|
|
The Starburst99 web page is [here](http://www.stsci.edu/science/starburst99/). This uses the common code base for stellar atmosphere grids and therefore need to be compiled just like any other grid. The first step is to take the spectrum that was generated by Starburst99 (called *_xxx.spectrum*_) and give it a name that ends in *_.stb99*_. An example of the Starburst99 format that Cloudy expects is given [here](https://data.nublado.org/stars/starburst99.stb99.gz). You can compile the file by giving the single Cloudy command *compile stars "<yourname.stb99>"*. You should replace *<yourname.stb99>* by the name you chose and make sure it is surrounded by double quotes (as is always the case when you include filenames in Cloudy input).
|
|
|
Cloudy will then create two files: *yourname.ascii* and *yourname.mod*. Keep the ASCII file as you will need it in the next version of Cloudy. To use the Starburst99 grid in a simulation, simply include the command *table star "<yourname.mod>" <age>*.
|
|
|
|
|
|
Use the starburst file by specifying the file name and the log of the age. An example might be
|
|
|
`table star "starburst.mod" age 6.7`
|
|
|
Use the starburst file by specifying the file name and the log of the age.
|
|
|
An example might be
|
|
|
*table star "starburst.mod" age 6.7*
|
|
|
The age will have whatever units are in the original Starburst99 file. The default is years.
|
|
|
|
|
|
The procedure for using Starburst99 grids was changed in c07.02. It was a special command in previous versions.
|
... | ... | @@ -58,7 +67,10 @@ The procedure for using Starburst99 grids was changed in c07.02. It was a specia |
|
|
|
|
|
## Installing PopStar grids
|
|
|
|
|
|
The PopStar models can be obtained [here](http://www.fractal-es.com/PopStar/). Click on "Download Models" on the left-hand side, and then you need to download 1 or more of the zip files in the column "Spectra zip file" on the right-hand side. Models are present for different initial mass functions (IMFs) and metallicities (Z). You can choose to convert a single combination of IMF and Z into a 1-dimensional grid allowing interpolation in age, or combine several runs with the _same_ IMF but different Z values into a 2-dimensional grid allowing interpolation in age as well as log(Z) (*note*: the latter option is *only* supported from c10 onwards). The first step is to take an empty (temporary) directory and unzip the files you downloaded in that directory. Next you run the script [convert_popstar.pl](https://data.nublado.org/stars/convert_popstar.pl) (make sure that the file has execute permission) and redirect the output to a file with a name of your choosing ending in *_.ascii*_. An example for a single zip file would be:
|
|
|
The PopStar models can be obtained [here](http://www.fractal-es.com/PopStar/).
|
|
|
Click on "Download Models" on the left-hand side, and then you need to download 1 or more of the zip files in the column "Spectra zip file" on the right-hand side. Models are present for different initial mass functions (IMFs) and metallicities (Z).
|
|
|
You can choose to convert a single combination of IMF and Z into a 1-dimensional grid allowing interpolation in age, or combine several runs with the _same_ IMF but different Z values into a 2-dimensional grid allowing interpolation in age as well as log(Z) (*note*: the latter option is *only* supported from c10 onwards). The first step is to take an empty (temporary) directory and unzip the files you downloaded in that directory. Next, you run the script [convert_popstar.pl](https://data.nublado.org/stars/convert_popstar.pl) (make sure that the file has execute permission) and redirect the output to a file with a name of your choosing ending in *.ascii*.
|
|
|
An example for a single zip file would be:
|
|
|
|
|
|
```
|
|
|
<download sp-sal1-z0200.zip from PopStar website>
|
... | ... | @@ -68,13 +80,13 @@ chmod +x convert_popstar.pl |
|
|
convert_popstar.pl > sp-sal1-z0200.ascii
|
|
|
```
|
|
|
|
|
|
Next you start up the Cloudy executable and type:
|
|
|
Next, you start up the Cloudy executable and type:
|
|
|
|
|
|
```
|
|
|
compile star "sp-sal1-z0200.ascii"
|
|
|
```
|
|
|
|
|
|
This will produce a file "sp-sal1-z0200.mod" which you need to move to your Cloudy data directory. After you have done this, you can delete the temporary directory if you wish. Now the grid can be used as described in the next section. The procedure for a 2-dimensional grid is very similar. You need to download and unzip multiple files, but apart from that the procedure is exactly the same. The conversion script will automatically detect that multiple metallicities are present and will alter the resulting *_.ascii*_ file accordingly. It is not necessary to download all metallicities belonging to a certain IMF, you can also use a subset if you wish. The script will extract the stellar flux *only*.
|
|
|
This will produce a file "sp-sal1-z0200.mod" which you need to move to your Cloudy data directory. After you have done this, you can delete the temporary directory if you wish. Now the grid can be used as described in the next section. The procedure for a 2-dimensional grid is very similar. You need to download and unzip multiple files, but apart from that, the procedure is exactly the same. The conversion script will automatically detect that multiple metallicities are present and will alter the resulting *.ascii* file accordingly. It is not necessary to download all metallicities belonging to a certain IMF, you can also use a subset if you wish. The script will extract the stellar flux *only*.
|
|
|
|
|
|
The PopStar grids are described in [Molla et al. (2009)](http://cdsads.u-strasbg.fr/abs/2009MNRAS.398..451M).
|
|
|
|
... | ... | @@ -101,13 +113,18 @@ BPASSv2_imf135_100_cont_binary.ascii |
|
|
BPASSv2_imf135_100_cont_single.ascii
|
|
|
```
|
|
|
|
|
|
Here "burst" refers to the single starburst models and "cont" to the continuous star formation models as outlined above. Furthermore, "single" refers to the single-star evolution models and "binary" to the binary-star evolution models. The ascii files can be converted into binary files in the usual manner by starting Cloudy and typing
|
|
|
Here "burst" refers to the single starburst models and "cont" to the continuous star formation models as outlined above.
|
|
|
Furthermore, "single" refers to the single-star evolution models and "binary" to the binary-star evolution models.
|
|
|
The ASCII files can be converted into binary files in the usual manner by starting Cloudy and typing
|
|
|
|
|
|
```
|
|
|
compile star "BPASSv2_imf135_100_burst_binary.ascii"
|
|
|
```
|
|
|
|
|
|
and similar for the other three files. After moving the binary files into the data directory, they can then be used in Cloudy. These are 2D grids allowing interpolation in age and metallicity. You can produce a mix of single and binary stars using e.g.:
|
|
|
and similar for the other three files.
|
|
|
After moving the binary files into the data directory, they can then be used in Cloudy.
|
|
|
These are 2D grids allowing interpolation in age and metallicity.
|
|
|
You can produce a mix of single and binary stars using e.g.:
|
|
|
|
|
|
```
|
|
|
table star "BPASSv2_imf135_100_cont_single.mod" 2e8 -1.8
|
... | ... | @@ -132,23 +149,23 @@ This will create two ascii files: |
|
|
BPASSv2p1_imf135_100_burst_single.ascii
|
|
|
BPASSv2p1_imf135_100_burst_binary.ascii
|
|
|
```
|
|
|
As was already mentioned above, continuous star formation files are no longer produced in v2.1, hence only two files are produced instead of four. The remainder of the procedure for using the ascii files is the same as above.
|
|
|
As was already mentioned above, continuous star formation files are no longer produced in v2.1, hence only two files are produced instead of four. The remainder of the procedure for using the ASCII files is the same as above.
|
|
|
|
|
|
This version of the grid is described in [Eldridge et al. (2017)](https://arxiv.org/abs/1710.02154)
|
|
|
|
|
|
|
|
|
## Installing your own grids
|
|
|
|
|
|
It is possible to install your own atmosphere grids. For this you need to create your own ascii file. Instructions for this are included in the file [vanhoof_atmosphere_grids.pdf](../tree/master/trunk/docs/vanhoof_atmosphere_grids.pdf?format=raw) which is also included as Appendix B of Hazy 1 (starting from c10.00). Once you created the ascii file, compiling it and using it is quite similar to Starburst99 files. To compile, issue the command *_compile stars "<yourname.ascii>"*_. To use it, issue the command *_table star "<yourname.mod>" <par1> <par2> ...*_ (the number of parameters here should exactly match the number of parameters you defined in the grid).
|
|
|
It is possible to install your own atmosphere grids. For this you need to create your own ASCII file. Instructions for this are included in the file [vanhoof_atmosphere_grids.pdf](../tree/master/trunk/docs/vanhoof_atmosphere_grids.pdf?format=raw) which is also included as Appendix B of Hazy 1 (starting from c10.00). Once you created the ASCII file, compiling it and using it is quite similar to Starburst99 files. To compile, issue the command *compile stars "<yourname.ascii>"*. To use it, issue the command *table star "<yourname.mod>" <par1> <par2> ...* (the number of parameters here should exactly match the number of parameters you defined in the grid).
|
|
|
|
|
|
|
|
|
## If you don't set up all the stellar SED grids
|
|
|
|
|
|
The Cloudy download includes a large body of test cases that are designed to confirm that the code gets the right answer. Running the test suite is an important part of setting up the code and is described on the TestSuite page.
|
|
|
|
|
|
The test suite includes a number of test cases that are designed to check that the stellar SEDs can be correctly accessed with the *table stars* command. These tests are in the _tsuite/auto_ directory and have names that start with "stars_". The command `ls stars_*.in` will list them all. You would need to download all of the stellar grids for all of the star tests to work.
|
|
|
The test suite includes a number of test cases that are designed to check that the stellar SEDs can be correctly accessed with the *table stars* command. These tests are in the _tsuite/auto_ directory and have names that start with "stars". The command `ls stars\*.in` will list them all. You would need to download all of the stellar grids for all of the star tests to work.
|
|
|
|
|
|
If you decide not to download all of the stellar grids then the _stars_*_ tests that use the missing SEDs will fail. This is *not a problem*, but is a reminder that some of the *_table stars*_ commands will not work.
|
|
|
If you decide not to download all of the stellar grids then the *stars\** tests that use the missing SEDs will fail. This is *not a problem*, but is a reminder that some of the *table stars* commands will not work.
|
|
|
|
|
|
|
|
|
## How to find out which grids you have installed
|
... | ... | @@ -165,11 +182,16 @@ table star wmbasic <Teff> <log(g)> <log(Z)> |
|
|
... <snip> ...
|
|
|
```
|
|
|
|
|
|
This shows that the _Tlusty_ O star 3-dimensional grid has three parameters, the temperature, gravity, and metallicity. The _Werner_ star grid has two parameters (the square brackets indicate that the second parameter is optional), and the _WMbasic_ grid again has three parameters. This output lists all the grids installed on your computer, excluding any grids that you defined yourself (since Cloudy doesn't know the names you gave to those files).
|
|
|
This shows that the _Tlusty_ O star 3-dimensional grid has three parameters, temperature, gravity, and metallicity. The *Werner* star grid has two parameters (the square brackets indicate that the second parameter is optional), and the *WMbasic* grid again has three parameters. This output lists all the grids installed on your computer, excluding any grids that you defined yourself (since Cloudy doesn't know the names you gave to those files).
|
|
|
|
|
|
Starting with Cloudy C17 the output of the *_table star available*_ command will also list several forms of the *_table star hm05*_ and *_table hm12*_ commands. These grids differ in certain aspects from the standard stellar atmosphere grids (e.g., they implicitly set the intensity). But they use the same underlying code infrastructure and the data files are fully compatible with standard stellar atmosphere grids. This is why they are included in the output.
|
|
|
Starting with Cloudy C17 the output of the *table star available* command will also list several forms of the *table star hm05* and *table hm12* commands.
|
|
|
These grids differ in certain aspects from the standard stellar atmosphere grids (e.g., they implicitly set the intensity). But they use the same underlying code infrastructure and the data files are fully compatible with standard stellar atmosphere grids. This is why they are included in the output.
|
|
|
|
|
|
The command *_table star <grid> list*_ will list the models contained in that grid. The parameter *_<grid>*_ should use the same syntax as given in the output from the *_table star available*_ command (without the parameters). An example would be *_table star tlusty Ostar Z+0.3 list*_, which produces (assuming the grid is installed on your computer):
|
|
|
The command *table star <grid> list* will list the models contained in that grid.
|
|
|
The parameter *<grid>* should use the same syntax as given in the output from
|
|
|
the *table star available* command (without the parameters).
|
|
|
An example would be *table star tlusty Ostar Z+0.3 list*,
|
|
|
which produces (assuming the grid is installed on your computer):
|
|
|
|
|
|
```
|
|
|
Teff\lg g| 3.00 3.25 3.50 3.75 4.00 4.25 4.50 4.75
|
... | ... | @@ -188,7 +210,7 @@ Teff\lg g| 3.00 3.25 3.50 3.75 4.00 4.25 4.50 4.75 |
|
|
55000 | -- -- -- -- 66 67 68 69
|
|
|
```
|
|
|
|
|
|
Entries with a number indicate models that are present in the grid. The number is the sequence number in the input file. The command will also work for user-defined grids by supplying the name of the mod file between quotes, e.g. *_table star "usergrid.mod" list*_.
|
|
|
Entries with a number indicate models that are present in the grid. The number is the sequence number in the input file. The command will also work for user-defined grids by supplying the name of the mod file between quotes, e.g. *table star "usergrid.mod" list*.
|
|
|
|
|
|
|
|
|
## Using the grids
|
... | ... | @@ -196,26 +218,30 @@ Entries with a number indicate models that are present in the grid. The number i |
|
|
|
|
|
### Standard grids in Cloudy
|
|
|
|
|
|
The *_table star available*_ command which was explained in the previous section will not only list the available grids on your computer, it will also show the correct syntax to include a stellar atmosphere in your simulation. Parameters between pointed brackets must be replaced by actual numbers. A valid example would be *_table star tlusty Ostar 3-dim 42300 4.22 -0.73*_ to get a Tlusty O-star model with Teff = 42,300 K, log g = 4.22, and log Z = -0.73. Parameters between square brackets may be omitted. This is only the case for the log g parameter in 2-dimensional grids. If it is omitted, it will default to the highest log g available in the grid. Hence the commands *_table star tlusty Ostar Z+0.3 42300 4.75*_ and *_table star tlusty Ostar Z+0.3 42300*_ are both valid and will both produce the exact same model.
|
|
|
The *table star available* command which was explained in the previous section will not only list the available grids on your computer, it will also show the correct syntax to include a stellar atmosphere in your simulation. Parameters between pointed brackets must be replaced by actual numbers. A valid example would be *table star tlusty Ostar 3-dim 42300 4.22 -0.73* to get a Tlusty O-star model with Teff = 42,300 K, log g = 4.22, and log Z = -0.73. Parameters between square brackets may be omitted. This is only the case for the log g parameter in 2-dimensional grids. If it is omitted, it will default to the highest log g available in the grid. Hence the commands *table star tlusty Ostar Z+0.3 42300 4.75* and *table star tlusty Ostar Z+0.3 42300*
|
|
|
are both valid and will both produce the exact same model.
|
|
|
|
|
|
|
|
|
### User-defined grids (including Starburst99 and PopStar grids)
|
|
|
|
|
|
For user-defined grids a slightly different syntax is used to include them in a simulation: *_table star "<yourname.mod>" <par1> <par2> ...*_ The number of parameters supplied must exactly match the number of parameters in the grid. For grids that were generated from Starburst99 output there is only a single parameter: the age. For other grids there may be more, depending on how the grid was defined by the user.
|
|
|
For user-defined grids a slightly different syntax is used to include them in a simulation: *table star "<yourname.mod>" <par1> <par2> ...*
|
|
|
The number of parameters supplied must exactly match the number of parameters in the grid.
|
|
|
For grids that were generated from Starburst99 output, there is only a single parameter:
|
|
|
the age. For other grids, there may be more, depending on how the grid was defined by the user.
|
|
|
|
|
|
|
|
|
## Using ascii files directly
|
|
|
## Using ASCII files directly
|
|
|
|
|
|
We are in the process of removing the need for compiled binary files and allow the code work directly on the ascii files. This work is still in progress, but some of the new functionality is already available. Starting with Cloudy version C17 you can use the command *_table star "<yourname.ascii>" <par1> <par2> ...*_ to interpolate directly on the data in the ascii file and skip the compilation stage. This works well for small grids (roughly 1 to 10 MB in size, depending on the speed of the computer). For large grids we will likely introduce a new (and optional) form of compilation that is independent of the frequency mesh in Cloudy to help speed up the reading process.
|
|
|
We are in the process of removing the need for compiled binary files and allow the code work directly on the ASCII files. This work is still in progress, but some of the new functionality is already available. Starting with Cloudy version C17 you can use the command *table star "<yourname.ascii>" <par1> <par2> ...* to interpolate directly on the data in the ASCII file and skip the compilation stage. This works well for small grids (roughly 1 to 10 MB in size, depending on the speed of the computer). For large grids, we will likely introduce a new (and optional) form of compilation that is independent of the frequency mesh in Cloudy to help speed up the reading process.
|
|
|
|
|
|
Starting with Cloudy C17 we also support the command *_table star "<yourname.ascii>" list*_ to list the contents of an ascii file. All other *_table star*_ commands still require the use of compiled binary files.
|
|
|
Starting with Cloudy C17 we also support the command *table star "<yourname.ascii>" list* to list the contents of an ASCII file. All other *table star* commands still require the use of compiled binary files.
|
|
|
|
|
|
-------
|
|
|
|
|
|
|
|
|
# Details about individual stellar grids
|
|
|
|
|
|
The following subsections describe details of each of the standard grids now in the code. People who wish to install all the available grids should download all the ascii files in our [stars directory](https://data.nublado.org/stars) as well as visit the links shown below in the Tlusty, Rauch, and CoStar sections.
|
|
|
The following subsections describe details of each of the standard grids now in the code. People who wish to install all the available grids should download all the ASCII files in our [stars directory](https://data.nublado.org/stars) as well as visit the links shown below in the Tlusty, Rauch, and CoStar sections.
|
|
|
|
|
|
|
|
|
|
... | ... | @@ -243,7 +269,7 @@ The following subsections describe details of each of the standard grids now in |
|
|
|
|
|
|
|
|
These are the Castelli & Kurucz
|
|
|
([Castelli, F., Kurucz R. L. 2004, astro-ph/0405087](http://cdsads.u-strasbg.fr/cgi-bin/nph-bib_query?bibcode=2004astro.ph..5087C&db_key=PRE&data_type=HTML&format=&high=456aed1c0813147)) LTE, plane-parallel, hydrostatic model atmospheres using the newest opacity distribution functions. The original versions of the files are from the [Kurucz web site](http://kurucz.harvard.edu/grids.html). These grids come in various metallicities, ranging from log Z = +0.5 to -2.5, all with a turbulent velocity of 2 km/s. There is also a single file atlas_3d_odfnew.ascii.gz which contains all metallicities and which enables interpolation in log Z. If you download the latter file, _you do not need any of the other odfnew files_, unless you want to run the entire test suite. *The ODFNEW models are the most up-to-date and preferred versions of the Atlas models.*
|
|
|
([Castelli, F., Kurucz R. L. 2004, astro-ph/0405087](http://cdsads.u-strasbg.fr/cgi-bin/nph-bib_query?bibcode=2004astro.ph..5087C&db_key=PRE&data_type=HTML&format=&high=456aed1c0813147)) LTE, plane-parallel, hydrostatic model atmospheres using the newest opacity distribution functions. The original versions of the files are from the [Kurucz web site](http://kurucz.harvard.edu/grids.html). These grids come in various metallicities, ranging from log Z = +0.5 to -2.5, all with a turbulent velocity of 2 km/s. There is also a single file atlas_3d_odfnew.ascii.gz which contains all metallicities and which enables interpolation in log Z. If you download the latter file, *you do not need any of the other odfnew files*, unless you want to run the entire test suite. *The ODFNEW models are the most up-to-date and preferred versions of the Atlas models.*
|
|
|
|
|
|
|
|
|
|
... | ... | @@ -291,7 +317,7 @@ These are the Castelli & Kurucz |
|
|
[atlas_3d.ascii.gz (all metallicities)](https://data.nublado.org/stars/atlas_3d.ascii.gz)
|
|
|
|
|
|
|
|
|
These are the final versions of the original Kurucz (Kurucz, R.L. 1991, in "Proceedings of the Conference on Precision Photometry: Astrophysics of the Galaxy", Eds. A.G.D. Philip, A.R. Upgren and K.A. Janes. Schenectady, NY: Davis Press, p. 27) LTE, plane-parallel, hydrostatic model atmospheres. The original versions of the files are from the [Kurucz web site](http://kurucz.harvard.edu/grids.html). These grids come in various metallicities, ranging from log Z = +1.0 to -5.0, all with a turbulent velocity of 2 km/s. There is also a single file atlas_3d.ascii.gz which contains all metallicities and which enables interpolation in log Z. If you download the latter file, _you do not need any of the other files_, unless you want to run the entire test suite. These models are included for backward compatibility and also because they cover a larger range of metallicities. The ODFNEW models further up are the most up-to-date and preferred versions of the Atlas models.
|
|
|
These are the final versions of the original Kurucz (Kurucz, R.L. 1991, in "Proceedings of the Conference on Precision Photometry: Astrophysics of the Galaxy", Eds. A.G.D. Philip, A.R. Upgren and K.A. Janes. Schenectady, NY: Davis Press, p. 27) LTE, plane-parallel, hydrostatic model atmospheres. The original versions of the files are from the [Kurucz web site](http://kurucz.harvard.edu/grids.html). These grids come in various metallicities, ranging from log Z = +1.0 to -5.0, all with a turbulent velocity of 2 km/s. There is also a single file atlas_3d.ascii.gz which contains all metallicities and which enables interpolation in log Z. If you download the latter file, *you do not need any of the other files*, unless you want to run the entire test suite. These models are included for backward compatibility and also because they cover a larger range of metallicities. The ODFNEW models further up are the most up-to-date and preferred versions of the Atlas models.
|
|
|
|
|
|
|
|
|
## Tlusty O and B star grids
|
... | ... | @@ -301,13 +327,14 @@ These are the final versions of the original Kurucz (Kurucz, R.L. 1991, in "Proc |
|
|
|
|
|
The [Tlusty](http://tlusty.oca.eu/) code is maintained by Ivan Hubeny & Thierry Lanz. They have produced extensive grids of non-LTE, line-blanketed, plane-parallel, hydrostatic O and B star SEDs. The [_SEDs for Cloudy_](http://tlusty.oca.eu/Tlusty2002/tlusty-frames-cloudy.html) link on their main web site gives links to the files we use.
|
|
|
|
|
|
There are 11 sets of O star SEDs compiled from the [OSTAR2002 grid](http://tlusty.oca.eu/Tlusty2002/tlusty-frames-OS02.html) with names "ostar2002_*.ascii.gz". They are described in the reference [Lanz, T., & Hubeny, I. 2003, ApJS, 146, 417](http://adsabs.harvard.edu/cgi-bin/nph-bib_query?2003ApJS..146..417L&db_key=AST). These SEDs are used by the _stars_ostar2002*.in_ simulations in the test suite.
|
|
|
There are 11 sets of O star SEDs compiled from the [OSTAR2002 grid](http://tlusty.oca.eu/Tlusty2002/tlusty-frames-OS02.html) with names "ostar2002_*.ascii.gz". They are described in the reference [Lanz, T., & Hubeny, I. 2003, ApJS, 146, 417](http://adsabs.harvard.edu/cgi-bin/nph-bib_query?2003ApJS..146..417L&db_key=AST). These SEDs are used by the *stars_ostar2002\*.in* simulations in the test suite.
|
|
|
|
|
|
At the time of this writing the B star grid is still under construction. There are currently 7 sets of B star SEDs compiled from the [BSTAR2006 grid](http://tlusty.oca.eu/Tlusty2002/tlusty-frames-BS06.html) with names _bstar2006_*.ascii.gz_. They are described in the reference [Lanz, T., & Hubeny, I. 2007, ApJS, 169, 83](http://adsabs.harvard.edu/cgi-bin/nph-bib_query?bibcode=2007ApJS..169...83L&db_key=AST&data_type=HTML&format=&high=45d30ec84024291). These SEDs are used by the _stars_bstar2006*.in_ simulations in the test suite.
|
|
|
At the time of this writing, the B star grid is still under construction. There are currently 7 sets of B star SEDs compiled from the [BSTAR2006 grid](http://tlusty.oca.eu/Tlusty2002/tlusty-frames-BS06.html) with names *bstar2006\*.ascii.gz*. They are described in the reference [Lanz, T., & Hubeny, I. 2007, ApJS, 169, 83](http://adsabs.harvard.edu/cgi-bin/nph-bib_query?bibcode=2007ApJS..169...83L&db_key=AST&data_type=HTML&format=&high=45d30ec84024291). These SEDs are used by the *stars_bstar2006\*.in* simulations in the test suite.
|
|
|
|
|
|
Starting with the C10 release of Cloudy, we have added support for merged OSTAR2002/BSTAR2006 grids. The resulting grids have a temperature coverage from 15 to 55 kK. In the overlap region between 27.5 and 30 kK, the BSTAR2006 models have been adopted. The merged grids have been produced for all metallicities supported by the BSTAR2006 grid. They have names _obstar_merged_*.ascii.gz_. When you use one of these grids, you should cite both [Lanz, T., & Hubeny, I. 2003, ApJS, 146, 417](http://adsabs.harvard.edu/cgi-bin/nph-bib_query?2003ApJS..146..417L&db_key=AST) and [Lanz, T., & Hubeny, I. 2007, ApJS, 169, 83](http://adsabs.harvard.edu/cgi-bin/nph-bib_query?bibcode=2007ApJS..169...83L&db_key=AST&data_type=HTML&format=&high=45d30ec84024291). These SEDs are used by the _stars_obstar_merged*.in_ simulations in the test suite.
|
|
|
Starting with the C10 release of Cloudy, we have added support for merged OSTAR2002/BSTAR2006 grids. The resulting grids have a temperature coverage from 15 to 55 kK. In the overlap region between 27.5 and 30 kK, the BSTAR2006 models have been adopted. The merged grids have been produced for all metallicities supported by the BSTAR2006 grid. They have names *obstar\_merged\*.ascii.gz*. When you use one of these grids, you should cite both [Lanz, T., & Hubeny, I. 2003, ApJS, 146, 417](http://adsabs.harvard.edu/cgi-bin/nph-bib_query?2003ApJS..146..417L&db_key=AST) and [Lanz, T., & Hubeny, I. 2007, ApJS, 169, 83](http://adsabs.harvard.edu/cgi-bin/nph-bib_query?bibcode=2007ApJS..169...83L&db_key=AST&data_type=HTML&format=&high=45d30ec84024291).
|
|
|
These SEDs are used by the *stars\_obstar\_merged\*.in* simulations in the test suite.
|
|
|
|
|
|
In general you will not need all the files listed on the Tlusty web site (unless you want to run the entire test suite cleanly) and you will have a couple of choices. If you are only interested in solar metallicity stars then one of the _ostar2002_p00.ascii.gz_, _bstar2006_p00.ascii.gz_ or _obstar_merged_p00.ascii.gz_ files is enough. If you want to interpolate in metallicity you will need one of the _ostar2002_3d.ascii.gz_, _bstar2006_3d.ascii.gz_ or _obstar_merged_3d.ascii.gz_ files, but none of the other ones. If you want to run models at other metallicities, but not interpolate in metallicity, you can choose from the remaining files.
|
|
|
In general, you will not need all the files listed on the Tlusty website (unless you want to run the entire test suite cleanly) and you will have a couple of choices. If you are only interested in solar metallicity stars then one of the _ostar2002_p00.ascii.gz_, _bstar2006_p00.ascii.gz_ or _obstar_merged_p00.ascii.gz_ files is enough. If you want to interpolate in metallicity you will need one of the _ostar2002_3d.ascii.gz_, _bstar2006_3d.ascii.gz_ or _obstar_merged_3d.ascii.gz_ files, but none of the other ones. If you want to run models at other metallicities, but not interpolate in metallicity, you can choose from the remaining files.
|
|
|
|
|
|
|
|
|
## WMbasic O and B stars
|
... | ... | |