openNCA computation engine is an R package that provides for generation of pharmacokinetic parameter estimates using non-compartmental (NCA) pharmacokinetic analysis methods.
MIT License
27
stars
5
forks
source link
Add specifics of handling DUPLICATE record scenarios in STDOUT messages #290
The openNCA computation engine provides duplicate record handling for the following scenarios (see section Duplicate Record Handling of the Computation Engine Specifications documentation):
Duplicate or replicate input time and concentration records can and do occur in input datasets. The response of the computation engine to two scenarios where this can occur is documented as follows:
When the input Time and Concentration values match exactly for multiple records within a single profile, a warning message will be generated/printed in the output messages. One of the records will be used for parameter generation and parameters for the profile are provided in the output results. Parameters for all other profiles with no duplication are generated in the output results.
When the input Times match exactly for multiple records within a single profile but the Concentration values are different across these records, an error message will be generated/printed in the output messages. No parameter results are generated for the profile where the replicate/duplicate records occur. Parameters for all other profiles with no duplication are generated in the output results.
The error and warning messages generated in the output messages should be updated to include exactly which behavior was detected and exactly which records were impacted and in scenario 1 above, which record was used for parameter generation.
The openNCA computation engine provides duplicate record handling for the following scenarios (see section Duplicate Record Handling of the Computation Engine Specifications documentation):
Duplicate or replicate input time and concentration records can and do occur in input datasets. The response of the computation engine to two scenarios where this can occur is documented as follows:
The error and warning messages generated in the output messages should be updated to include exactly which behavior was detected and exactly which records were impacted and in scenario 1 above, which record was used for parameter generation.