Matt Hall
Matt Hall
Need to think a bit about how this would work with aliases, either as a key and/or as a value. Will need to be implemented in various places.
Implemented, but in a fairly hacky way... going to leave this open for now. 
Hm, hard to change in the repr because of course it has no arguments... could be a project-level attribute. `identifier` can be any field in `well.header` (say).
I don't know if there's a newer version, but of course everything is always in the history, eg https://github.com/agilescientific/geocomp-gl/blob/74b714c91022a29ce1f4a95ae5bc348887bdc44c/master/Plotting_well_data.ipynb
Definitely could be improved. These might help: - You can pass a 'legend' to describe how to plot curves. - You can pass kwargs to `well.plot()` and `curve.plot()`, and these...
Actually, not sure about the kwargs option in your case, but check out the use of legends in tutorial/Plotting.ipynb.
What might that list look like? CSV type of thing?
Need to think about where to put the result of this... doing it on the way to the DataFrame is a 'soft' merge, not changing the well's data. But doing...
Right, it's indexing. Just implemented in a wonky way, compared to `pandas`. Each curve has its own. It is computed from `start` and `step`, and has the same length as...
Good point. Thank you for thinking about this. It wouldn't be too hard to implement, because `scipy` has various interpolation methods, including nearest, previous, etc. In the meantime, it's not...