You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi!
Currently in DLMReader/InMemoryDatasets, Floats very close to zero (under 5e-324) are parsed as missing values. It seems to me that the prefered behaviour should be to parse those as 0.0 (like CSV/DataFrames does) in order to distinguish from "real" missing values. Keeping the warning (as opposed to CSV) is probably a good idea though. What do you think about it?
Thanks a lot!
The text was updated successfully, but these errors were encountered:
I think Julia Base parser doesn't allow such a behaviour, however, the Parsers package provides such a functionality. Currently, DLMReader prints warnings for the mentioned cases, however, maybe it would be a good idea to round the values to zero and keep the warning message.
Hi!
Currently in DLMReader/InMemoryDatasets, Floats very close to zero (under 5e-324) are parsed as missing values. It seems to me that the prefered behaviour should be to parse those as 0.0 (like CSV/DataFrames does) in order to distinguish from "real" missing values. Keeping the warning (as opposed to CSV) is probably a good idea though. What do you think about it?
Thanks a lot!
The text was updated successfully, but these errors were encountered: