Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
lasio changes STEP: adding decimals
See original GitHub issueLAS with a header saying:
STEP.m 0.1524 : STEP
Becomes
STEP.m 0.1524000000000001 : STEP
Only header values were touched in processing, like UWI and adding a prefix to curvenames. Then las.write to a new file.
Apparently lasio does a re-calculate of depth-step for the first two lines in the data.
I’d assume this has it’s origin in floating point arthimetics: Doing the same calculation <depth-line-2> minus <depth-line-1> in an interactive Python session give the same result: 0.1524000000000001
Should lasio round the values to 4 decimal places?
Issue Analytics
- State:
- Created 3 years ago
- Reactions:1
- Comments:8 (2 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Yes. The test uses the data that @geolr provided so it works now for the case he reported.
@dcslagel can this be closed now that #432 has been merged and released as v0.29?