6.30.3456#

SDK Version attached to KAPPA-Automate 6.30.3456 is version 6.30.5842.

This release contains the following changes.

New Features#

  • MeasureEnum gains the 14 measures that the server catalog exposes but the SDK was missing, and now covers it entirely: MeasureEnum.acoustic_impedance, MeasureEnum.acoustic_noise, MeasureEnum.a_sqrt_k (AreaPermeabilitySquareRoot), MeasureEnum.attenuation, MeasureEnum.k_xmf__2 (PermeabilityLengthSquare), MeasureEnum.parachor, MeasureEnum.power_per_length, MeasureEnum.pressure_derivative, MeasureEnum.absolute_roughness, MeasureEnum.slowness, MeasureEnum.strain_rate, plus the composed measures MeasureEnum.gas_rate_pressure, MeasureEnum.liquid_rate__pressure__0_5 and MeasureEnum.mass_length. They were usable as raw strings only until now.

Improvements#

  • The measures and units documentation has been rewritten from the server catalog (GET /v3/field/unitSystems). The Measures Reference now gives, for every measure, its identifier, its MeasureEnum member, its internal unit and the unit each shipped unit system displays it in; a new Units Reference lists the units accepted by each measure with their UnitEnum member and their a / b conversion coefficients, and documents the payload of the endpoint the catalog comes from. Both tables are regenerated by utils/update_units_doc.py.

  • The allowed analytical models returned for an Automatic RTM workflow are now strongly typed as AutomaticRTMAnalyticalModel values (MZFD, SRVB, Trilinear) instead of raw strings.

  • The output Data of a UserTask now reports its Data.kind as DataKindEnum.basic_data, which is what it actually is on the server, instead of a meaningless DataKindEnum.data. As a consequence, Data.update_data_type() now targets the correct endpoint for these data (it previously failed with a 404 ITEM_DOES_NOT_EXIST), and their Data.md, Data.tvd and Data.tvdss properties no longer raise a ValueError.

Breaking Changes#

  • DataKindEnum.data has been removed. This value never matched any data kind on the server: it came from the user task parameter discriminant (Data / WellProperty), not from a data kind. The output data of a UserTask are now correctly reported as DataKindEnum.basic_data, so use that value instead in any comparison on Data.kind.