Kent

I just submitted PR #19 for this. I hadn't seen this issue so rather than accepting a list it accepts any number of arrays as arguments. It would align better...

Hi @LuisNavarro93, would you be able to open an issue on https://github.com/kinverarity1/lasio for this? One thing that would be helpful is to post the LAS file or at least let...

The striplog bug for py2.7 is here: https://github.com/agile-geoscience/striplog/issues/91

The other thing that might be nice is an ability to provide a function to parse the UWI (or name) from the well header. Many wells in my dataset have...

Agreed - in lasio it's properly "index" i.e. first curve is `LASFile.index`, but I don't think that's a very natural term to a geologist.

FYI we had this [discussion](https://github.com/kinverarity1/lasio/issues/105#issuecomment-140720623) for lasio and settled on `GR:1`, `GR:2` etc. as the best option - at least for duplicate mnemonics in the same file. That's how I've...

Hey @mycarta -- what version of lasio do you have installed? I'm not sure if this is happening with the latest, I'm not seeing it here with a quick test.

OK thanks, I'll have to dig deeper to try and reproduce it. Get Outlook for Android ________________________________ From: Matteo Niccoli Sent: Tuesday, February 26, 2019 1:13:08 AM To: agile-geoscience/welly Cc:...

I've confirmed that this is an issue with `welly`. Both the `Well` and ``Project`` workflows are affected in the same way. See two example files here for reproducing it: [6038187_las_files.zip](https://github.com/agile-geoscience/welly/files/2943792/6038187_las_files.zip)...

Huh, feels like that should be parsed, I'll try to fix it in lasio.