You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
History and profiles are the basic output types for all MESA models, and HDF5 options for these would enable storing data far more efficiently. I imagine many users have existing workflows that would be disrupted, so we would likely want to continue to support the current plain text output files as default, at least initially. We could start by hiding an HDF5 option for this output behind an inlist flag that defaults to false.
use_hdf5_for_output_data = .false.
We would also likely want to distribute lightweight python tooling analogous to py_mesa_reader so that users can easily load their MESA output into python analysis scripts for postprocessing. The goal should be to make this seamless enough that the average user running models and making plots with python doesn't have to think at all about the underlying HDF5 format of the data.
The text was updated successfully, but these errors were encountered:
History and profiles are the basic output types for all MESA models, and HDF5 options for these would enable storing data far more efficiently. I imagine many users have existing workflows that would be disrupted, so we would likely want to continue to support the current plain text output files as default, at least initially. We could start by hiding an HDF5 option for this output behind an inlist flag that defaults to false.
We would also likely want to distribute lightweight python tooling analogous to
py_mesa_reader
so that users can easily load their MESA output into python analysis scripts for postprocessing. The goal should be to make this seamless enough that the average user running models and making plots with python doesn't have to think at all about the underlying HDF5 format of the data.The text was updated successfully, but these errors were encountered: