Found during the 2026-07-24 cross-repo parity sweep.
docs/format/04-legacy-wiff-calibration.md:143 and crates/opensxraw/src/raw/dde.rs:22 both explicitly state charge state and isolation width were looked for in DDERealTimeDataEx and not found - a documented dead end. Collision energy and activation type are never mentioned anywhere in the format docs or source, meaning - unlike charge/isolation width - nobody has actually looked yet.
PrecursorInfo.collision_energy/.activation (OpenMassSpecCore/src/types.rs:44-47,52) are populated via ..Default::default() in reader.rs:305, always None/None. CE settings are typically stored per-method rather than per-scan telemetry, so the plausible source is the unexplored MethodSubtree/.../Period0/ExperimentN/IonSourceParamsTable or a sibling CE-specific stream (docs/format/01-legacy-wiff-cfbf.md:23-25 catalogs the tree but has no CE field yet).
Effort: needs new RE work in unexplored method-stream territory - a genuinely open question, not a documented dead end.
Found during the 2026-07-24 cross-repo parity sweep.
docs/format/04-legacy-wiff-calibration.md:143andcrates/opensxraw/src/raw/dde.rs:22both explicitly state charge state and isolation width were looked for inDDERealTimeDataExand not found - a documented dead end. Collision energy and activation type are never mentioned anywhere in the format docs or source, meaning - unlike charge/isolation width - nobody has actually looked yet.PrecursorInfo.collision_energy/.activation(OpenMassSpecCore/src/types.rs:44-47,52) are populated via..Default::default()inreader.rs:305, alwaysNone/None. CE settings are typically stored per-method rather than per-scan telemetry, so the plausible source is the unexploredMethodSubtree/.../Period0/ExperimentN/IonSourceParamsTableor a sibling CE-specific stream (docs/format/01-legacy-wiff-cfbf.md:23-25catalogs the tree but has no CE field yet).Effort: needs new RE work in unexplored method-stream territory - a genuinely open question, not a documented dead end.