NONMEM Users Network Archive

Hosted by Cognigen

RE: Long file name bugs in NONMEM and NM-TRAN

From: Andreas Krause <akrause>
Date: Wed, 18 Apr 2007 02:02:35 -0700

Let me add that there is seemingly no way to get it to accept spaces in
path names, for example if the path was
../dir with space/data.csv
I tried it plain, using quotes and escaping the space once (\ ) and
twice (\\ ),
all resulting in error messages.
Remember that Windows creates default home directories in
"Documents and Settings/<username>" and a default document location "My

   Andreas Krause

Andreas Krause, PhD
Pharsight Corporation
Strategic Consulting Services


From: owner-nmusers
On Behalf Of Gastonguay, Marc
Sent: Tuesday, April 17, 2007 7:58 PM
To: nmusers
Cc: Ludden, Thomas (MYD)
Subject: Re: [NMusers] Long file name bugs in NONMEM and NM-TRAN

Tom, nmusers:
Here's a suggestion that might be helpful if file names are long because
of a long file path.
NMTRAN does recognize relative path designations, using the location of
the control file as the relative reference.

For example...

If the data file is in:

and the control file is in:

You can refer to a relative path in the NMTRAN control stream, such as:

$DATA ../Data/LongDataFileName.csv


Marc R. Gastonguay, Ph.D.
Scientific Director, Metrum Institute []
President & CEO, Metrum Research Group LLC []
Email: marcg

On Apr 17, 2007, at 12:53 PM, Ludden, Thomas (MYD) wrote:

        We thank Nick Holford for bringing this problem to our attention
and Alison Boeckmann for defining the source of the problem and
providing the workarounds. Please note that the code changes are too
extensive for us to provide code fixes at this time.
        Tom Ludden
        NONMEM Code
        6. Background:
        Filenames in the NONMEM control stream (FSTREAM) for data files,
        specification, and table files may be at most 72 characters
        However, when the filename is exactly 72 characters long, a
        error may occur with some compilers. (When using Sun Fortran
there is
        no error message, and the file is opened correctly.) Note that
there is
        no such bug for input data files that are modified by NM-TRAN,
        when the NONMEM data file is FDATA.
        This bug affects all versions of NONMEM.
        Make sure the name specified for data files, model
specification, and
        table files is at most 71 characters in length.
        NM-TRAN Code
        5. Background:
        NM-TRAN allows all types of file names (including names on the
        record) to be more than 80 characters long. They are truncated
to 80
        characters, with no error message. Further, when the file names
of the
        types listed above are written to FSTREAM, they are further
        to exactly 72 characters. In such cases, the wrong file names
are used
        by NM-TRAN and (possibly) by NONMEM.
        This bug affects all versions of NM-TRAN.
        Make sure the file names specified in the NM-TRAN control stream
are at
        most 80 characters in length. If the file name is that of a data
        (when the NONMEM and NM-TRAN data file are the same), or a model
        specification or table file, then the file name should be at
most 71

        This e-mail transmission may contain confidential or legally
privileged information that is intended only for the individual or
entity named in the e-mail address. If you
        are not the intended recipient, you are hereby notified that any
disclosure, copying, distribution, or reliance upon the contents of this
e-mail is strictly prohibited.
        If you have received this e-mail transmission in error, please
reply to the sender, so that ICON can arrange for proper delivery, and
then please
        delete the message. Thank You.


Received on Wed Apr 18 2007 - 05:02:35 EDT

The NONMEM Users Network is maintained by ICON plc. Requests to subscribe to the network should be sent to:

Once subscribed, you may contribute to the discussion by emailing: