Compare circuit simulations with fresh instrument measurements

Why use this

1. An engineer may have a simulation trace and a fresh measurement that appear different because their axes, trigger references or acquisition settings do not align. Adjusting the model too quickly can conceal a comparison problem rather than explain circuit behavior.

2. This job could prepare a transparent comparison record with acquisition assumptions and normalization choices visible. The engineer can then decide whether later numerical analysis supports a model change, keeping instrument operation and physical safety under explicit control.

Why an agent / simpler alternative

Useful judgment

Reconcile trace metadata, identify alignment ambiguity and distinguish measurement/setup questions from model discrepancies.

Simpler alternative

Compare traces manually when units, timing and acquisition settings are already consistent.

Unsuitable when

The task would control energized equipment, alter unsafe settings or certify circuit performance without qualified oversight.

Proposed inputs

1. Name

   Trace/model manifest

   Owner

   Authorized engineer

   Minimum scope

   Simulation and measurement identifiers with units and settings

   Quality check

   Check provenance, acquisition time and trigger reference

2. Name

   Comparison brief

   Owner

   Engineer

   Minimum scope

   Expected behavior, allowed alignment and review criteria

   Quality check

   Separate display normalization from physical parameter changes

Access and setup — proposed or unknown

Proposed minimum

1. Use fictional trace metadata and a comparison plan; no oscilloscope connection, SPICE execution or hardware actuation.

Compatibility unknowns

1. Current instrument interfaces, data formats, calibration context and runtime compatibility are unknown.

External actions requiring approval

1. Instrument access, acquisition changes, live circuit work, computation and shared engineering data require appropriate approval.

Expected deliverable and review checks

Proposed artifact

Comparison-plan candidate with metadata reconciliation, proposed alignment checks and unresolved engineering questions.

Critical checks

1. Preserve original traces; record units and time origins; avoid adjusting away unexplained differences; require engineering interpretation.

Missing output evidence

This overlay adds no new output inspection, execution or validation; consult the referenced canonical source outcome limits.

Failure signals and proposed responses

1. Signal

   Milliseconds and seconds are mixed

   Why it matters

   The apparent response mismatch may be a unit error

   Proposed response

   Resolve units before comparing shape.

2. Signal

   Trigger offsets are treated as circuit delay

   Why it matters

   Alignment becomes an unsupported physical conclusion

   Proposed response

   Separate trigger reference from measured behavior.

Effort and cost — unknown

Setup work

1. Document acquisition settings and acceptable comparison methods.

Ongoing review

1. Engineer reviews any later processed traces and model interpretations.

Unknowns

1. Instrument accuracy, model suitability, computation effort and equipment costs are unknown.

First check — proposed, unexecuted

Status

proposed_unexecuted

Synthetic fixture

Invent two trace manifests with different time units and trigger references; draft a reconciliation checklist only.

Acceptance checks

1. Flag units and reference mismatch; calculate no performance estimate; claim no circuit validation.

Stop conditions

1. Stop if hardware safety, data provenance or access authority is unresolved.

Limits

1. A metadata comparison cannot validate a circuit model, measurement accuracy or safe physical operation.