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
We would like to have a standard way to specify patch behavior for the probabilistic sampling experiments, ideally with the following characteristics:
easy to describe (whether it's in a workflow, config file or python)
is patch independent so it can be applied and scaled to an arbitrary number of patches
can use the robust state recovery mechanism used for linear depletion task
Currently under discussion
The state recovery mechanism requires a XML serializable class declaration, which is currently clunky to write in the workflow/c# scripts. We would like something close to a record/named tuple, but unfortunately records are not available in net472, so might be easier to have a common record base class with built-in print functionality and XML serialization abilities that could be used by simply declaring a list of public fields.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Goal
We would like to have a standard way to specify patch behavior for the probabilistic sampling experiments, ideally with the following characteristics:
Currently under discussion
The state recovery mechanism requires a XML serializable class declaration, which is currently clunky to write in the workflow/c# scripts. We would like something close to a record/named tuple, but unfortunately records are not available in
net472
, so might be easier to have a common record base class with built-in print functionality and XML serialization abilities that could be used by simply declaring a list of public fields.Beta Was this translation helpful? Give feedback.
All reactions