Let's see if you are smarter than my vendor...

[Zenmervolt]

Rules for a system are specified thus:

? Group 1 = lowest up to, but not including 33.34
? Group 2 = 33.34 up to but not including 66.67
? Group 3 = 66.67 or higher

An item has a value of 33.335. Into which group should it be assigned? Note that the system will always display 33.335 as "33.34".

A) Group 1 since 33.335 is less than 33.34.
B) Group 2 since 33.335 rounds to 33.34 and the specifications only go out to two decimal places.
C) Call the client and validate.

ZV

 

[randay]

need more details. how do we know the value is 33.335 when the "system" always displays 33.34?

 

[Ramma2]

If the system always displays it as 33.34, and other bits of the app are reading it as 33.34, then it goes into the 33.34 category.

If other bits are pulling it as 33.335 then it should be in group A.

 

[Ns1]

I say group 2, but call the client to make sure.

 

[mordantmonkey]

what the system displays to the end user and what it uses for calculations can very often contain a different number of significant digits.

 

[randay]

on second thought, its probably not the vendors fault that the client provided the wrong amount of sig figs. the nice thing to do is to call client and get a new number, but if its clearly stated, rounding the number also would be fine.

 

[jagec]

Poll needs an option for "Group 3" just to see how stupid people can be.

Sig figs would put it in Group 2, but I'd still call the client.

 

[MotF Bane]

Add an option: burn significant digits.

 

[nakedfrog]

Whatever I feel like at the moment, and blame it on poor specs.

 

[legoman666]

sig figs are for saps. I use as many decimal places as I have.

 

[Zenmervolt]

Originally posted by: randay
need more details. how do we know the value is 33.335 when the "system" always displays 33.34?

User interface displays 33.34. Calculating the values yields 33.335.

ZV

 

[Zenmervolt]

Originally posted by: nakedfrog
Whatever I feel like at the moment, and blame it on poor specs.

If I didn't know better, I'd say that you were the vendor I'm working with.

ZV

 

[Safeway]

Originally posted by: Zenmervolt

Originally posted by: randay
need more details. how do we know the value is 33.335 when the "system" always displays 33.34?

User interface displays 33.34. Calculating the values yields 33.335.

ZV

That's a shitty fucking program, then.

Option 4, rewrite the shitty program.

 

[Zenmervolt]

Originally posted by: Ramma2
If other bits are pulling it as 33.335 then it should be in group A.

The number will be recorded in the system of record as 33.34. There is no other system that will ever see or interact with the 33.335 value.

ZV

 

[Zenmervolt]

Originally posted by: Safeway

Originally posted by: Zenmervolt

Originally posted by: randay
need more details. how do we know the value is 33.335 when the "system" always displays 33.34?

User interface displays 33.34. Calculating the values yields 33.335.

ZV

That's a shitty fucking program, then.

Option 4, rewrite the shit.

There is no need for end users to go beyond two decimal places. It would introduce confusion in the user population because all other values for this system are standardized at two decimal places with standard rounding rules.

ZV

 

[Hail The Brain Slug]

Edit: Nevermind, you answered it right before my post. Group 2.

 

[Atomic Playboy]

My preferred digits are my thumb and forefinger, though without the middle finger you would be unable to appropriately signal your intentions in traffic. The ring and pinky finger are not significant digits, and therefore can be dropped.

And it's group 2. If you treat 3.335 as 3.34 in any circumstance, you must treat it that way in every circumstance, or you'll get burned in accounting.

 

[Zenmervolt]

To everyone who has voted for Group 2 or to phone the client for clarity, thank you. You can work with me any day.

To everyone who voted for Group 1, I'm naming my first ulcer after you.

ZV

 

[smack Down]

Group 1 33.335 < 33.34

 

[alkemyst]

Group two...you may have three decimals on that number, but the classification is 2 decimal based.

Just because you have X places decimal doesn't mean you have X places significant.