Re: [NMusers] [Suggest] NONMEM adds UTF-8 support for csv files

From: Sebastien Bihorel <>
Date: Mon, 4 Jun 2018 09:04:13 -0400 (EDT)


Two things:
- NONMEM does not require ID to be the first variable in $INPUT
- the headers of your csv file do not have to match the variable names used=
 in $INPUT

So you have 2 easy workarounds for your issue:
- as previously pointed out, you can use another first variable... a deleti=
on flag variable or a study variable are as good candidates as ID for the 1=
st column of your data.
- rename your ID variable as NMID in your csv file (or any alphanumeric com=
bo that do not start with ID for that matter)


From: "Mark Tepeck" <>
To: "Nick Holford" <>,
Sent: Monday, June 4, 2018 7:52:28 AM
Subject: Re: [NMusers] [Suggest] NONMEM adds UTF-8 support for csv files

Hi All,

Unfortunately, the latest release of MS Excel 2017 (build 9330.2087 for off=
ice 365) becomes more restrictive on SYLK files, which is apparently a step=
-back update, but really a typical Microsoft behavior ☹ . Even you =
agree to continue with the warning messages, the latest Excel will end up w=
ith a blank sheet. Using #ID is a practical workaround for this situation b=
ut definitely not the most intuitive one. On the other hand, even most NONM=
EM users are already used to some ‘tricks’, this issue stil=
l costs unnecessary efforts and deepens the learning curve for NONMEM newbi=
es. Personally, it is surprising to see a well-maintained software lack sup=
port for UTF-8 csv files, which are now well supported by all major csv vie=
wers, e.g. Editpad, Notepad++, open office, MS office. If this is a small f=
ix for NONMEM, I sincerely hope that it could become true. This feature mig=
ht potentially streamline NONMEM runs without adding # , as well as make NO=
NMEM learning more fun.

Thank you,


On Mon, Jun 4, 2018 at 1:15 AM, Nick Holford < [ mailto:n.holford_at_auckland.= | ] > wrote:


Excel can open files with ID as the first column header. You just have to a=
gree to continue when Excel shows its warning messages.

Personally I use #ID as the first column header which avoids the Excel warn=
ings and also means I don’t need to specify an IGNORE character in =
NM-TRAN because # is the default.

Best wishes,



Nick Holford, Professor Clinical Pharmacology

Dept Pharmacology & Clinical Pharmacology, Bldg 503 Room 302A

University of Auckland, [
mail&source=g | 85 Park Rd ] ,Private Bag 92019,Auckland,New Zealand

office:+64(9)923-6730 mobile:NZ+64(21)46 23 53 FR+33(6)62 32 46 72

email: [ | ]

[ |

[ |
14 ]

Read the question, answer the question, attempt all questions

From: [ | =
] < [ | ] =
> On Behalf Of HUI, Ka Ho
Sent: Monday, June 4, 2018 4:48 AM
To: Mark Tepeck < [ | ] =
>; [ | ]
Subject: [FORGED] [NMusers] 回覆 : [NMusers] [Suggest] NONMEM=
 adds UTF-8 support for csv files

Dear Mark

Does it work if you don't put "ID" as the first column? Back to the days wh=
en I frequently used Excel, this had been the solution for me.


------ 原有訊息 ------

寄件者: Mark Tepeck

日期 : 2018 年 6 月 4 日週=

收件者: [ | nmus= ] ;


主旨: [NMusers] [Suggest] NONMEM adds UTF-8 support f=
or csv files

Hi NONMEM Users,

As a PK scientist, I often manipulate csv files with Microsoft Excel, R, an=
d NONMEM. As some of you may have seen, if the first record in a csv file i=
s a string “ID”, Microsoft Excel would mistake it as an SYL=
K file which cannot be opened normally by Excel. One workaround is to use a=
ny strings other than ID, e.g. id, '‘ID’. However, this may=
 cause new problems in some scenarios. Another potential solution is to use=
 the R function readr::write_excel_csv ('dataframe.csv') to output a csv fi=
le with UTF-8 Byte order mark. Unfortunately, this csv file turned out to b=
ecome unreadable for NONMEM although Excel likes it. Since waiting for bug =
fixing of Excel by Microsoft is not optimistic, I would truly appreciate it=
 if NONMEM can add UTF-8 support.

Thank you,

Mark Tepeck

Received on Mon Jun 04 2018 - 09:04:13 EDT

This archive was generated by hypermail 2.3.0 : Fri Sep 27 2019 - 17:00:00 EDT