Re: 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:
C:\LongDirecotryName\LongDirecotryName2\LongDirecotryName3 \LongDirecotryName4\Data\LongDataFileName.csv
and the control file is in:
C:\LongDirecotryName\LongDirecotryName2\LongDirecotryName3 \LongDirecotryName4\Run\LongControlFileName.ctl
You can refer to a relative path in the NMTRAN control stream, such as:
$DATA ../Data/LongDataFileName.csv
Marc
Marc R. Gastonguay, Ph.D.
Scientific Director, Metrum Institute [www.metruminstitute.org]
President & CEO, Metrum Research Group LLC [www.metrumrg.com]
Email: [EMAIL PROTECTED] Direct: +1.860.670.0744 Main: +1.860.735.7043
Quoted reply history
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, model
> specification, and table files may be at most 72 characters long.
> However, when the filename is exactly 72 characters long, a run-time
> 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, i.e.,
> when the NONMEM data file is FDATA.
>
> This bug affects all versions of NONMEM.
>
> Workaround:
>
> 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 $SUBR
> 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 truncated
>
> 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.
>
> Workaround:
>
> 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 file
> (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
> characters.
>
> ______________________________________________________________________ _________________________________________________________________
>
>