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
Update - PR #339 implements a results_handle.get_state() method.
Call to get_parameter() is still outstanding.
A call to results_handle.get_data() should enable access to scenario data from a decision module.
Blocks nismod/nismod2#53 as digital comms decision module requires access to adoption scenario data, based on strategy chosen.
Above no longer correct as get_results can be used to obtain information from output of model, but it would be very useful if the decision module has access to parameters though a result_handle.get_parameter() method
Update digital comms wrapper
To do:
- smif decision module access to scenario data - see nismod/smif#328
- nismod digital_comms adoption scenario data provision from FTP -
willu47
changed the title
decisions: decisionmodule should have access to scenario data
decisions: decision module should have access to parameters and previous_state
Mar 27, 2019
willu47
changed the title
decisions: decision module should have access to parameters and previous_state
decisions: decision module should have access to parameters
Apr 8, 2019
Update - PR #339 implements a results_handle.get_state() method.
Call to get_parameter() is still outstanding.
results_handle.get_data()
should enable access to scenario data from a decision module.Blocks nismod/nismod2#53 as digital comms decision module requires access to adoption scenario data, based on strategy chosen.Above no longer correct as get_results can be used to obtain information from output of model, but it would be very useful if the decision module has access to parameters though a
result_handle.get_parameter()
methodSee also #333
The text was updated successfully, but these errors were encountered: