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
The current Ostrich objects rely on some hard coded templates for the run script. I think we could be quite a bit smarter about this. A vague outline would be that we implement a method, Ostrich.run_script which gets written out when Ostrich.write_config() is called. I think we can accomplish this with the inspect module. We will still require some small template that would look like:
$runScript
if __name__ == '__main__':
$runScriptName($runScriptArgs)
This would allow users to specify much more complex functionality, such as allowing for integration with mizuRoute to do distributed basin routing, use transfer functions to map to parameter values (See #146), or even modify model structure during calibration.
The text was updated successfully, but these errors were encountered:
The current
Ostrich
objects rely on some hard coded templates for the run script. I think we could be quite a bit smarter about this. A vague outline would be that we implement a method,Ostrich.run_script
which gets written out whenOstrich.write_config()
is called. I think we can accomplish this with theinspect
module. We will still require some small template that would look like:This would allow users to specify much more complex functionality, such as allowing for integration with mizuRoute to do distributed basin routing, use transfer functions to map to parameter values (See #146), or even modify model structure during calibration.
The text was updated successfully, but these errors were encountered: