search

PardeeCenterDU / IFs-Issues-Tracking

This repository only holds the list of bugs that have been reported for IFs. Anyone may add a bug report, but please look to see if your issue has already been added!
2 stars 0 forks source link

Different number of decimal points in imported data #276

Closed quciet closed 8 months ago

quciet commented 8 months ago

I'm using this file as an example pip_215.xlsx. When importing, the MostRecent column produces more number of decimal points than required.

image

In addition, I checked previous tables I merged to the master database and found an issue I was not able to explain. Poverty tables from WDI (IncBelow2D15c%, IncBelow3D65c%, and IncBelow6D85c) were brought in during the WDI batch pull (database version IFsHistSeries 8.05 + WDI 20230911). Here is the IFsDataImport.db file that was merged into the master database IFsDataImport WDI.zip. In that update, values in these tables are normal. See the screenshot below, image

These tables have not been updated since then, you can double check that by looking at the DataDict table, the last update date is still 2023/07/25. However, values in those tables are showing a weird pattern now, i.e., inconsistent number of decimal points between the actual data values and the most recent column. I checked several versions of database in IFs and think this happened as early as IFs version 8.09. image

Any idea why this is the case? Thanks!

PardeeCenterIFs commented 8 months ago

I found the MostRecent rounding issue, and it was easy to fix, that will be included in version 8.19.

Regarding the issue you're showing bellow, is it possible it's the same issue you were talking to Mohammod where some Nulls were replaced with 0s? notice that the 0.4 MostRecent value is the most recent non-zero value. Or maybe is the MostRecent logic, that is not detecting 0s.

PardeeCenterIFs commented 8 months ago

Could you try importing this again, just the one table and checking if the 0s are not taken into account for the most recent field in the most recent version of the GUI.

quciet commented 8 months ago

Thanks! I tested it with version 8.19 and the issue is now gone.