| Message / code | What to do |
|---|---|
| NO_DATASET | Load a valid LAS file before requesting settings, verification or export. |
| INVALID_JSON | Choose a JSON settings file, not the LAS itself. |
| SCHEMA_VERSION / TOOL_MISMATCH | Use a petrophysics.scene/v1 file with its matching tool. |
| DATASET_MISMATCH | Load the exact original LAS, allowing only line-ending/BOM differences. Do not overwrite its fingerprint to force a match. |
| CURVE_MISMATCH | Inspect dataset IDs, mnemonics and units. A mnemonic alone is not sufficient. |
| INVALID_SCENE or a display-validation message | Check the named property, ordered depth interval, positive log limits, colours and supported choices. |
| REGRESSION_FAILED | Check sample count, distinct X values and positive-domain requirements. The previous successful fit is preserved by this API command. |
| BUSY / DATASET_CHANGED | Wait for the active action and repeat against the current dataset. |
| HASH_UNAVAILABLE | Use HTTPS, localhost, or a supported browser context with Web Crypto. Plotting through the ordinary controls remains available. |
| LAS_INPUT or parser message | Check size, format, curve declarations, numeric data and the NULL sentinel. LiDAR LAS is not a well-log LAS. |
| EXPORT_SIZE / EXPORT_FAILED | Reduce displayed curve legends or use a smaller viewport, and retry. |
Warnings are part of the result
Read import notes and Verify plot: defaulted headers, skipped malformed rows, missing values, log-domain exclusions and duplicate depths can change what is plotted. An empty filter result or an unsuccessful regression is not a software promise of zero uncertainty.
JSON loading does not fetch a LAS file automatically. Source data and settings must be supplied separately. The tools never search your computer or access another tab’s private dataset.