Skip to content

fix(python): correct BarometerData field types to scalars#9801

Open
Bartok9 wants to merge 1 commit into
microsoft:mainfrom
Bartok9:aerial/python-barometer-data-types-20260722
Open

fix(python): correct BarometerData field types to scalars#9801
Bartok9 wants to merge 1 commit into
microsoft:mainfrom
Bartok9:aerial/python-barometer-data-types-20260722

Conversation

@Bartok9

@Bartok9 Bartok9 commented Jul 22, 2026

Copy link
Copy Markdown

Summary

  • Align BarometerData Python defaults with C++ BarometerBase::Output / RpcLibAdaptorsBase::BarometerData (altitude/pressure/qnh as real scalars, not Quaternionr/Vector3r).
  • Offline unittest documents the scalar contract without requiring a live sim.

Motivation

Python client types.py historically declared wrong barometer field shapes. That mismatches the RPC adaptor and confuses typed clients/nested from_msgpack defaults. C++ SoT:

struct Output {
  TTimePoint time_stamp;
  real_T altitude; // meters
  real_T pressure; // Pascal
  real_T qnh;
};

Verification

Notes

  • AI-assisted implementation; human-reviewed before push
  • Typo freeze observed (real type bug, not docs casing)

Agent-Owner: sera · Platform: hermes · Claim-TTL: 24h

BarometerBase::Output and RpcLibAdaptorsBase::BarometerData expose
altitude/pressure/qnh as real_T. Python defaults incorrectly used
Quaternionr/Vector3r, which misleads clients and nested decode.

Signed-off-by: Bartok9 <danielrpike9@gmail.com>
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