Reference Data

Download instructions

All tabulated data files are downloaded automatically by running the setup script from the repository root:

bash tools/setup/get_zalmoxis.sh

This invokes tools/setup/setup_zalmoxis.py, which fetches the required data through fwl-io into $FWL_DATA and links each folder of the data/ directory to its dataset. Set FWL_DATA first. See Installation Step 4 of the installation guide for details.

Zalmoxis reads a PALEOS table only when its digest is the one the fwl-io registry pins for its file name and, for a link, also for the name of the file the link points to; names are compared case-insensitively, and a pin that is not an md5 stops the run and names the pin (zalmoxis.eos.registry_guard). A table that differs in its version directory under the current FWL_DATA is fetched again; a table anywhere else that differs, for example an older copy in a real data/ folder or under an earlier FWL_DATA, stops the run with StaleTableError, which names the file, both digests and the refresh command; a table that cannot be read, or a registry that is broken or pins one name twice with different digests, stops it the same way. Without an importable fwl-io no table can be checked, since the manifest says which names are pinned, so every checked read stops with MissingFwlIoError, a StaleTableError that names the file and the pip install of fwl-io. Every Zalmoxis reader of the tables, the export of the SPIDER and Aragog tables included, passes the error on. A table of your own must therefore not carry the file name of a registry table: give it another name and point the EOS entry at it. The binary cache of a unified table x.dat is x.cache.pkl beside it; it holds the md5 of the table it was built from and the identity of the code that built it (the loader source taken at import, or its compiled code when no source is installed, and the numpy and scipy versions), is written in one step and not at all when the table changes while it is read, and is used only when its bytes match their digest and both identities match; any other .pkl file beside a table is not read. Beside a table that cannot be read, a cache whose md5 is the pinned one is used.

Data inventory

The table below lists every data file used by Zalmoxis, organised by subdirectory.

Equation of state tables

Melting curves

Tabulated (downloaded data files):

Analytic (hardcoded, no data files needed):

See configuration guide for usage.

Mass-radius curves

Radial profiles (validation benchmarks)

Seager EOS data

Zalmoxis uses the tabulated equation of state (EOS) data from Seager et al. (2007), providing pressure-density relations for iron (Fe epsilon), silicate (MgSiO3 perovskite), and water ice (ice VII). These tables are automatically downloaded during the setup process described above.

Analytic EOS

The Analytic:<material> EOS options (e.g. Analytic:iron, Analytic:MgSiO3, Analytic:H2O) use the analytic modified polytropic fits from Table 3 of Seager et al. (2007). All fit parameters are hardcoded directly from the paper and do not require any data downloads. This makes the analytic EOS suitable for quick setup, CI environments, or situations where the tabulated data files are not available.

Any EOS name beginning with Analytic: is self-contained. The analytic EOS additionally provides three materials (MgFeSiO3, graphite, SiC) that are not available in the tabulated data.

Mass-radius relations

The following curves serve as reference benchmarks for validating the Zalmoxis internal structure model under both rocky and water-rich configurations:

• Earth-like rocky exoplanets, with a 32.5% Fe + 67.5% MgSiO3 composition, taken from Zeng et al. (2019).

• Water exoplanets, with a 50% Earth-like rocky core (32.5% Fe + 67.5% MgSiO3) and 50% water by mass at 300 K and surface pressure of 1 mbar.