All:
I have data which looks like this with the line number inserted in ( ).
WSUBJ TIME CP MDV CTIME DAY AMT EVID DV
(1)1 0 0 0 0 1
0.001 1 0.153846
(12)2 0 0 0 0 1
0.001 1 -0.30769
(21)3 0 0 0 0 1
0.001 1 1.076923
I get the following warning with each run.
(DATA WARNING 5) RECORD 1, DATA ITEM 9, CONTENTS 0.1538
THE DV DATA ITEM IS POSITIVE, BUT THE MDV ITEM IS 1
(DATA WARNING 5) RECORD 21, DATA ITEM 9, CONTENTS 1.0769
THE DV DATA ITEM IS POSITIVE, BUT THE MDV ITEM IS 1
Each is a dosing for PD; however, it does not happen for record 12, also a
dosing record. Can someone tell me why, and how to address this issue?
data
Hi,
I'm not sure why the error is only for positive DV, but the error message is
stating that it is only looking for positive (and not nonzero) values.
Since DV is negative on row 12, you're not getting the warning.
More generally for NONMEM, you should have your observations on different
rows than doses. So, all of those rows should have DV set to "." (or
equivalently "0"), and insert a new row with the DV measurement on it for
estimation.
Thanks,
Bill
Quoted reply history
From: [email protected] <[email protected]> On Behalf
Of [email protected]
Sent: Monday, September 5, 2022 10:41 AM
To: [email protected]
Subject: [NMusers] data
All:
I have data which looks like this with the line number inserted in ( ).
WSUBJ TIME CP MDV CTIME DAY AMT EVID DV
(1)1 0 0 0 0 1
0.001 1 0.153846
(12)2 0 0 0 0 1
0.001 1 -0.30769
(21)3 0 0 0 0 1
0.001 1 1.076923
I get the following warning with each run.
(DATA WARNING 5) RECORD 1, DATA ITEM 9, CONTENTS 0.1538
THE DV DATA ITEM IS POSITIVE, BUT THE MDV ITEM IS 1
(DATA WARNING 5) RECORD 21, DATA ITEM 9, CONTENTS 1.0769
THE DV DATA ITEM IS POSITIVE, BUT THE MDV ITEM IS 1
Each is a dosing for PD; however, it does not happen for record 12, also a
dosing record. Can someone tell me why, and how to address this issue?
Hi,
You have non-zero AMT and DV values on the same records.
Simple solution is to separate dosing records from observation records.
W TIME CP MDV CTIME DAY AMT EVID DV
1 0 0 1 0 1 0.001
1 .
1 0 0 0 0 1 .
0 0.153846
Best wishes,
Nick
--
Nick Holford, Professor Emeritus Clinical Pharmacology, MBChB, FRACP
mobile:NZ+64(21)46 23 53 ; FR+33(6)62 32 46 72
email: [email protected]<mailto:[email protected]>
web: http://holford.fmhs.auckland.ac.nz/
Quoted reply history
From: [email protected] <[email protected]> On Behalf Of
[email protected]
Sent: Monday, 5 September 2022 4:41 PM
To: [email protected]
Subject: [NMusers] data
All:
I have data which looks like this with the line number inserted in ( ).
WSUBJ TIME CP MDV CTIME DAY AMT EVID DV
(1)1 0 0 0 0 1
0.001 1 0.153846
(12)2 0 0 0 0 1
0.001 1 -0.30769
(21)3 0 0 0 0 1
0.001 1 1.076923
I get the following warning with each run.
(DATA WARNING 5) RECORD 1, DATA ITEM 9, CONTENTS 0.1538
THE DV DATA ITEM IS POSITIVE, BUT THE MDV ITEM IS 1
(DATA WARNING 5) RECORD 21, DATA ITEM 9, CONTENTS 1.0769
THE DV DATA ITEM IS POSITIVE, BUT THE MDV ITEM IS 1
Each is a dosing for PD; however, it does not happen for record 12, also a
dosing record. Can someone tell me why, and how to address this issue?
Dear Andre,
Since nonmem warns for the same lines as before it is quite clear the nonmem is
reading the old datafile.
Did you update the datafile name in the nonmem control stream?
Or, if you did not change the name of the datafile, are you sure the datafile
is updated on the server where nonmem is running, and not only locally on your
desktop, perhaps?
Best regards
Jakob
Quoted reply history
> On 5 Sep 2022, at 18:28, <[email protected]> <[email protected]>
> wrote:
>
> I sent out this question and got the same response from all which I
> implemented.
> The suggested fix was to separate the dosing from data records.
> However, the warning results make no sense since the DV item is (.).
> However, it is read as 0.15 which is record 2.
> Any explanation and how to fix this?
>
> WSUBJ
> TIME
> CP
> MDV
> CTIME
> DAY
> AMT
> EVID
> DV
> Line(1) 1
> 0
> 0
> 1
> 0
> 1
> 0.001
> 1
> .
> Line(2) 1
> 0
> 0
> 0
> 0
> 1
> .
> 0
> 0.153846
> Line(13)
> 2
> 0
> 0
> 1
> 0
> 1
> 0.001
> 1
> .
> Line (14)
> 2
> 0
> 0
> 0
> 0
> 1
> .
> 0
> -0.30769
> Line(24)
> 3
> 0
> 0
> 1
> 0
> 1
> 0.001
> 1
> .
> Line 25
> 3
> 0
> 0
> 0
> 0
> 1
> .
> 0
> 1.076923
>
>
> (DATA WARNING 5) RECORD 1, DATA ITEM 9, CONTENTS: 0.153846154
> THE DV DATA ITEM IS POSITIVE, BUT THE MDV DATA ITEM IS 1
>
> (DATA WARNING 5) RECORD 21, DATA ITEM 9, CONTENTS: 1.076923077
> THE DV DATA ITEM IS POSITIVE, BUT THE MDV DATA ITEM IS 1
> TRUE LINE 21
> 2 9 6.61 0 9 1 0
> 0 -0.07692
--
*This communication is confidential and is only intended for the use of the
individual or entity to which it is directed. It may contain information
that is privileged and exempt from disclosure under applicable law. If you
are not the intended recipient please notify us immediately. Please do not
copy it or disclose its contents to any other person.*
*Any personal data
will be processed in accordance with Pharmetheus' privacy notice, available
here https://pharmetheus.com/privacy-policy/.**
*
Hi Andre,
It seems like you got the help you needed. I just want to bring to your attention that the R package NMdata provides a function called NMcheckData that can scan a data set for compatibility with Nonmem and additional pitfalls for PK or PK/PD data sets. Admittedly, it would report a finding if MDV=1 and DV<0.
Sometimes the problems occur because the the $INPUT section in the control stream has a different order of columns than the data set. If you pass a control stream as
NMcheckData(file=<path-to-control-stream>)
it will read the data as defined in the control stream, compare to column names (if found) in the input data file, and then turn to checking the data set for nonmem compatibility. So if something weird is going on, that can very often point you to where and why.
Best,
Philip
Quoted reply history
On 9/5/22 10:41, [email protected] wrote:
> All:
>
> I have data which looks like this with the line number inserted in ( ).
>
> WSUBJ TIME CP MDV CTIME DAY AMT EVID DV
>
> (1)1 0 0 0 0 1 0.001 1 0.153846
>
> (12)2 0 0 0 0 1 0.001 1 -0.30769
>
> (21)3 0 0 0 0 1 0.001 1 1.076923
>
> I get the following warning with each run.
>
> (DATA WARNING 5) RECORD 1, DATA ITEM 9, CONTENTS 0.1538
>
> THE DV DATA ITEM IS POSITIVE, BUT THE MDV ITEM IS 1
>
> (DATA WARNING 5) RECORD 21, DATA ITEM 9, CONTENTS 1.0769
>
> THE DV DATA ITEM IS POSITIVE, BUT THE MDV ITEM IS 1
>
> Each is a dosing for PD; however, it does not happen for record 12, also a dosing record. Can someone tell me why, and how to address this issue?