Repository navigation
Kylie bug fix - #15
Conversation
|
If you could test locally @kwabenantim and check it does sort out #14 that would be great. I have tried and failed, but suspect it is me having a stale docker around or something, as code seems plausible. |
There was a problem hiding this comment.
Pull request overview
This PR addresses Issue #14 by preventing ApPredict from receiving an invalid --pacing-max-time argument when pacingMaxTime is not provided in the input JSON, and updates some user-facing text/copyright headers.
Changes:
- Build
ApPredictCLI args so--pacing-max-timeis only included whenpacingMaxTimeis present. - Improve the invalid-operation error message (spacing + include
STDERR/STDOUT). - Update copyright years in help text and
LICENSE.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| server.js | Avoids passing undefined pacing max time to ApPredict; updates GET operation error messaging. |
| LICENSE | Updates copyright year range. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
|
After the changes, {"success":[{"c":"Concentration(uM)","uv":"UpstrokeVelocity(mV/ms)","pv":"PeakVm(mV)","a50":"APD50(ms)","a90":"APD90(ms)","da90":["delta_APD90(%)"]},
{"c":"0","uv":"350.596","pv":"47.8243","a50":"184.455","a90":"216.892","da90":["0"]},
{"c":"0.001","uv":"351.022","pv":"47.8407","a50":"184.7","a90":"217.155","da90":["0.121071"]}]} |
|
@copilot resolve the merge conflicts in this pull request, keep both the scripts and the engine version |
Resolved the merge conflicts in commit |
|
I don't think this is working yet, but still not convinced. For request.json of I got : which isn't right, there is still a It should basically have zeros in the da90 entries. |
|
@mirams I've now added in a test that rebuilds the image and checks that the args in STDOUT exactly match |
|
Hmmm, what are the full voltage_results with that? |
|
@mirams the CI now prints out the results as well: In the last run, the voltage_results were: |
|
Thanks, I think that's a different simulation, different concs, is it easy for you to test with the request in my comment above? |
|
@mirams The tests are now waiting a bit longer (allowing up to 5m) for the full results to complete. The final |
|
Perfect, that looks fixed. |
To close #14