Skip to content

Add kriging diagnostic outputs to the task SDK client (superseded) - #347

Closed
amirabbas-jalali-bentley wants to merge 2 commits into
SeequentEvo:mainfrom
amirabbas-jalali-bentley:GSTAT-282-kriging-diagnostic-outputs
Closed

amirabbas-jalali-bentley wants to merge 2 commits into
SeequentEvo:mainfrom
amirabbas-jalali-bentley:GSTAT-282-kriging-diagnostic-outputs

Conversation

@amirabbas-jalali-bentley

@amirabbas-jalali-bentley amirabbas-jalali-bentley commented Sep 9, 2026

Copy link
Copy Markdown
Contributor

Superseded by 348.

Expose the `target.diagnostics` structure introduced by GSTAT-280, so the
16 optional per-location diagnostics can be requested through the SDK.

`KrigingParameters.diagnostics` takes a `KrigingDiagnostics` and is folded
into `target.diagnostics` on the wire, matching how the source and target
filters are already handled. Each diagnostic accepts `True` for the
Leapfrog-aligned recommended attribute name, a string for a custom name, a
typed attribute to update an existing one, or an explicit create/update
specification.

The renamed fields are carried through (`variance` -> `kriging_variance`,
`slope` -> `slope_of_regression`, `efficiency` -> `kriging_efficiency`,
`mean` -> `kriging_mean`, `sample_count` -> `num_samples`), and the result
now parses `target.diagnostics` so `KrigingResult.diagnostics` reports the
definitive name and reference of every attribute that was written.
@amirabbas-jalali-bentley amirabbas-jalali-bentley changed the title Update kriging task SDK client with diagnostic outputs Add kriging diagnostic outputs to the task SDK client (superseded) Sep 9, 2026
@amirabbas-jalali-bentley
amirabbas-jalali-bentley deleted the GSTAT-282-kriging-diagnostic-outputs branch September 9, 2026 15:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant