-
Notifications
You must be signed in to change notification settings - Fork 3
ExoTETHyS FAQ
We report here the answers to some of the frequently asked questions from the users of ExoTETHyS.
If you cannot find the answer to your question, do not hesitate to raise an issue or to contact by e-mail giuseppe.morello.11@ucl.ac.uk.
The answer depends mainly on the wavelength range of interest, and on the stellar parameters.
The MPS_Atlas_set1_2023 and MPS_Atlas_set2_2023 grids, along with Atlas_2000, have the broadest coverage in wavelength and stellar parameters. The MPS_Atlas grids have been optimized to match solar observations. Recent measurements of empirical limb-darkening on FGK stars from TESS and Kepler observations are in good agreement with these models (Maxted 2023).
The Atlas_2000 grid enables calculations for the hottest stars.
The Phoenix_2012_13 and Phoenix_drift_2012 enable calculations for the coolest stars. In particular, Phoenix_2012_13 contains model spectra of stars with effective temperatures between 3000 K and 10000 K, while Phoenix_drift_2012 is for M dwarfs with temperatures between 1500 K and 3000 K. Phoenix_2018 is more up to date, but it covers up to 2.6 micron.
The Stagger_2018 relies on fully 3D hydrodynamic models and contains spectra between 0.1 and 20 micron for stars with effective temperatures between 4000 K and 7000 K. It is an extension of the older Stagger_2015 grid, which covers a smaller wavelength range. The Stagger perform similar or better than MPS_Atlas grids on empirical measurements from TESS and Kepler (Maxted 2023), but the Stagger ones cover a smaller temperature range with a coarse sampling.
| Grid Name | Geometry | Teff (K) | log(g) | [M/H] | Lambda (micron) | Refs |
|---|---|---|---|---|---|---|
| Phoenix_2012_13 | S1 | 3000 - 10000 | 0.0 - 6.0 | 0.0 | 0.25 - 10 | Cl12 , Cl13 |
| Phoenix_drift_2012 | S1 | 1500 - 3000 | 2.5 - 5.5 | 0.0 | 0.001 - 950 | Cl12 |
| Phoenix_2018 | S1 | 2300 - 12000 | 0.0 - 6.0 | 0.0 | 0.05 - 2.6 | Cl18 |
| Atlas_2000 | P-P | 3500 - 50000 | 0.0 - 5.0 | -5.0 - 1.0 | 0.009 - 160 | Cl00 |
| Stagger_2018 | S3 | 4000 - 7000 | 1.5 - 5.0 | -2.0 - 0.5 | 0.1 - 20 | Ch18 |
| Stagger_2015 | S3 | 4000 - 7000 | 1.5 - 5.0 | -2.0 - 0.5 | 0.2 - 1 | Ma15 |
| MPS_Atlas_set1_2023 | P-P | 3500 - 9000 | 3.0 - 5.0 | -5.0 - 1.5 | 0.009 - 160 | Ko23 |
| MPS_Atlas_set2_2023 | P-P | 3500 - 9000 | 3.0 - 5.0 | -5.0 - 1.5 | 0.009 - 160 | Ko23 |
I have got an error ending with urllib.error.ContentTooShortError: <urlopen error retrieval incomplete: got only number1 out of number2 bytes>. Why did it happen?
The run failed to download a file from the online database. It was the latest file for which it appeared the message Downloading... filename.pickle.
You should remove this file from your local database using the subpackage manage_database, then try to repeat the same run. If the problem persists, most likely due to poor internet connection or some security settings, you can ask the models that you need by e-mail giuseppe.morello.11@ucl.ac.uk.
I have got an error ending with _pickle.UnpicklingError: pickle data was truncated. Why did it happen?
One of the files in your local database is corrupted, most likely because of issues during its download during a previous run. It is the latest file for which it appeared the message File already here... filename.pickle. You should remove this file from the database using the subpackage manage_database, then try to repeat the same run.