Closed abdullahhamadeh closed 3 years ago
Did you use version 10 of the QualiRunner? https://ci.appveyor.com/project/open-systems-pharmacology-ci/QualificationRunner/build/artifacts
I am able to generate the files with v9 but v10 is failing
I also can't see the log files that are referred to in the error message
moving the issue to the QualiRunner-Repo
Can you show me how you are calling the runnner? And which files are you using? I need to be able to reproduce
'C:/path/to/QualificationRunner 10.0.40/QualificationRunner.exe' -i 'C:/path/to/Qualification-DDI-CYP2C19-main/Qualification/Input/qualification_plan.json' -o 'C:/path/to/reporting engine input/' -p 'C:/Program Files/Open Systems Pharmacology/PK-Sim 9.1/'
ok you are mixing v9 of PKSim and v10 of runner. Please install the latest portable version of PKSim and try again
https://ci.appveyor.com/project/open-systems-pharmacology-ci/pk-sim/build/artifacts
using v10 of pksim I am getting what we expect
@Yuri05 For the moment, PKSim is still running the simulation. I am going to make it optional (default true) so that we can turn that off (compatible with current Matlab reporting engine). Then when we have completely migrated to R, we can set the default to true?
Or is it ok to set the default to run = FALSE (and then we can just update the call in the matlarb reporting engine). I would prefer this solution. Let me know
@msevestre can you pls point me to v10 of pksim? I see only v9.1 here
oops, I need better glasses
maybe you just need glasses :)
beware. At the moment, it is also calculating the simulation which is not what you want. I am adding an option to the runner to turn that off. So once you are done with generating the pkml etc.. you should deleted all csv results files
I am going to make it optional (default true) so that we can turn that off (compatible with current Matlab reporting engine). Then when we have completely migrated to R, we can set the default to true?
Would prefer this option for now. No need for the new version of Matlab-RE then and no unexpected side effects due to the change of the default :)
see PR. Not possible with flag. So we need to update the code in reporting engine and add the -r flag
V10 TODO list grows...
LEt me see if I can declare the flag as nullable to catch when it's not set...and then say it's true
ok I can't. But I'll create another termp flag "noRun" which by default will be false. Setting --norun will switch it to true
All right. There is the flag --norun that will make sure we do not run the simulation. I am going to add it to the call in the new reporting engine
Only XML files are generated in the reporting engine input folder