C# client for the ComboCurve REST API
View the Project on GitHub insidepetroleum/combocurve-client-csharp
One phase’s configuration to write. xAxis is the only field that cannot always be sent back as GET returns it. When customBasisKey is set, GET returns the basis’s composite ratio as xAxis, and sending that ratio back is a 400. Omit xAxis when customBasisKey is set; otherwise it is required. yAxis determines which factors the phase must include: eur for eur and eur_per_pll, peak for peak, and both for eur_and_peak. In the single-factor cases the other factor must be omitted, not sent empty. customBasisKey cannot be combined with yAxis: eur_and_peak. A basis normalizes a single factor, so the second factor would be ignored. Unknown fields are rejected with a 400 that names them.
| Name | Type | Description | Notes |
|---|---|---|---|
| YAxis | string | What is normalized, and so which factors the phase must include. `eur_per_pll` puts EUR divided by `perf_lateral_length` on the y axis, against `xAxis`. | |
| Targets | List<TypeCurveV2NormalizationTargetInput> | The target values, at most three. Required; send an empty list when no target is set. | |
| XAxis | string | The well header this phase normalizes against. Required unless `customBasisKey` is set. The composite ratios that `GET` returns for a custom basis are not accepted. | [optional] |
| CustomBasisKey | string | One of six fixed derived-axis bases. Cannot be combined with `yAxis: eur_and_peak`. | [optional] |
| LinkedTo | string | The phase whose per-well multipliers this phase inherits instead of applying its own fit. Omit it to have the phase use its own fit. It cannot name the phase itself or a phase that is linked in turn: the source must apply its own fit. The phase's other fields are still required. Because the write replaces the whole configuration, omitting `linkedTo` removes an existing link. | [optional] |
| Eur | TypeCurveV2NormalizationFactorInput | [optional] | |
| Peak | TypeCurveV2NormalizationFactorInput | [optional] |