b Bedeoan
on

 

Hi all,

Do we need a rule for limitating the number of decimals used to represent the --STRESN variable for domains that contain measurements - e.g. OM or BW?

 

Forums: Validation Rule Suggestions

s Sergiy
on June 11, 2012

Hi!

What do you suggest for this check?

 

b Bedeoan
on June 12, 2012

Hi Sergiy,

I'm not 100% sure about this. It was more like a question than a suggestion.

E.g. for OM you can have both collected measurements (e.g. 500 g) and "derived" measurements that are computed as ratio (percentage) between the organ's weight and the subject's final body weight (0.12345%).

For collected measurements there should not be any problem: no one will collect weights with more than a reasonable amount of digits (2-3 digits). The derived measurements are computed however as ratio (percentage) and here you can get values with a high number of decimals - unless your exporting system is capable of limiting the number of decimals.

Maybe it should be decided how many decimals are actually relevant for statistics? And limit the number of decimals for the numeric values (mostly --STRESN variable) to that amount?

Thanks!

 

 

a Anthony
on June 13, 2012

It appears this can be accomplished by a cross-check between the data and the SignificantDigits attribute of the corresponding ItemDef in the define.xml?

Want a demo?

Let’s Talk.

We're eager to share and ready to listen.

Cookie Policy

Pinnacle 21 uses cookies to make our site easier for you to use. By continuing to use this website, you agree to our use of cookies. For more info visit our Privacy Policy.