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
It seems that with the separation of the simulation and model aspects in PR #426, some inconsistencies were introduced in the radial1d_model handling, in particular when the legacy_run_simulation is used.
Details
Running the tradis_example interactively in an ipython session using the run_tardis method, the simulation runs smoothly.
The runner now lives within the Simulation class, which is completely fine. However, in view of legacy support and of compatibility of the current radial1d_model layout, the Simulation models should have a methode like lecacy_add_runner, which adds the runner as an attribute to the radial1d_model and also performs all other omitted assignments.
The text was updated successfully, but these errors were encountered:
Summary
It seems that with the separation of the simulation and model aspects in PR #426, some inconsistencies were introduced in the radial1d_model handling, in particular when the legacy_run_simulation is used.
Details
Running the tradis_example interactively in an ipython session using the run_tardis method, the simulation runs smoothly.
However, some features of the radial1d_model do not work properly:
For similar reasons, the to_hdf5 method is also broken:
In addition, the radial1d_model does not have a runner attribute anymore (which is in clear conflict with to_hdf5):
Potential Solution Strategy
The runner now lives within the Simulation class, which is completely fine. However, in view of legacy support and of compatibility of the current radial1d_model layout, the Simulation models should have a methode like
lecacy_add_runner
, which adds the runner as an attribute to the radial1d_model and also performs all other omitted assignments.The text was updated successfully, but these errors were encountered: