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
Is your feature request related to a problem? Please describe.
Currently, we can only select a time point of interest to do a sensitivity analysis.
However, the Eval contained questions that required analysis of not a fixed timepoint for all samples, but the peak timepoint of each sample (i.e. max per sample). A nice-to-have would be to include a "argmax per sample" option too.
Describe the solution you'd like
Akin to the natural-language interface in "Optimize", the timepoint selection could be:
Consider how sensitive the [select "peak value | peak timepoint | value at timepoint"] [if "value at timepoint", show numeric text field for timepoint] of the outcome(s) of interest [multiselect with filter "state variable or observable"] is to the model parameters [multiselect with filter "model parameters"].
liunelson
changed the title
[FEAT]: Sensitivity analysis in "Simulate" operator should support
[FEAT]: Sensitivity analysis in "Simulate" operator should support other "slice" options besides a specific timepoint
Feb 18, 2025
Is your feature request related to a problem? Please describe.
Currently, we can only select a time point of interest to do a sensitivity analysis.

However, the Eval contained questions that required analysis of not a fixed timepoint for all samples, but the peak timepoint of each sample (i.e.
max
per sample). A nice-to-have would be to include a "argmax
per sample" option too.Describe the solution you'd like
Akin to the natural-language interface in "Optimize", the timepoint selection could be:
Pseudocode
If
value at timepoint
(currently):If
peak value
:If
peak timepoint
:The text was updated successfully, but these errors were encountered: