SD1212: --STRESN does not equal --STRESC.

SD1212: --STRESN does not equal --STRESC

The reason behind this is that SAS Transport V ("XPT") is a very old format (30 years!) from the mainframe time. It was developed for allowing to exchange SAS data sets between IBM mainframes and VAX computers (only to be found in musea nowadays). The problem is that the binary presentation of numeric values is completely different from the one modern computers are using. The result is that there is an inherent uncertainty (lack of precision) when you have many decimal places when reading the old representation with a modern computer language like Java.
In my own software, I implemented this so that an error is only generated when the two values differ by more than 0.001% or so. I do however not know how this has been implemented in the Pinnacle21 validator.
And the FDA is still refusing to accept Dataset-XML ... :-(

Thankyou

Hi  XML4Pharma,

 Thank you for your answer.

 What a pity there's been no solution yet.

 Therefore, we are going to explain what happened in the Study Data Reviewer's Guide

and just remain the error(SD1212) .

 If you have some other suggestions, I would be appreciate hearing from you.

Best regards,

vivi

Precision

@Jozef This specific issue would not be solved by Dataset-XML though, as we saw in the FDA Dataset-XML pilot, since that format would not have an exact representation of floating point data. I think in this case the Define-XML document needs to define the significant digits.

--STRESN does not equal --STRESC

@Lex: I completely agree.
This is also how the XPT2DatasetXML software works (freely available from SourceForge at: https://sourceforge.net/projects/smart-sds-xml-viewer/files/ )
When transforming numeric values from XPT files, the software looks into the define.xml to find out whether the value is either an integer or a float, and in the latter case looks up what the definined precision is (@SignificantDigits attribute), and "rounds" the value according to that information.
For example, when the direct translation (from XPT-IBM format) is "5.00000001" (although you see "5" in the XPT viewer), and the define.xml states that this is a float with @SignificantDigits (which is a misleading wording, as it defines the precision after the decimal point) = 3, then the value "5.000" will appear in the Dataset-XML data point.
 

--STRESN does not equal --STRESC

Hi All,

I have faced the similar issue in PP domain recently. Let me know if there is any update to be done. As per the previous comments looks like there is an issue.

Thanks,

Subhash

--STRESN does not equal --STRESC

There is no solution for this, except for finally getting rid of SAS Transport 5 and moving to modern formats like XML, JSON, Turtle-RDF.
A "workaround" can be e.g. to check whether the values differ by more that 0.001% or so, or use the "SignificantDigits" from the define.xml.

When one thinks a bit further, why should the same information be provided twice (data redundancy in -STRESC and -STRESN)?
Right, ONLY because of the mandated use of outdated SAS Transport 5 ...