Dear Andreas,
Isn't the limit you're referring to the maximum amount of etas/thetas, these
can be adjusted (see: http://www.icondevsolutions.com/nonmem_tip20.htm )
As far as I known the amount of data items can not be adjusted. If some of them
are not in use, you can use the DROP data item. The complete column will be
removed in the analysis.
" If DROP (or SKIP) is used as a data item label or synonym, the data
item type will not appear in the NONMEM data set. DROP (or SKIP) may
be used with more than one item."
Cheers,
Rob
_______________________________
Rob ter Heine, MSc, PharmD
Department of Pharmacology, Slotervaart Hospital
Amsterdam, The Netherlands
E: [email protected]
T: +31-20-5124737
>>> <[email protected]> 03/16/09 2:43 >>>
I am looking for a solution to get around the limit of 20 input variables
in nonmem.
The message you get with more than 20 variables in $INPUT is this:
16 $INPUT: NO. OF DATA ITEMS EXCEEDS 20.
STOP 4 statement executed
I did not find anything in the archives or on the Web. I recall having
successfully done that in nonmem V, and I think it was about changing the
value of 20 to another value in a few files.
My original naive idea was that this was just a single change to the SIZES
file in nm VI but that seems to not be the case.
To keep the discussion focused, I am not looking for workarounds like
solutions with concatenated values and an indicator variable.
For a change I am trying to get the software to adapt to the user's needs
instead of the usual opposite situation.
Thanks for any pointers.
Andreas
-----
Andreas Krause, PhD
Lead Scientist Modeling and Simulation
Actelion Pharmaceuticals Ltd
Gewerbestrasse 16
CH-4123 Allschwil
Switzerland
The information of this email and in any file transmitted with it is strictly
confidential and may be legally privileged.
It is intended solely for the addressee. If you are not the intended recipient,
any copying, distribution or any other use of this email is prohibited and may
be unlawful. In such case, you should please notify the sender immediately and
destroy this email.
The content of this email is not legally binding unless confirmed by letter.
Any views expressed in this message are those of the individual sender, except
where the message states otherwise and the sender is authorised to state them
to be the views of the sender's company. For further information about Actelion
please see our website at http://www.actelion.com
Betr.: 20 variable limit in $INPUT
Andreas,
Some months ago I spent a few hours investigating this same problem. Below are
my notes. Currently I use the last approach (which is actually a workaround,
sorry...), that will hopefully be redundant when NM7 arrives,
best regards,
Ron
approaches for using more covariates in dataset:
* using CONT method ( http://www.cognigencorp.com/nonmem/nm/99aug272005.html):
- Pro: easy using PsN to generate the splitted dataset
- Con: Could get it to work only in NMV, not in NMVI (reason unknown, with and
without PsN). poorly documented in NM. Needs ID CONT DV and MDV as the first
columns on each row.
* using Fortran script ( http://www.cognigencorp.com/nonmem/nm/99mar232005.html)
- Pro: in theory neat method, separate dataset for covariates.
- Con: gave problems with g77 compiler, but works with df. Needs adaptation for
time-changing covariates.
* row-wise incorporation in dataset using EVID=2 events.
- Pro: solves problems with above methods... Unlimited amount of covariates.
- Con: can make datasets much bigger (=slower?) when lot of covariates included
(however, in NM6 easily switch on/off reading of covariates using IGNORE=...).
May need extra code to avoid numerical difficulties for covariates that define
states at t=0.
RJ Keizer, PharmD
Department of Pharmacy & Pharmacology
Slotervaart Hospital / The Netherlands Cancer Institute
Louwesweg 6, 1066 EC Amsterdam, The Netherlands
Phone: +31205124662
>>> <[email protected]> 03/16/09 2:43 nm >>>
I am looking for a solution to get around the limit of 20 input variables
in nonmem.
The message you get with more than 20 variables in $INPUT is this:
16 $INPUT: NO. OF DATA ITEMS EXCEEDS 20.
STOP 4 statement executed
I did not find anything in the archives or on the Web. I recall having
successfully done that in nonmem V, and I think it was about changing the
value of 20 to another value in a few files.
My original naive idea was that this was just a single change to the SIZES
file in nm VI but that seems to not be the case.
To keep the discussion focused, I am not looking for workarounds like
solutions with concatenated values and an indicator variable.
For a change I am trying to get the software to adapt to the user's needs
instead of the usual opposite situation.
Thanks for any pointers.
Andreas
-----
Andreas Krause, PhD
Lead Scientist Modeling and Simulation
Actelion Pharmaceuticals Ltd
Gewerbestrasse 16
CH-4123 Allschwil
Switzerland
The information of this email and in any file transmitted with it is strictly
confidential and may be legally privileged.
It is intended solely for the addressee. If you are not the intended recipient,
any copying, distribution or any other use of this email is prohibited and may
be unlawful. In such case, you should please notify the sender immediately and
destroy this email.
The content of this email is not legally binding unless confirmed by letter.
Any views expressed in this message are those of the individual sender, except
where the message states otherwise and the sender is authorised to state them
to be the views of the sender's company. For further information about Actelion
please see our website at http://www.actelion.com
Hi Ron,
Thanks for your summary.
In my case, it always shows an error that DV is positive and MDV is 1.
Maybe this indicates that in NMVI a new rule to check DV and MDV have been
added. The problem could be solved when CONT is 1 and MDV is 1, DV is set to
'.'.
Best regards,
Guangli
Quoted reply history
-----Original Message-----
From: [email protected] [mailto:[email protected]] On
Behalf Of Ron Keizer
Sent: Monday, March 16, 2009 6:23 PM
To: [email protected]; [email protected]
Subject: Betr.: [NMusers] 20 variable limit in $INPUT
Andreas,
Some months ago I spent a few hours investigating this same problem. Below
are my notes. Currently I use the last approach (which is actually a
workaround, sorry...), that will hopefully be redundant when NM7 arrives,
best regards,
Ron
approaches for using more covariates in dataset:
* using CONT method
( http://www.cognigencorp.com/nonmem/nm/99aug272005.html):
- Pro: easy using PsN to generate the splitted dataset
- Con: Could get it to work only in NMV, not in NMVI (reason unknown, with
and without PsN). poorly documented in NM. Needs ID CONT DV and MDV as the
first columns on each row.
* using Fortran script
( http://www.cognigencorp.com/nonmem/nm/99mar232005.html)
- Pro: in theory neat method, separate dataset for covariates.
- Con: gave problems with g77 compiler, but works with df. Needs adaptation
for time-changing covariates.
* row-wise incorporation in dataset using EVID=2 events.
- Pro: solves problems with above methods... Unlimited amount of covariates.
- Con: can make datasets much bigger (=slower?) when lot of covariates
included (however, in NM6 easily switch on/off reading of covariates using
IGNORE=...). May need extra code to avoid numerical difficulties for
covariates that define states at t=0.
RJ Keizer, PharmD
Department of Pharmacy & Pharmacology
Slotervaart Hospital / The Netherlands Cancer Institute
Louwesweg 6, 1066 EC Amsterdam, The Netherlands
Phone: +31205124662
>>> <[email protected]> 03/16/09 2:43 nm >>>
I am looking for a solution to get around the limit of 20 input variables
in nonmem.
The message you get with more than 20 variables in $INPUT is this:
16 $INPUT: NO. OF DATA ITEMS EXCEEDS 20.
STOP 4 statement executed
I did not find anything in the archives or on the Web. I recall having
successfully done that in nonmem V, and I think it was about changing the
value of 20 to another value in a few files.
My original naive idea was that this was just a single change to the SIZES
file in nm VI but that seems to not be the case.
To keep the discussion focused, I am not looking for workarounds like
solutions with concatenated values and an indicator variable.
For a change I am trying to get the software to adapt to the user's needs
instead of the usual opposite situation.
Thanks for any pointers.
Andreas
-----
Andreas Krause, PhD
Lead Scientist Modeling and Simulation
Actelion Pharmaceuticals Ltd
Gewerbestrasse 16
CH-4123 Allschwil
Switzerland
The information of this email and in any file transmitted with it is
strictly confidential and may be legally privileged.
It is intended solely for the addressee. If you are not the intended
recipient, any copying, distribution or any other use of this email is
prohibited and may be unlawful. In such case, you should please notify the
sender immediately and destroy this email.
The content of this email is not legally binding unless confirmed by letter.
Any views expressed in this message are those of the individual sender,
except where the message states otherwise and the sender is authorised to
state them to be the views of the sender's company. For further information
about Actelion please see our website at http://www.actelion.com