m3resp.ParameterResult#
- class m3resp.ParameterResult(name, value, modality, category=None, unit=None, metric_type=None, breath_id=None, breath_ids=None, event_id=None, start_time=None, end_time=None, region=None, channel=None, method=None, metadata=<factory>)[source]#
A named, unit-tagged metric produced by a processing step.
A parameter can be scoped to whichever of these apply. All are optional and can be combined (e.g. one metric per breath within a time period), except
breath_idwithbreath_ids, which raisesValueError:a single breath (
breath_id);multiple breaths, e.g. a metric computed over a rolling window of breaths (
breath_ids);a single timepoint (
start_timeset,end_timeleftNone);a time period, e.g. during an intervention or one 30-second window (
start_timeandend_timeboth set) - these are single values on one instance, not a list, so repeated windows are one instance each;a specific
m3resp.data.events.Event(event_id), e.g. a blood-gas draw used for a P/F ratio, or a labeled intervention like a Baydur maneuver;the whole signal, when none of the above are set.
namestays a free-form, human-readable label.metric_typeis the standardized metric this instance represents, used to group/compare across runs regardless of what a step happened to call it: it’s auto-derived fromnameviam3resp.data.metrics.normalize_metric_name()when left unset, and staysNonefor a custom name that isn’t a known standard metric (so nothing is mislabelled). Passmetric_typeexplicitly to override the derivation.modalitynames the device/technique this metric came from;categorynames the physical quantity it is derived from (seem3resp.data.categories). They are independent axes - a Pocc pressure-time product ismodality="ventilator",category="airway_pressure".unitis normalized viam3resp.data.units.normalize_unit().Methods
JSON-serializable representation (
valuebecomes a list if array).Attributes
Whether
valueis a single number rather than an array.- Parameters: