A modular set of synthetic spectral energy distributions for young stellar objects - Robitaille (2017) - v1.1 [Hyperion files]

These are the input and output files for the radiative transfer code (Hyperion) for the model sets presented in

A modular set of synthetic spectral energy distributions for young stellar objects, Robitaille (2017)

Each model set is provided as a single tar file. Each tar file expands to grids-1.1/<set name>, so if you expand all tar files in the same folder, you will end up with a single grids-1.1 folder with 18 sub-folders, one for each model set.

For a given model set, the files are as follows:

• grids-1.1/<set name>/input - input Hyperion files
• grids-1.1/<set name>/log - log files from Hyperion
• grids-1.1/<set name>/output - output Hyperion files
• grids-1.1/<set name>/par - parameters for each model
• grids-1.1/<set name>/ranges.conf - ranges of parameters varied in the model set
• grids-1.1/<set name>/parameters.hdf5 - table of parameters for all models
• grids-1.1/<set name>/d03_5.5_3.0_A_sub.hdf5 - dust file used for the models

Given the large number of models for some of the model sets, the models are not all stored directly inside the par, input, output or log directories - instead these directories contain folders formed from the first two characters (forced to lowercase) of the names of the models they contain. For example, a3 contains all models whose name starts with a3 or A3. This was done to avoid having too many files in a single folder which can cause issues on certain file systems.

For the Hyperion input and output files, in some cases an _sed file is present. In these cases, the output SEDs (and polarization spectra) should be read from the _sed file, not the original output file. This is the case for all models that are in a set for which the ambient medium was present, as described in §4.2.3 of Robitaille (2017). Furthermore, in some cases the SED file is called _sed_noscat to indicate that scattering was not included, as described in §5.1 of Robitaille (2017).

To avoid taking up too much disk space, the Hyperion HDF5 input/output files use external links to refer to each other and to the dust file. To make sure the links work, you should do all operations with the input/output files from the directory containing grids-1.1. For example, to open a Hyperion output file, you would need to do (in Python):

    In [1]: from hyperion.model import ModelOutput

    In [2]: mo = ModelOutput('grids-1.1/s---s-i/output/a3/A3kQmQtj.rtout')

A notebook with examples of reading in the output files can be found here:

https://github.com/hyperion-rt/paper-2017-sed-models/blob/master/notebook_raw/reading_raw_files.ipynb

More information on using Hyperion, including reading input/output files, can also be found at http://docs.hyperion-rt.org

For announcements of new versions of these models, you can subscribe to the following mailing list:

https://groups.google.com/forum/#!forum/protostars

For questions or issues using these models, you can open a GitHub issue in the companion repository:

https://github.com/hyperion-rt/paper-2017-sed-models/issues/new