Re: Installation of NONMEM using NMQual.

From: "Gastonguay, Marc" marcg@metrumrg.com Subject: Re: [NMusers] Installation of NONMEM using NMQual. Date: Mon, 24 Apr 2006 22:06:52 -0400 Dear Ramajogi, I'll try to answer your general questions about NMQual and then the specific questions about the code changes you are trying to implement. NMQual is an open-source (GPL) tool to implement and track whatever NONMEM code changes/install options a user wishes to make for a given installation. NMQual also links each specific installation to a specific NONMEM run command and provides a mechanism for ensuring installation code integrity at each run time. NMQual 4.1 is provided with templates with typical code changes for all reported NONMEM V bug fixes and some of the common setup options, compiler or operating system specific changes as well. I believe that NMQual is the only publicly available tool that automates the processes of keeping your NONMEM installation up to date and maintaining a record of all code changes. For more information on how to use NMQual, please read the User Guide and see the FAQ on the NMQual resources web site ( http://metruminstitute.org/downloads/nmqual/). You might also be interested in attending the upcoming web-cast training sessions on NMQual ( http://metruminstitute.org/training.html). A fee-based Professional Services Package with extended support is also available from Metrum Research Group, LLC (nmqual-services@metrumrg.com). The code changes you've identified in steps 13 and 14 are not part of the standard recommended code changes for NONMEM installation on linux, but I think I've found the sources for these: Your Step #13 is related to display of iteration results to the terminal and is not a required installation step on linux. As Bill Bachman points out, this is a recommended code change if you are running with the PDxPop interface. See: http://www.cognigencorp.com/nonmem/nm/98dec112003.html I can't find a reference in the NONMEM installation guides for your Step #14, but this change has been suggested by Nick Holford so that NONMEM's INTER file is not deleted after completion of a run. See: http://www.cognigencorp.com/nonmem/nm/98may192005.html You can safely install NONMEM without implementing these changes, as is the default in the NMQual configuration and changes (changes.linux.01.xml) files, but you can also modify the changes files to accommodate the additional changes. For example, if you want to implement your Step # 14, you could create a new changes.*.xml file (call it changes.linux.02.xml) by using changes.linux.01.xml as a template and inserting the following lines of code before the the last </changes> sentinel in the xml code. (Make sure to refer to the new changes.linux.02.xml file in the setup configuration file): <change> <ref>From Nick Holford's nmusers post ( http://www.cognigencorp.com/nonmem/nm/98may192005.html)</ref> <file>nm/CFILES.f</file> <from> CLOSE(UN(28),STATUS=DELETED)</from> <to> C ATTRIBUTION C CLOSE(UN(28),STATUS=DELETED) CLOSE(UN(28))</to> </change> One of the useful features of NMQual is that these changes will be tracked to a particular NONMEM installation and you can re-use the configuration and changes files across multiple installations so that you don't have to do this manually each time. NMQual can also be used to efficiently install NONMEM across a grid or cluster of computers. I hope you'll find this useful. Marc ----------------------------- Marc R. Gastonguay, Ph.D. marcg@metrumrg.com www.metrumrg.com NONMEM® is a registered trademark of the University of California and is licensed exclusively to GloboMax LLC. _______________________________________________________