PPSTRESC does not equal PPORRES when PPSTRESU is equal to PPORRESU

n Natalie

on February 19, 2021

Good Morning,

When running SDTM datasets PC, PP and RELREC through Pinnacle 3.1.0 community version my team does not see any error's/warnings regarding the PPORRES in relation to PPSTRESC. However, clients using Pinnacle Enterprise are getting this error when running the same datasets:

SD1353

PPSTRESC does not equal PPORRES when PPSTRESU is equal to PPORRESU

Is there a reason this would show up on the enterprise version and not on the community version?

Thank you very much in advance,

Forums: SDTM

Sergiy

on February 19, 2021

P21

Hi Natalie, Could you…

Hi Natalie,

Could you provide example of non-reported cases?

Please include PPORRES, PPORRESU, PPSTRESC, PPSTRESN, PPSTRESU values.

Thank you,
Sergiy

n Natalie

on February 19, 2021

Not sure if this is what you…

Not sure if this is what you are looking for but here is a snapshot of those variables from the PP dataset:

PP domain

Previously with v2.x.x of Pinnacle we would get STRESC does not equal STRESN. Therefore we chose to round STRESC and STRESN to 6 decimal points to make it equal and leave ORRES.

When I run the PC,PP and RELREC through 3.1.0 using CT 12-18-2020 community version here is the results from the report:

Thank you!

Sergiy

on February 22, 2021

P21

Hi Natalie, Our compression…

Hi Natalie,

Our compression algorithms work based on accuracy of 5 significant digits. So, in your example no SD1353 issues should be reported. I executed your example in both Community and Enterprise with not validation messages for SD1353.

If you like to further diagnose your issue, please contact Pinnacle Enterprise Support.

Kind Regards,
Sergiy