PharmPK Discussion - NONMEM Invalid MDV field error

• On 4 Jul 2011 at 12:26:23, chandramouli Radhakrishnan (rcmoulirc.-at-.gmail.com) sent the message
  

  
  Hi,
  
  This is my Data set when i run nonmem i am getting the following error.  Can someone help me with the error.
  
  Error in NM-TRAN_Execution with run002
  Wings for NONMEM
  C:\nmvi\ver6_20070814\df\std\tr\nmtran.exe run002.ctl
     WARNINGS AND ERRORS (IF ANY) FOR PROBLEM    1
                (WARNING  2) NM-TRAN INFERS THAT THE DATA ARE POPULATION.
  
   (DATA ERROR)      RECORD     6, DATA ITEM  6, CONTENTS: 0.15
   INVALID MDV FIELD.
  
   (DATA ERROR)      RECORD     9, DATA ITEM  6, CONTENTS: 0.15
   INVALID MDV FIELD.
  
   (DATA ERROR)      RECORD    12, DATA ITEM  6, CONTENTS: 0.15
   INVALID MDV FIELD.
  
   (DATA ERROR)      RECORD    15, DATA ITEM  6, CONTENTS: 0.15
   INVALID MDV FIELD.
  
   (DATA ERROR)      RECORD    18, DATA ITEM  6, CONTENTS: 0.13
   INVALID MDV FIELD.
  
   (DATA ERROR)      RECORD    21, DATA ITEM  6, CONTENTS: 0.15
   INVALID MDV FIELD.
  
   (DATA ERROR)      RECORD    24, DATA ITEM  6, CONTENTS: 0.2
   INVALID MDV FIELD.
  
   NM-TRAN TERMINATED ABNORMALLY BECAUSE OF DATA ERRORS.
   PLEASE CORRECT ERRORS AND RE-RUN NM-TRAN.
  Error in NM-TRAN_Execution with run002
  [status]
  Error=NM-TRAN_Execution
  This is my data set
  
  #ASH
  ID      Time    AMT     RATE    DV      MDV     WT      BSA     SEX      Age
  
  1       -20     0       0       .       1       71      1.82    0        26
  
  1       -15     0       0       .       1       71      1.82    0        26
  
  1       -10     0       0       .       1       71      1.82    0        26
  
  1       -5      0       0       .       1       71      1.82    0        26
  
  1       0       0       0       .       1       71      1.82    0        26
  
  1       0.01    0       .       0.15    0       71      1.82    0        26
  
  1       5       150     -2      .       1       71      1.82    0        26
  
  1       10      150     -2      .       1       71      1.82    0        26
  
  1       10.01   150     .       0.15    0       71      1.82    0        26
  
  1       15      150     -2      .       1       71      1.82    0        26
  
  1       20      150     -2      .       1       71      1.82    0        26
  
  1       20.01   150     .       0.15    0       71      1.82    0        26
  
  1       25      150     -2      .       1       71      1.82    0        26
  
  1       30      150     -2      .       1       71      1.82    0        26
  
  1       30.01   150     .       0.15    0       71      1.82    0        26
  
  1       35      150     -2      .       1       71      1.82    0        26
  
  1       40      150     -2      .       1       71      1.82    0        26
  
  1       40.01   150     .       0.13    0       71      1.82    0        26
  
  1       45      150     -2      .       1       71      1.82    0        26
  
  1       50      150     -2      .       1       71      1.82    0        26
  
  1       50.01   150     .       0.15    0       71      1.82    0        26
  
  1       55      150     -2      .       1       71      1.82    0        26
  
  1       60      150     -2      .       1       71      1.82    0        26
  
  1       60.01   150     .       0.2     0       71      1.82    0        26
  
  1       65      150     -2      .       1       71      1.82    0        26
  
  1       70      150     -2      .       1       71      1.82    0        26
  
  -- Kind Regards
  
  Chandramouli Radhakrishnan
  
  

  Back to the Top

• On 4 Jul 2011 at 07:41:38, "Elassaiss - Schaap, J. (Jeroen)" (jeroen.elassaiss-schaap.at.merck.com) sent the message
  

  
  The following message was posted to: PharmPK
  
  Hi Chandramouli,
  
  It seems that labels and columns do mismatch and therefore the MDV label  errornously refers to your DV column, as can be seen from the messages.  Please check your dataset for non-space characters between columns and  check your $DATA statement.
  
  I also noted negative times which are not allowed in nonmem. The time  data item should also be referred to as TIME, otherwise it is not  recognized, from the TIME doc:
  
  ' TIME  labels  PREDPP's  time  (TIME) data item.  The time data item is
  required with PREDPP.  (An exception occurs with ADVAN9 when there are
  only  equilibrium  compartments,  in  which case the time data item is
  optional.)  However, even when PREDPP is not used, a  time  data  item
  has a special meaning to NM-TRAN; see below.
  
  With  PREDPP,  the  time  data  item  gives the time of the event, the
  "event time."  Time data items must be  non-negative.   Event  records
  must  be  ordered  within  an  individual record so that time does not
  decrease, i.e., so that time on any record other  than  the  first  is
  greater than or equal to time on the prior record.  Exceptions are the
  event times of reset and reset-and-dose events, where the time may  be
  any non-negative number.
  '
  
  Best regards,
  Jeroen
  
  J. Elassaiss-Schaap
  Scientist PK/PD MSD
  PO Box 20, 5340 BH Oss, Netherlands
  
  

  Back to the Top

Copyright 1995-2011 David W. A. Bourne (david@boomer.org)