Deal with curves with multiple runs by same curve names

[EvanBianco]

The goal is to have a way to load one LAS file to a well with, say, a GR curve, and then load a second file (possibly with different depth extents) with the same curve name, GR.

Basically we need the key in well.data to have an additional information. Like, well.data['GR.1'], well.data['GR.2'], etc.

Newburn H-23 is a well will multiple culprits.

[kinverarity1]

FYI we had this discussion 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 implemented it for now, along with some subtleties around empty mnemonics.

I'm not sure how you'd handle loading two LAS files into the one Well object, each containing duplicate mnemonics. Down the rabbit hole.

[pradhyumna85]

Hi, Any plans to implement a optional functionality for this, which:

1. Allows to pass extra config for this purpose for some files (eg. a dictionary with las filename/well as key, and value as a dictionary with keys as the root name and value is a list of curve names to stack), or a single config for all files, better if regex pattern is supported too
2. A flag can be introduced if <curve_name>:* pattern should automatically considered for splicing
3. Priority would be something like process splicing first and then aliasing

?