Repository navigation
Strange behaviour when no max pacing time specified #14
Description
Kylie observed it only seemed to be running a handful of paces (should default to 10,000 paces). I checked ApPredict executable is behaving fine.
Managed to reproduce her error with the json:
{
"modelId": 1,
"pacingFrequency": 0.5,
"plasmaPoints": [
0,
3,
10,
30,
100
]
}
which is giving voltage_results of
{"success":[{"c":"Concentration(uM)","uv":"UpstrokeVelocity(mV/ms)","pv":"PeakVm(mV)","a50":"APD50(ms)","a90":"APD90(ms)","da90":["delta_APD90(%)"]},
{"c":"0","uv":"350.595","pv":"47.8241","a50":"184.455","a90":"216.892","da90":["0"]},
{"c":"0.001","uv":"351.024","pv":"47.8408","a50":"184.7","a90":"217.155","da90":["0.121071"]},
{"c":"3","uv":"351.389","pv":"47.8557","a50":"184.92","a90":"217.391","da90":["0.22991"]},
{"c":"10","uv":"351.708","pv":"47.8692","a50":"185.12","a90":"217.605","da90":["0.328427"]},
{"c":"30","uv":"351.972","pv":"47.8814","a50":"185.3","a90":"217.798","da90":["0.417461"]},
{"c":"100","uv":"352.204","pv":"47.8923","a50":"185.464","a90":"217.973","da90":["0.497991"]}]}
i.e. increasing APD90 when the first conc should run to steady state and the rest be unchanged.
I tracked this down to ApPredict being passed this argument in the middle of the app-manager STDOUT:
ApPredict args : --pacing-freq 0.5 --pacing-max-time undefined --plasma-concs 0 3 10 30 100 --model 1
so I think the undefined is being read as a strange number by ApPredict.
Desired behaviour - don't pass the option and argument at all if there is no pacingMaxTime in the json
Metadata
Metadata
Assignees
Labels
No labels
Activity