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
Docstrings for the lasio package — lasio 0.30 documentation
Configure or change STRT, STOP, and STEP values on the LASFile object. Keyword Arguments: STOP, STEP (STRT,) – value to set on the...
Read more >Adding and Subtracting Decimals (How to) | Math with Mr. J
Learn about adding and subtracting decimals with Mr. J! This video will cover how to add and subtract decimals and examples will be...
Read more >How to Add Decimals | Math with Mr. J - YouTube
Mr. J will go through adding decimals examples and explain the steps of how to add decimals. ✓ MORE ADDING AND SUBTRACTING DECIMALS...
Read more >ADDING AND SUBTRACTING DECIMALS
TO ADD OR SUBTRACT DECIMALS: 1) Line up the decimal points vertically. Fill in any 0's where necessary. 2) Add or subtract the...
Read more >Adding decimals: 9.087+15.31 (video) - Khan Academy
Just remember: we must line up the decimals and keep the place values aligned throughout the calculation, move the decimal straight down, ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
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?