Differences between running P21 GUI vs CLI

d David

on August 27, 2019

I've noticed when testing CLI validation of 3.0.1 that there are differences in the results of the validation between CLI and GUI.

Using the same XPTs running CLI took 30 mins compared to GUI 10 mins. I think the differences in time could be due to CLI having to download configs/checks from the internet. The time isn't so much of an issue, but when checking the validation report there are significant differences even though both use the same config files and validation engine, except in a different location due to the new install nature of P21 3.0. They are identical as they have been copied from c:\users docs to a central location to run CLI.

Pinnacle 21 Validator Report - CLI
Configuration:........\pinnacle21-community-3-0-1\resources\app.asar.unpacked\components\lib\configs\1903.1\SDTM-IG 3.2 (FDA).xml
Define.xml: Not provided
Generated: 2019-08-27T12:19:13+01:00
CDISC SDTM CT Version: 2018-12-21
Validation Engine Version: 1903.1

Pinnacle 21 Validator Report - GUI
Configuration: ...... \Documents\Pinnacle 21 Community\configs\1903.1\SDTM-IG 3.1.2 (FDA).xml
Define.xml: Not provided
Generated: 2019-08-27T15:06:16+01:00
CDISC SDTM CT Version: 2018-12-21
UNII Version: 2018-10-25 (seems to be defaulted)
NDF-RT Version: 2018-02-05 (seems to be defaulted)
Validation Engine Version: 1903.1

Attached are the summaries of the same AE dataset, but these differences also happened for most other datasets when I would expect them to be the same. Any hints or guidance would be much appreciated.

Thanks

David

Attached Files

p21_cli.PNG

p21_gui.PNG

Forums: Troubleshooting and Problems

Philipp

on August 27, 2019

P21

Re: Differences between running P21 GUI vs CLI

Hello David!

Thank you for the feedback!

It looks like you are running CLI and GUI validations against different config files (SDTM 3.2 for CLI and 3.1.2 for GUI). That probably caused a difference in rules firing.

To set the standard and version in CLI you can use specify --standard and --standard.version or just provide a direct or relative path to the config file as --config.

As I see from report summary that you've provided, CLI is also missing --unii.version and --ndf-rt.version. You would probably want to specify these parameters for SDTM validations, as they aren't picked up automatically.

We recommend putting CLI jar into Documents/Pinnacle 21 Community, then it will be able to reach all latest configs, CTs and dictionaries.

Documents/Pinnacle 21 Community/configs folder gets auto-updated when you use Community GUI, so if you use CLI from Documents/Pinnacle 21 Community, you can always get identical and up-to-date results.

Thanks,

Philipp

d David

on August 28, 2019

Thanks very much, that was…

Thanks very much, that was indeed the issue! I was sure that GUI now defaulted to 3.2 and that was the only part I didn't double check, so it matches now. Thanks again!