for the pharmacometrician and the system pharmacologist , computer software is , quite simply , the equivalent of the laboratory for the molecular biologist , or of the research clinic for the practicing clinician .
it is the environment where tools are developed , observations and conjectures are made , hypotheses are formulated and tested , multiple scenarios are run , and discoveries are made for the betterment of science or patients .
it is only natural that cpt : psp , in its efforts to merge pharmacometrics and systems pharmacology , wishes to be the home to cutting - edge tutorial papers that can bring practitioners of one discipline closer to the other , spreading beyond the initiated to familiarize our audience with an ever - increasing number of tools .
such familiarity is expected to facilitate new findings , developments , and discoveries by indicating capabilities and potential applications of pharmacometrics and systems pharmacology software and helping with repeatability of the study , an essential element in any scientific discipline . in the words of umberto eco , thinking back to another powerful medium used to propagate information , 
if you want to use television to teach somebody , you must first teach them how to use television . 
the cpt : psp designation for a tutorial , as stated in the journal 's guide to authors , is an  educational article providing practical tutorial on tools , methodologies , and approaches in pharmacometrics and systems pharmacology .
 this is of crucial importance for the continued health of both pharmacometrics and systems pharmacology because the pace of changes in these dynamic fields appears to outpace any concerted efforts to provide timely didactic needs by current higher education systems .
