Changes between Version 59 and Version 60 of StellarAtmospheres


Ignore:
Timestamp:
2018-02-08T15:30:24Z (2 weeks ago)
Author:
peter
Comment:

Announce that the TABLE STAR command will work directly on ascii files after C17

Legend:

Unmodified
Added
Removed
Modified
  • StellarAtmospheres

    v59 v60  
    33== Future changes ==
    44
    5 In Cloudy versions up to and including C17, the code was set up in such a way that in order to compile the stellar atmosphere grids they had to reside in the local directory. On the other hand, when you wanted to use the compiled grids, they had to be in the data directory. So either you had to move the compiled files into the data directory, or place the downloaded ascii files in the data directory in the first place. After C17, the rules for searching input files will be the same for all commands, which includes the stellar grids. This means that both during compilation and when using the grids during a run, the files are searched along the entire search path. That implies that during compilation the code will find ascii files in other locations (such as the data directory) as long as they are on the search path. On the other hand, during a run the code will be able to use a compiled atmosphere grid that is stored in the local directory. This gives the user more freedom to organize the files. One example would be compiled grids using a non-standard frequency mesh, which could be stored locally, avoiding a clash with the version using a standard frequency mesh which could be stored elsewhere.
     5In Cloudy versions up to and including C17, the code was set up in such a way that in order to compile the stellar atmosphere grids they had to reside in the local directory. On the other hand, when you wanted to use the compiled grids, they had to be in the data directory. So either you had to move the compiled files into the data directory, or place the downloaded ascii files in the data directory in the first place. After C17, the rules for searching input files will be the same for all commands, which includes the stellar grids. This means that both during compilation and when using the grids during a run, the files are searched along the entire search path. That implies that during compilation the code will find ascii files in other locations (such as the data directory) as long as they are on the search path. On the other hand, during a run the code will be able to use a compiled atmosphere grid that is stored in the local directory. This gives the user more freedom to organize the files.
     6
     7After C17 another important change will take effect. All TABLE STAR commands will work directly on the ascii file and the compiled binary *.mod files will no longer serve any purpose. This implies that the ascii files need to be stored somewhere along the data search path. Compiling ascii files is still supported (albeit optional) and now produces index files with names ending in *.idx. These help speed up reading the ascii files and are strongly recommended for large grids. Note that despite the simple appearance of these files, they are (in principle) still platform dependent. The big advantage of this setup is that there is no longer a dependence on the frequency mesh, so ''you do not need to recompile the ascii grids when you change the frequency mesh''. Compiling grids that are not in the standard Cloudy format (e.g. Starburst99 output) is still mandatory.
    68
    79The page below describes the situation as it exists for C17. The changes described above will take effect once the next major release is available.
     
    33353) 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'''.
    3436
    35 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'''.  You do not need to keep the original ascii files.  However, if the internal format of the mod files is changed in a future Cloudy release, or 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 '''"\
     374) 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 '''"\
    3638m -f *0.1"'''. There may be a great many of them, and they are still contained in the tarballs you downloaded.
    3739
     
    4042== Installing Starburst99 grids ==
    4143
    42 The Starburst99 web page is [http://www.stsci.edu/science/starburst99/ here].  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 [http://data.nublado.org/stars/starburst99.stb99.gz here]. 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'''''. The first file is not strictly needed, but you can keep it around in case you want to create mod files for other platforms, or recompile it with a newer version of Cloudy. To use the Starburst99 grid in a simulation, simply include the command '''''table star "<yourname.mod>" <age>'''''.
     44The Starburst99 web page is [http://www.stsci.edu/science/starburst99/ here].  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 [http://data.nublado.org/stars/starburst99.stb99.gz here]. 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>'''''.
    4345
    4446Use the starburst file by specifying the file name and the log of the age.  An example might be