openNCA computation engine is an R package that provides for generation of pharmacokinetic parameter estimates using non-compartmental (NCA) pharmacokinetic analysis methods.
Tested with commit c3d3f48 , FLGTIME doesn't switch the selected mct$TIME to the alternate time as documented in the openNCA Computation Engine specifications document.
All testcase materials are stored on a onedrive folder.
The testcase that probes the behavior for 8 sub testcases is tc1908. The sub cases are as follows:
Testcase1: execute with mct$TIME==NOMINAL using existing incorrect FLGTIME coding as “ACTUAL/NOMINAL” with no FLGTIME modifications
Testcase2: execute with mct$TIME==ACTUAL using existing incorrect FLGTIME coding as “ACTUAL/NOMINAL” with no FLGTIME modifications
Testcase3: execute with mct$TIME==NOMINAL using existing incorrect FLGTIME coding as “ACTUAL/NOMINAL” with selected data records with FLGTIME set as “ACTUAL” rather than nominal
Testcase4: execute with mct$TIME==ACTUAL using existing incorrect FLGTIME coding as “ACTUAL/NOMINAL” with selected data records with FLGTIME set as “NOMINAL” rather than actual
Testcase5: execute with mct$TIME==NOMINAL using the correct FLGTIME coding as “0 – use MCT$TIME variable”/”1 – use alternate time” with no FLGTIME modifications
Testcase6: execute with mct$TIME==ACTUAL using existing incorrect FLGTIME coding as “0 – use MCT$TIME variable”/” 1 – use alternate time” with no FLGTIME modifications
Testcase7: execute with mct$TIME==NOMINAL using existing incorrect FLGTIME coding as “0 – use MCT$TIME variable”/” 1 – use alternate time” with selected data records with FLGTIME set as “1” pointing to ACTUAL rather than NOMINAL
Testcase8: execute with mct$TIME==ACTUAL using existing incorrect FLGTIME coding as “0 – use MCT$TIME variable”/” 1 – use alternate time” with selected data records with FLGTIME set as “1” pointing to NOMINAL rather than ACTUAL
In testcases, 3,4,7,8 , referring to CONCTIME values, there’s no switch as requested to the alternate time on a record by record basis.
Tested with commit c3d3f48 , FLGTIME doesn't switch the selected mct$TIME to the alternate time as documented in the openNCA Computation Engine specifications document.
All testcase materials are stored on a onedrive folder.
The testcase that probes the behavior for 8 sub testcases is tc1908. The sub cases are as follows:
Testcase1: execute with mct$TIME==NOMINAL using existing incorrect FLGTIME coding as “ACTUAL/NOMINAL” with no FLGTIME modifications
Testcase2: execute with mct$TIME==ACTUAL using existing incorrect FLGTIME coding as “ACTUAL/NOMINAL” with no FLGTIME modifications
Testcase3: execute with mct$TIME==NOMINAL using existing incorrect FLGTIME coding as “ACTUAL/NOMINAL” with selected data records with FLGTIME set as “ACTUAL” rather than nominal
Testcase4: execute with mct$TIME==ACTUAL using existing incorrect FLGTIME coding as “ACTUAL/NOMINAL” with selected data records with FLGTIME set as “NOMINAL” rather than actual
Testcase5: execute with mct$TIME==NOMINAL using the correct FLGTIME coding as “0 – use MCT$TIME variable”/”1 – use alternate time” with no FLGTIME modifications
Testcase6: execute with mct$TIME==ACTUAL using existing incorrect FLGTIME coding as “0 – use MCT$TIME variable”/” 1 – use alternate time” with no FLGTIME modifications
Testcase7: execute with mct$TIME==NOMINAL using existing incorrect FLGTIME coding as “0 – use MCT$TIME variable”/” 1 – use alternate time” with selected data records with FLGTIME set as “1” pointing to ACTUAL rather than NOMINAL
Testcase8: execute with mct$TIME==ACTUAL using existing incorrect FLGTIME coding as “0 – use MCT$TIME variable”/” 1 – use alternate time” with selected data records with FLGTIME set as “1” pointing to NOMINAL rather than ACTUAL
In testcases, 3,4,7,8 , referring to CONCTIME values, there’s no switch as requested to the alternate time on a record by record basis.
An example from sub testcase8 is as follows: