Incorrect parsing of null values with negative values

[ghost]

I have a las file where one of the log values is -0.0733. When this is read in with null_policy="aggressive", the value is incorrectly parsed as the string NaN733, presumably because -0.0 is one of the values in NULL_POLICIES.

To avoid this unwanted behaviour, it would be useful if lasio checked that -0.0 was followed by a word boundary and not further digits.

[dcslagel]

Hi @Connossor ,

This should be fixed by pull-request #429 "Change null_policy to handle small non-zero values", which is now merged. If you are working with the GitHub source, could you update to the latest Lasio code and see if your las file's log values are parsed properly when read with `null_policy="aggressive"?

Thank you,
DC

[kinverarity1]

Hi @Connossor I'm closing this based on @dcslagel's comment. Please re-open if you find the solution is not working for you!