From: mark.e.sale@GSK.com
Subject: Re: [NMusers] Any way to change the maximum input data item no.?
Date: Date: Thu, 11 Aug 2005
Two solutions, you can use continuation lines, as described in the guide:
-------------------------------------------------------------------
| |
| CONT DATA ITEM |
| |
------------------------------------------------------------------
MEANING: Continuation (CONT) data item for PREDPP
CONTEXT: $INPUT record and NONMEM data set
USAGE:
$INPUT ... CONT ...
DISCUSSION:
CONT labels PREDPP's continuation (CONT) data item. The continuation
data item is optional. The CONT data item allows a PREDPP event
record to span several data records. It is useful when more than 20
data items are needed to describe a single event. When the CONT data
item is not defined on the $INPUT record, every event record consists
of a single data record.
Values are:
0 This is the last or only data record of the event record.
1 This and the succeeding record are both members of the same event
record. MDV must be 1.
PREDPP ignores records having CONT=1, except to pass them to the PK
and ERROR routines as part of the complete event record. Values of
PREDPP data items such as EVID, AMT, etc., are significant only on the
final record of each event record, i.e., on records having CONT=0.
With NM-TRAN abbreviated code, values on data records having CONT=1
are not available for use as right-hand quantities, i.e., abbreviated
code cannot reference the values in data records other than the last
of each event record. (It would be possible to reference such values
using verbatim code, however). When NM-TRAN performs time translation
or ii conversion (see date, time, ii), it does so only for the event
records having CONT=0.
REFERENCES: Guide VI, section II (p. 5), V.A (p. 55), V.I (p. 62)
REFERENCES: Guide IV, section V.B (p. 61), V.C.5 (p. 70)
Or, you can write additional data to a seperate file and read it in from verbatum code in $PK.
If you want to read it in from a separate file, let me know I'll send the code.
GO BUCKS (BS OSU, 1981, MD OSU, 1985)
Mark Sale M.D.
Global Director, Research Modeling and Simulation
GlaxoSmithKline
919-483-1808
Mobile
919-522-6668
Any way to change the maximum input data item no.?
From: Sam Liao sliao@pharmaxresearch.com
Subject: Re: [NMusers] Any way to change the maximum input data item no.?
Date: Thu, 11 Aug 2005 10:30:38 -0400
Dear Mark:
Do you mind sharing the verbatum code in $PK to read a separate file?
What platform this code is working? UNIX or PC?
Best regards,
Sam Liao
Pharmax Research
From: Sam Liao sliao@pharmaxresearch.com
Subject: Re: [NMusers] Any way to change the maximum input data item no.?
Date: Thu, 11 Aug 2005 11:52:00 -0400
Dear Mark:
Thanks a lot for your quick response. It can be very useful program for me.
The complication is that I need to read additional items for every observation records.
Best regards,
Sam
From: mark.e.sale@gsk.com
Subject: Re: [NMusers] Any way to change the maximum input data item no.?
Date: Thu, 11 Aug 2005 12:03:41 -0400
Can be done in the same way. Try setting up the data file and the "extra
data" file with a unique number for every observation or event, rather
than every subject, them use that number for search the array, rather than
the ID. You'll have to call PK with every observation or event (using
CALLFL = -2 or -1), then call get_sub with every call to PK (as it is
now). I don't know if NMTRAN/NONMEM would set CALLFL correctly, that is
if it would look inside the verbatim code to see if PK must be called with
every event, so I'd probably just go ahead and force a call to PK with
every observation or event. I can't claim to understand the logic that
NONMEM uses to decide when to call PK.
Mark Sale M.D.
Global Director, Research Modeling and Simulation
GlaxoSmithKline
919-483-1808
Mobile
919-522-6668
_______________________________________________________