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
When starting sensitivity analysis in MoBi: parameters are only added to the sensitivity analysis configuration view if they have CanBeVaried=true and are neither table nor categorical.
Sensitivity calculation also additionally filters out parameters with start value=0 (those parameters are not filtered in the configuration view out because the user could change parameter value in the simulation and then the sensitivity would be calculated).
In R, parameters available for sensitivity are defined by:
Thus comparing parameter filter criteria in R vs. MoBi, there is a bunch of additional restrictions in R which define if a parameter can be used in sensitivity calculations:
Parameter value is not zero
Parameter is not defined as read-only
Parameter is constant (➡️ either defined by const value or distributed or the formula was overwritten by a const value)
While the first restriction perfectly makes sense for me: I don't see any reason for the restrictions 2. and 3.
Especially the restriction "Parameter is not defined as read-only" is problematic, because the read-only flag can be changed neither in R nor in MoBi nor in PK-Sim. So if I want to calculate sensitivity for such a parameter - my only chance is to change the flag value in a pkml file (which is errore prone, especially because the flag is a bit field).
So: why do we have those restrictions in R and can we remove them?
The text was updated successfully, but these errors were encountered:
When starting sensitivity analysis in MoBi: parameters are only added to the sensitivity analysis configuration view if they have CanBeVaried=true and are neither table nor categorical.
https://github.com/Open-Systems-Pharmacology/MoBi/blob/7e68545a23f1b4a54ed9389fa146d756ac4a7ab2/src/MoBi.Core/Services/ParameterAnalysableParameterSelector.cs#L6-L13
Sensitivity calculation also additionally filters out parameters with start value=0 (those parameters are not filtered in the configuration view out because the user could change parameter value in the simulation and then the sensitivity would be calculated).
In R, parameters available for sensitivity are defined by:
OSPSuite.Core/src/OSPSuite.R/Mapper/SensitivityAnalysisToCoreSensitivityAnalysisMapper.cs
Lines 56 to 59 in f299281
with
CanUseParameter(parameter)
defined asOSPSuite.Core/src/OSPSuite.R/Services/ParameterAnalysableParameterSelector.cs
Lines 6 to 15 in f299281
and
parameter.IsConstantParameter()
defined asOSPSuite.Core/src/OSPSuite.Core/Domain/ParameterExtensions.cs
Lines 46 to 49 in f299281
Thus comparing parameter filter criteria in R vs. MoBi, there is a bunch of additional restrictions in R which define if a parameter can be used in sensitivity calculations:
While the first restriction perfectly makes sense for me: I don't see any reason for the restrictions 2. and 3.
Especially the restriction "Parameter is not defined as read-only" is problematic, because the read-only flag can be changed neither in R nor in MoBi nor in PK-Sim. So if I want to calculate sensitivity for such a parameter - my only chance is to change the flag value in a pkml file (which is errore prone, especially because the flag is a bit field).
So: why do we have those restrictions in R and can we remove them?
The text was updated successfully, but these errors were encountered: