Known Bugs
The most common source of errors is problems with psn.conf. Instructions about how to make correct settings can be found in PsN Configuration.pdf.
Like all software, PsN has bugs. Some unfixed bugs and known workarounds can be found in the document Known Bugs and Workarounds.pdf.
Known Bugs in PsN 4.9.0
- sse will use the wrong simulated data for reestimation if the simulation model file has more than one $INPUT statement. The table file with simulated data used for reestimation will only include the items from the last $INPUT. Note: It works fine to split $INPUT over several lines, as long as the text $INPUT only appears once.
- Data values with more than five significant digits in sse. The simulated datasets used in sse are \$TABLE output from NONMEM, and NONMEM rounds off values when printing tables. In NONMEM 6 1013201 is rounded to 1013200 (five significant digits), and if this makes a significant change to the model estimation, for example if the value is a covariate, then the sse results will be wrong. In NONMEM 7 it is possible to set the FORMAT option in $TABLE to make sure no important information is lost. With NONMEM 6 the user must make sure the rounding to five significant digits does not harm the results.
- Lower case user defined and reserved words. Starting with NONMEM 7.2 lower case user defined and reserved words are supported. This is not supported by PsN. For example in $INPUT all reserved words have to be upper case.
Submit a Bug
Please help us improve PsN by letting us know about undocumented errors or problems.
The easiest way to submit a bug is to use the New Issue feature of the PsN repository on Github.
Note that you need to sign up to be able to use Github.
Before you send your issue, please check
Known Bugs and Workarounds.pdf if the error or the problem you are experiencing already has appeared.
You can also check the reported issues and if there is a suitable solution available.
You can browse the issues by using the label tab as well as the Milestone tab (for different PsN versions) at the PsN Github repository.
Include the following information when submitting a bug
- Your operating system (Windows 10, Mac OS X, Red Hat Linux etc.)
- The PsN version you are using.
- In reasonable detail, what the bug is and what you did when it appeared.
- The command you used to start PsN and all messages that PsN gave up until the crash.
- Any other information you think might be helpful.
But please, do not send any model files or data files unless we ask you to do so. From there we will try to help you out.
If you sign up to the PsN mailing list you can also get help from other PsN users and read about already submitted bugs in the mailing list archives.