NONMEM Users Network Archive

Hosted by Cognigen

Re: FDATA file missing

From: Cook, Sarah <sfcook>
Date: Tue, 26 Nov 2019 16:53:57 +0000

Hi Mark,

I'm guessing that you are probably running NONMEM via PsN. The default beha=
vior of PsN is to suppress some output files, including the FDATA file. To =
request that the FDATA file be retained, you can include the option -extra_=
output=fdata on your PsN execute command line.

I don't think there is any way to include the column headings (since they a=
re ignored and not actually read into NONMEM), but having the FDATA file sh=
ould help you troubleshoot your problem. As far as I know, the warnings rel=
ate to the location in the FDATA file, again, because the ignored rows are =
not actually being read in.

Best of luck,


Sarah F. Cook, PhD
Adjunct Assistant Professor
University at Buffalo
Department of Pharmaceutical Sciences
E-mail: sfcook
Phone: (570) 362-2981
From: owner-nmusers
 of Mark Tepeck <mark.tepeck
Sent: Tuesday, November 26, 2019 11:13 AM
To: nmusers
Subject: [NMusers] FDATA file missing

During my troubleshooting of a failed NONMEM run, I want to confirm the cor=
rect exclusion of some records (e.g., IGNORE CMT=2) for the input file. H=
owever, I could not find the FDATA file in the run directory. Is there any =
way to force NONMEM to generate a FDATA? I am also wondering about the pos=
sible causes of missing FDATA.
Even the FDATA file is available, is it possible to include the column head=
s (e.g., ID, DV) on the top of the numbers? So, I can confirm which column =
is excluded or retained.
In addition, I am not sure whether the dataset related warnings (e.g., DATA=
eing to the FDATA file or the raw input CSV file. In other words, the probl=
ematic record 100 represents the row 100 in the FDATA file or the CSV file?
Thank you,

Received on Tue Nov 26 2019 - 11:53:57 EST

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: