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
Introduce trigger model options in pedestal_model itself
Various options for trigger model
Trigger type (e.g. "prescribed" or "martin" or "metal wall")
the attribute for the "prescribed" model is a timearray Boolean (like set_pedestal now)
For martin or metal_wall is the state-depending scaling
dLH , the time window following a transition (True-->False or False-->True) in which the tped, nped, pped, ramps up or down to or from their nominal value
Set appropriate dynamic_runtime_params based on state at beginning of stepper time interval. This will need to be stateful due to dLH
Include a multiplication factor for the trigger in "martin" or "metal wall" for sensitivity tests
It is recommended that a domain expert carry this out due to the various subtleties
Thank you for your motivation and willingness to contribute.
However, this issue is already assigned and as written we would prefer that a domain expert carry this out since there are some subtleties and considerations to take into account, that would also need dedicated testing where deeper understanding of the simulation time series outputs are important.
The text was updated successfully, but these errors were encountered: