Matt Hall
Matt Hall
`HTML(p.curve_table_html(tests=tests, alias=alias))` should give a trafiic light for each curve type (column) and each well (row). Columns should at least get a score. For rows, traffic light can be based...
NaNs change back to -999.25 (from Darren Kondrat).  Occurs to me that you're really only ever interested in the null value when reading and writing files. Best thing is...
Right now, if you pas `req` (and `alias` — both are needed) to `Project` or `Well.from_las()`, you get **all** the curves in a given alias. It's probably more consistent with...
Should all be in `well.get_mnemonic()` and `curve.get_alias()`.
Check in with Bruno Pinho about where he got to with borehole paths. Maybe use `pygslib` — https://github.com/opengeostat
Probably with a flag like `auto_order` which is `True` by default (current behaviour). Or maybe there are other options, eg `order='alpha'`, or `order='count'` or `order='keys'` perhaps.
project's well qc table could be better: - Add a quality score per alias/curve (i.e. per column), and an overall score for the project. Would help when running fixes — ...
Copy a curve — a little tricky because want all the header info (can't just copy data)
Get quality of curve or alias from across project... add it to the curve quality table.