ARVREL
Home / Laboratory exercises

Education and reproducibility · beta.6

Teach the complete chain from virtual source to external timing evidence.

These exercises connect the beta.6 TESTSET↔relay loop, process-bus trust, feeder protection, Transformer Differential, AVR/OLTC, and MMS virtual-control evidence to stable scenarios and explicit claim boundaries.

Scenario catalogValidation matrix

Preparation

Record the model and provenance before the result.

Software identity

  • ARVREL v0.1.0-beta.6 or exact commit
  • Package/source build
  • Windows/.NET context when relevant

Scenario identity

  • Scenario ID and source mode
  • Settings and CT/VT/transformer context
  • Virtual wiring/topology when closed loop is used

Evidence identity

  • Clock/timing profile
  • Trust state and permissions
  • Operation/timing evidence and fingerprints
Data rule: use synthetic, contributor-owned, or explicitly authorized data only.

Laboratory 1 · MET-001 / MET-003

Separate TESTSET metrology from relay processing.

Procedure

  1. Review the default timing profile: 1 µs TESTSET clock, 10 kHz BI, 4 kHz relay processing.
  2. Run the beta.6 internal feeder fault.
  3. Record RELAY ANY PU, TESTSET BI2, operated-element pickup/P→T, relay trip request, and TESTSET BI1.
  4. Explain why BI2 may precede the eventual operated-element pickup.
  5. Compare a 60 ms 50P setting with the 60.000 ms operated-element P→T reference behavior.

Expected evidence

  • Clock domains are explicitly distinct
  • Generic ANY PICKUP is not substituted for operated-element pickup
  • BI1 is the external measured-trip authority
  • WPF cadence is not timing authority
dotnet test .\tests\Arvrel.Application.Tests\Arvrel.Application.Tests.csproj -c Release `
  --filter "FullyQualifiedName~MetrologyGradeTimingTests"

Laboratory 2 · MET-002

Observe causal relay acquisition from settled pre-fault history.

Procedure

  1. Start from stopped source with the relay measurement already valid.
  2. Apply a strong fault at T0.
  3. Observe that protection does not jump immediately to the final phasor.
  4. Observe pickup developing as post-T0 samples replace pre-fault history.

Interpretation

The relay path uses instantaneous signed terminal samples, clipping/quantization, configured delay, and a causal rolling DFT. It neither receives a source-side phasor shortcut nor suffers an artificial empty one-cycle startup blackout.

Laboratory 3 · MET-005

Prove the open-trip-wire invariant.

  1. Disconnect RELAY.BO1.TRIP → TESTSET.BI1.TRIP.
  2. Apply a fault that operates the relay.
  3. Confirm the relay may latch trip internally.
  4. Confirm TESTSET BI1 does not accept a trip.
  5. Confirm no external trip time exists and trip auto-stop does not occur.
Learning objective: a virtual test set must observe the external virtual-I/O path, not peek at relay private state.

Laboratory 4 · reset / re-arm

Retain completed evidence while returning equipment to a valid ready state.

  1. Run a fault to BI1 auto-stop.
  2. Verify OUTPUT OFF · FROZEN CAPTURE while source setpoints remain retained.
  3. Press relay RESET once.
  4. Observe stale causal acquisition release, relay state clear, BO1/BO2 LOW, and BI1/BI2 LOW.
  5. Wait for READY TO RE-ARM.
  6. Confirm completed TESTSET timing/trip evidence remains available and start a new run.

Laboratory 5 · TRUST-001

Keep pickup visibility separate from trip permission.

Procedure

  1. Run the trust-gated feeder test.
  2. Apply current above pickup with a trip-blocking trust state.
  3. Record pickup, blocked reason, and trip result.
  4. Relate the result to AllowsMeasurement, AllowsPickup, and AllowsTrip.

Expected result

Pickup can remain diagnostically visible while a trust reason prevents a new virtual trip.

Continuity and recoveryEvidence and trust

Laboratory 6 · Transformer Differential

Use the shipped 87T/REF baseline.

  1. Run the deterministic 10-scenario self-test and expect PASS · 10/10 · transformer-public-beta-v1.
  2. Apply Balanced through load and verify low differential/no operation.
  3. Apply Internal fault and verify intended 87T/87T-HS behavior.
  4. Apply REF HV/NGR and REF LV/NGR using explicit independent neutral current.
  5. Explain why calculated phase residual is not independent neutral-CT authority.

Laboratory 7 · AVR / OLTC / MMS

Exercise virtual control authority without field authority.

  1. Start the simulated transformer and 17-position OLTC.
  2. Change LOCAL/REMOTE and AUTO/MANUAL states and observe interlocks.
  3. Use an authorized laboratory MMS client for browse/read and DataSets.
  4. Observe reports/GI/integrity, then issue a modeled control.
  5. Record accepted/rejected cause and virtual plant response.
  6. State explicitly that the command terminated inside the simulator.

Laboratory 8 · Engineering report

Turn observations into a bounded, reviewable record.

  1. Choose at least one operate and one restraint/block case.
  2. Record version, source/run identity, settings fingerprint, topology, timing profile, and expected result.
  3. Attach timing/trust/operation evidence and sanitized screenshots only.
  4. Separate observed software behavior from any extrapolation to physical equipment.
  5. Cite ARVREL using CITATION.cff.
Recommended conclusion: “The referenced ARVREL version reproduced the expected deterministic software behavior for the stated fixture. The result is not calibration, type-test, conformance, commissioning, or operational evidence.”

Assessment boundary

Laboratory success does not authorize plant operation.

These exercises are for education, controlled engineering evaluation, and research. They provide no switching authority, protection-setting approval, commissioning acceptance, physical trip output, calibrated test evidence, or hard-real-time performance claim.

RelatedEducation and research workflowNextPublic roadmap