You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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. I want to explore whether (and ideally make sure that) welly is capable, wherever possible, of loading data from LAS files that lasio can already load.
Describe the solution you'd like
It could take a different form, but one idea is to take large archives of LAS files - compiling a list of any such easily-available archives could be a useful side-product - and attempt to parse the LAS files using (1) welly and (2) lasio, to see what happens. We can then look at fixing any bugs that we find, if worthwhile.
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
. I want to explore whether (and ideally make sure that) welly is capable, wherever possible, of loading data from LAS files that lasio can already load.Describe the solution you'd like
It could take a different form, but one idea is to take large archives of LAS files - compiling a list of any such easily-available archives could be a useful side-product - and attempt to parse the LAS files using (1) welly and (2) lasio, to see what happens. We can then look at fixing any bugs that we find, if worthwhile.
Describe alternatives you've considered
Additional context
The repository https://github.com/agile-geoscience/LASinfections could be a useful starting place.
The text was updated successfully, but these errors were encountered: