6.30.3400#

SDK Version attached to KAPPA-Automate 6.30.3400 is version 6.30.5834.

New Features#

  • UnitEnum gains the units newly published by the server catalog, including composite-symbol units such as pressure/time, pressure/depth, pressure.temperature and gas- and liquid-rate-per-pressure ratios, as well as acoustic, slowness, attenuation, power-per-length and parachor measures.

  • Added WellPropertyContainer.get_well_property_measure() to retrieve the measure (MeasureEnum) of a well property by its alias, mirroring WellPropertyContainer.get_well_property_values().

  • ShutIn now exposes ShutIn.rate_multiplier, and a new ShutIn.update() method to edit a shut-in’s category, type, rate multiplier, comment and reference flag. The change is persisted immediately; the ShutIn must be obtained through ShutInList.from_data().

  • Connection now accepts a timeout parameter, applied as a network timeout (in seconds) to every HTTP request, given either as a single value or a (connect, read) tuple. It defaults to (30, 300) — 30 s to connect, 300 s to read — so long-running server operations are not cut short while a hung request still fails eventually. Increase the read value for longer operations, or set it to None to disable the timeout entirely.

  • VsDepthVector now exposes VsDepthVector.data_type, the data-type (phase) alias of the vector. The profiles returned by Well.compute_forward_rates() (ForwardRatesOutputs) are now tagged with their server-assigned data type, so consumers can tell whether a computed rate profile is oil (qo/qod) or gas (qg/qgd) instead of inferring it from the PVT.

Improvements#

  • Filters now inherit the md, tvd and tvdss depth properties from their parent gauge, exposed through Data.md, Data.tvd and Data.tvdss on the filter Data.

  • Data.update_data_type() now targets the correct server endpoint for basic data. Previously it always issued the gauge update request, so calling it on a basic data (DataKindEnum.basic_data) failed with a 404 ITEM_DOES_NOT_EXIST error; it now routes to the basicData endpoint for basic data and keeps using the gauge endpoint for gauges.

  • Bundled the tzdata package so that fields configured with legacy IANA time-zone aliases (e.g. US/Central, Egypt, Japan) no longer fail to load with an invalid timezone validation error on minimal runtime images that ship only the canonical time-zone database.

Breaking Changes#

Field.create_automatic_rtm_aggregator() no longer accepts mandatory_well_properties

Well property inputs (wellbore radius, porosity, etc.) are now selected and validated by the server: it reports which ones are mandatory, along with a default value for each, and the SDK includes them automatically when building the creation request. The mandatory_well_properties parameter had no server-side effect anymore and has been removed — remove it from call sites, no replacement is needed.

AutomaticRTMProperties.input_well_properties now returns typed objects instead of vector id strings

The server no longer reports well property inputs as containerId/alias vector id strings. Each item is now a AutomaticRTMWellPropertyInput, exposing type, value, alias and container_id (the last two are None when no specific alias/container was set for that property). Code that consumed the vector id strings directly must be updated to read the new fields instead.