Measurement: Validate automatic Total R computation in single-point-test flow

[luizvilla]

Context

Source: session recap email (2026-02-19)

Problem

The single-point-test branch mentions automatic Total R measurement (2x Rdson + RLdc), but validation and integration criteria are not formalized.

Expected Outcome

An automated and validated workflow computes Total R and is reproducible against manual DC reference measurements.

Scope

In:

• Verify current implementation in single-point-test.
• Define algorithm and measurement protocol for Total R = 2*Rdson + RLdc.
• Compare automatic output against manual reference.
  Out:
• Full branch merge planning.
• Unrelated measurement channels.

Acceptance Criteria

• Automatic Total R computation is executable from documented flow.
• Comparison against manual reference is included with error threshold.
• Pass/fail criteria are documented for acceptance.

Evidence / Notes

• Email excerpt: "branche single-point-test -> fonctions à tester pour mesurer automatiquement Total R (2x Rdson + RLdc)"
• Related files/paths: supervisor_script_v1_2.py, supervisor_v2_2.py
• Related issue(s): none

[luizvilla]

Related issues created from the same session recap:

• Documentation: Define archive and descriptor synchronization governance: Documentation: Define archive and descriptor synchronization governance #8
• Simulation: Publish adjusted simulation set to shared Pandore path: Simulation: Publish adjusted simulation set to shared Pandore path #9
• Simulation: Investigate loss mismatch between simulation and bench measurements: Simulation: Investigate loss mismatch between simulation and bench measurements #10
• Measurement: Validate automatic Total R computation in single-point-test flow: Measurement: Validate automatic Total R computation in single-point-test flow #11
• Instrumentation: Stabilize DMM trigger timing for fast phase sweep plateaus: Instrumentation: Stabilize DMM trigger timing for fast phase sweep plateaus #12
• Validation: Document benchmark point and bench-vs-simulation comparison protocol: Validation: Document benchmark point and bench-vs-simulation comparison protocol #13