lasio
lasio copied to clipboard
Curve mnemonics difficult to browse/discover in files with lots of curves e.g. image data
Is your feature request related to a problem? Please describe. When there are lots of curves (e.g. a file containing image/sonic (generally 2D) data), the curve mnemonics can be difficult to browse or discover. For example, see test_utah_well.las.txt (sourced from https://gdr.openei.org/submissions/1076). There are more than a thousand lines in the ~Curves section. I've clipped most of these out with "...":
~Curve Information
TDEP .ft : {F}
AvgCali .in : {F}
Azimuth .dega : {F}
Breakout_Azimuth_N .dega : {F}
Breakout_Dip_Azimuth .dega : {F}
Breakout_Height_N .ft : {F}
Breakout_Omega_Angle_N .dega : {F}
Breakout_Width_N .dega : {F}
Centered_DEPTH .ft : {F}
Colour . : {S}
Dip_TRU .dega : {F}
FMI_DYN_Azimuth .dega : {F}
FMI_DYN_Dip_APP .dega : {F}
FMI_DYN_DipHeight .ft : {F}
FRACTURE_APERTURE[0] .dega : {F}
FRACTURE_APERTURE[1] .dega : {F}
...
FRACTURE_APERTURE[1078] .dega : {F}
FRACTURE_APERTURE[1079] .dega : {F}
FVA .mm : {F}
FVAH .mm : {F}
HAzi .deg : {F}
HDev .deg : {F}
Induced_Fracture_Azimuth_N .dega : {F}
Induced_Fracture_Dip_Azimuth .dega : {F}
Induced_Fracture_Height_N .ft : {F}
Induced_Fracture_Omega_Angle_N .dega : {F}
InfoArray[0] . : {F}
InfoArray[1] . : {F}
...
InfoArray[12] . : {F}
InfoArray[13] . : {F}
Quality . : {F}
Shape .Dip_Classification : {F}
Terzaghi_correction_factor . : {F}
Type . : {S}
Describe the solution you'd like
The repr()
methods for las.curves
should exploit the fact that the mnemonics for FRACTURE_APERTURE
and InfoArray
already have an index indicated in their mnemonic e.g. [0]
, and so on, and show only their range. Otherwise there is essentially no way to see the curves at the end of the above list unless you deliberately write code to identify them, or you look at the file in a text editor.
We have already written some code for users to do this manually with LASFile.stack_curves
(see #293 and #284). That could possibly be extended or used in some way for this feature request.
Describe alternatives you've considered N/A
Additional context N/A