an integrated technical education on modeling and simulation tools has been sporadic , carried out individually in centers scattered around the globe .
as explained in the inaugural editorial and in a description of our disciplines foundational tutorials , cpt : psp strongly supports ( technical ) tutorials that aid the dissemination and uptake of model - based approaches in pharmacometrics and systems pharmacology , targeting a wide spectrum of audiences from novices to advanced modelers . inevitably , many of these tutorials may focus on one or more software tools , some of which may be commercial products or otherwise proprietary .
the cpt : psp editorial team has been debating the content of the tutorials , their scientific scope , and also whether in any way to limit the scope of such tutorials to those where the software is available for free ( whether tout court , for research purposes , or for research purposes to noncommercial organizations only ) , because this fits into the mission of the journal to support the dissemination of the discipline .
this editorial is the result of our deliberations and defines our current position on this topic ; we are putting it forth in cpt : psp to be proactive and in the hope that it will stimulate some needed debate .
an important ( but often underappreciated ) distinction we need to make early on is between a software tutorial and a user 's manual .
we would most often consider user 's manuals not publishable by cpt : psp , as they consist of a sequence of steps and/or reference material that software users can consult as they solve real - world problems or attend a hands - on workshop to learn the mechanics of the software .
cpt : psp looks to publish software tutorials that contain a real - world scientific problem ( case study ) and apply the method or the software to solve that problem step - by - step , much like it is done in a real - world scientific inquiry scenario .
that way , the usefulness of the document is increased , as the reader now learns twice over : from the scientific basis of the solution to the case study , and the operational aspects of the specific computer software being used .
a software tutorial is thus richer than a user 's manual , as it includes both a description of the scientific problems the software is meant to solve and the practicalities of the software tool itself , whereas a user 's manual most often contains only the latter .
we collectively believe that cpt : psp should focus on software tutorials , whereas user 's manuals may be published separately ( in a biomedical computing journal , for example ) or become a useful appendix to a tutorial manuscript ( e.g. , available through a web link ) . in general , the tutorials should provide a balanced view of the field and include consideration of other , similar software .
the journal requires all software to be freely available under the open source initiative for an article to be considered for publication .
the best case in point would probably be that we could not publish a nonmem tutorial if we were to apply such criteria .
to us , there seems to be a fundamental difference between the bioinformatics / computational biology discipline ( where software has always been free and open source , since the very early days of the field ) and ours ( where software has very often , almost exclusively , been commercial ) .
however , unambiguously adjudicating the scientific merit of publications requires that the study be repeatable by other researchers , and this will still be facilitated when the files and data used for any piece of research are made available to others , as opposed to the software platform itself .
an analogy can be drawn when details of an analytical method to assay chemicals or genes are given , but the ability to repeat the study is still impinging on access to a liquid chromatography  mass spectrometry machine or gene sequencer , which obviously can not be easily provided as an appendix to the report !
let us elaborate further on these aspects and on what this implies for the authors and readers of software tutorials published in cpt : psp . in many ways ,
the intent of the more traditional approach of including in research articles the model ( differential ) equations in plain text ensures that mathematical models can be ultimately implemented ( with a bit of work ! ) in any computer code . however , everyone with an interest in this topic is painfully aware that what gets in the way of the process is that the information is usually incomplete and the textual reporting is error prone .
publishing or making available computer code or modeling scripts is intended to streamline the process of implementing anew models described in cpt : psp research articles .
curated databases are also increasingly available that are accessible to all free of charge , without significant restrictions .
it is apparent that databases such as these are of value , and unrestricted access has in general to be evaluated for costs and benefits against other modes of dissemination .
we certainly see availability of computer code as a very important avenue to maximize the impact of our published tutorials . a compromise that we are already striving to implement in the cpt : psp research articles would be to upload enough information to enable the reader to reproduce the model results , assuming the software platform is broadly available , perhaps at a cost
. this could be as simple as a parameter set ( in native format ) , or as detailed as the actual model code or tutorial script ( e.g. , control files for nonmem ) , workspace file , and so forth , depending on the specifics of the platform used .
this would enable the reader access to the software to reproduce the simulations , even if the software is commercial or otherwise proprietary .
the only requirement would be that the journal reader needs to be able to run the code in the native software format and reproduce the published simulations ( for verification ) with no modifications . of note
, this approach is indirectly borne out in the life sciences : a dna sequence is required to be published in some journals , but this does not require the author to supply a sequencer machine as well . the tools to run a simulation can be separate from the conditions and inputs that need to be specified , i.e. , all the details that permit an independent reader re - run the study .
this is in line with the requirements from other journals , and it is our belief that such an approach would satisfy the great majority of readers .
financial interests are often complex and hard to define , and software fees vary widely in the amount of profit they bring . some tools may require a fee which includes user support , and others may charge separately for extended service ( through consulting , for example ) . at any rate , we feel that there may be a place in cpt : psp also for commercial software .
this is provided the considerations we outlined above about reproducibility of the simulations can be met .
we encourage submissions of tutorials where authors are not exclusively employed by the developer , or where not all authors have a financial interest in the software .
we recognize the potential limitations of this ; however , we believe the user base who regularly applies these tools would be attracted to manuscript co - authorship with the developers , thus bringing the user community 's specific perspective to the tutorial text . finally , regardless of its potential shortcomings , it seems to us that  peer review  will continue to be the method of choice for propagation of scientific information on new discoveries and novel approaches to technical problems , and our journal of course wholeheartedly supports this notion .
our view is that peer - reviewed software tutorials to be published in cpt : psp should include : a description of one or more scientific motivating problems that will be used to structure the tutorial flow ; instructions as to how to use the software to solve this or similar modeling analysis problems ; scripts or other computer code or pseudocode , as appropriate , to enable a user to reproduce the tutorial sequence ; and an inclusive author list , ideally comprising users without monetary interests in the software , in addition to the software developers .
a line attributed to the mathematician paul halmos states that  the best way to learn is to do ; the worst way to teach is to talk .  after committing some of our thoughts to paper , we now prefer to let our submissions do the talking .
accordingly , we hope that the software tutorials we will host on the pages of cpt : psp will contain relevant , useful , reproducible , durable , and practical examples to effectively assist our readers in learning , and in turn sharing and thus growing , our craft .
 in addition to methodological tutorials,1 cpt : psp has recently started to publish software tutorials.2,3 our readership and authors may be wondering what kind of format or product is expected , and the review of submissions we have already received prompted several discussions within the psp editorial team . 
 this editorial reflects on these discussions and summarizes their salient points . 
 it aims at providing some details about the current vision of cpt : psp for software tutorial articles . 
 in addition , it brings some clarity on the topic of what role commercial software tutorials can have in cpt : psp and how cpt : psp tutorials differ from publications which describe the software itself , as those which can be found in other computer science journals . 
 finally , the discussion includes reproducibility considerations and the general use of commercial and noncommercial software in cpt : psp publications . 
 we hope our thoughts , and especially a stated requirement to publish user input to the software to aid in reproducibility , will help in guiding our authors and will stimulate healthy debate among our readers about the evolving nature of our science , how it can be facilitated using software and associated databases as a conduit , and what role this journal can play in fostering both the best modeling and simulation practices and the best scientific approaches to computational modeling , to bring the advantages of modeling and simulation to all regular practitioners , and not to just a ( self ) selected few . 
Software Tutorial vs. User Guide
Accessibility of Software and Modeling Study Repeatability
Guidance on Preparing Software Tutorials
Managing Conflicts
Summary