Abstract
AbstractThe OpenCDISC Validator GUI writes output to a fixed location in the installation folder, a behaviour which is not acceptable in a server environment. Furthermore, on each call, the user must navigate to the location of the files to be checked. OpenCDISC does include a command line interface (CLI) which offers user control of both input and output locations but requires relatively complex commands. One solution is to use a scripting language to read the input parameters for the OpenCDISC CLI from a file and make the appropriate calls to OpenCDISC. This approach can be independent of operating system and also facilitates repeated runs. Scripting languages such as Perl or Python are well suited to such tasks but are not always available. We show that R, usually available for statistical analysis reasons, can also carry out such tasks with ease and in a manner which hides operating system level details from the programmer.
Sign-in/Register to access full text options 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
