Open rfaelens opened 2 years ago
Thanks for the input @rfaelens. Do you expect many more variations of NMTRAN vs NM-TRAN? If not I would simply add the hyphen as optional in the regular expression.
I do not expect any other variations; what you propose would also work.
In https://github.com/UUPharmacometrics/xpose/blob/3e67b397a495f92d22a4fc492fb78457b2577c75/R/read_nm_model.R#L100, the code searches for the magic string
NM-TRAN MESSAGES
.Some software uses
NMTRAN MESSAGES
instead (note absence of the hyphen).The package would be much more flexible if all magic strings can be put into an option. That way, I could simply execute
options(xpose.magic.nmtranMessages = "NMTRAN MESSAGES")
, instead of adapting the LST file manually or adapting the xpose code.