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
These flags allow the user to specify other files from which pymagicc should read config. They are hugely confusing to use and can cause unexpected behaviour. For our sanity, we should prevent users from using them, instead providing a convenience function load_tuningmodel_cfg which can take a list of tuningmodels and merge them into a config which can then be passed to MAGICC.run. This gets the config blending into Python, where it's simple to debug, and out of the calls to ./magicc, where it's much harder to debug.
These flags allow the user to specify other files from which pymagicc should read config. They are hugely confusing to use and can cause unexpected behaviour. For our sanity, we should prevent users from using them, instead providing a convenience function
load_tuningmodel_cfg
which can take a list of tuningmodels and merge them into a config which can then be passed toMAGICC.run
. This gets the config blending into Python, where it's simple to debug, and out of the calls to./magicc
, where it's much harder to debug.@lewisjared or @znicholls will have a go unless someone else gets there first.
The text was updated successfully, but these errors were encountered: