-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Data Precision #353
Comments
Importing excel data (the intervention costings data) in the database has introduced false precision due to the way computers store and calculate numbers and the way the libraries that connect our code to excel work. As a results, we have a whole bunch of numbers with a bajillion numbers after the decimal in the database. This is obviously not correct. To fix it, there's two approaches:
I'm inclined to go with solution 1 for the time being and procrastinate on doing solution 2. Yay/Nay? |
Hi Roman,
Hmm…most numbers in the cost spreadsheets should have no decimals (so as not to appear more precise than they are), and a few really do need decimals (e.g., fortification levels for vitamin B12, which would never be anything larger than 0.xxx, full time equivalents, etc). Would it be possible to round everything to the nearest whole number and then manually change specific fields to have decimals? Louise, what do you think?
Best,
Katie
|
Very possible, though would obviously also be lots of work. And we wouldn't be able to do it until we release, since we're re-importing the data from the spreadsheets continuously. Beyond decimals, there are other instances of too many significant figures e.g. the total 10-year cost is reported as $3,908,368,096 in the excel sheet (maybe we can get a $96 discount somewhere and make it an even $3,908,368,000 😉). I figured that, at least for version 1, having a few too many decimals might not be too bad as long as it allows us to get rid of numbers like |
Teams discussion
@Fuhji which fields have you had problems with?
The text was updated successfully, but these errors were encountered: