lasio

lasio copied to clipboard

**Describe the bug** For a file containing this data section: ``` ~A Depth GAMN NEUT SP IND CALI 0.05 -2163.978 -0.0 -3.049 -90.567 34.779 0.10 56.264 -0.0 -3.049 -90.567 34.779...

kinverarity1

Provide an option in `LASFile.write` to put curve names in the ~A row. This is related to #30 and #90 which address reading this kind of data in. ***What is...

kinverarity1

Cannot write a file with non-numeric values in ~A section

3

sample file bellow. >~Version Information VERS. 2.0: CWLS log ASCII Standart - VERSION 2.0 WRAP. NO: One line per depth step ~Curve Information Block DEPT.m : data.u :data ~Ascii Log...

ASRSim13

Retain comment lines (e.g. `#`) so that they can be written out

1

This causes an error at the moment but should be accommodated: ``` #11/15/1999 13:29:44 Updated by the Kansas Geological Survey # #KGS#ID: 30S30W/1006347516 # #KGS#INPUT_FILE: /home/crude2_3/WellLogs/Watney/sw-ne/Kohn119a.las.las ~VERSION INFORMATION VERS. 2.0:...

kinverarity1

**Is your feature request related to a problem? Please describe.** We need a clear way to see how a given PR changes the speed of lasio, based on the pytest...

kinverarity1

STEP should only be recalculated if the depth index curve is modified

3

Prompted by #404. Currently, by default (`STEP=None`) `writer.py:write` modifies the `LASFile.well.STEP` header value to be the difference between the first two depth intervals in the file. This is intended so...

kinverarity1

**Is your feature request related to a problem? Please describe.** Many users will never use lasio directly, but will instead use it via functions like [`welly.Well.from_las`](https://github.com/agile-geoscience/welly). I want to explore...

kinverarity1

Need to test on output for a regular depth increment because otherwise other LAS software will break. If the input file has it then the output file must.

kinverarity1

Allow writing of LAS 3 sections (i.e. non standard)

2

Ref email enquiry. Need to modify writer.py to allow the addition of sections which are not contained in the LAS 2 specs e.g. Tops_Parameter, Tops_Definition, Tops_Data

kinverarity1

Null subsitutions do not work for non-numeric data sections

2

I am working with files that have characters in the data section. The substitution of null values is broken for them. Adding `null_policy` is not helping. las_file = lasio.read('characters.las.txt') las_file...

krzysztof-slowinski