Repository navigation
Phase 2: Parallel Tas + OpenStudio runs from SAM_UI with jobs panel, progress and cancel (gate G4) #235
Description
Parent: #227
Goal
Implement the job runner designed in #234, and run the validated Tas and OpenStudio workflows in parallel from SAM_UI.
Scope
- The job layer has no WPF dependency, so the SAM MCP server (Phase 3: SAM MCP server on validated simulation workflows and job layer (extensible to other SAM functions) #236) can use it too. The engine adapters wrap the validated Phase 1 paths (Phase 1: Minimal OpenStudio/EnergyPlus run from SAM_UI without disrupting Tas (gate G1, first PR) #229, Phase 1: Unified "Run Simulation" (Tas / OpenStudio / Both) on one frozen snapshot + Tas/OpenStudio comparison report and lightweight view (gate G2) #231) and do not reimplement them.
- A Jobs panel showing status, progress, cancel, the run folder, and an "open comparison" action when a Tas/OpenStudio pair finishes.
- Tas concurrency is capped by licence limits. Each Tas job runs on its own STA thread.
Depends on
#234 (approved design), G3 (#233).
Acceptance criteria / gate G4
| Check | Where | Result |
|---|---|---|
| Unit tests: scheduling caps, cancel, manifest round-trip, using a fake engine | GitHub CI | NOT RUN |
| Parallel results identical to sequential results for cases A and B (B1a byte-equal apart from timestamp and duration) | Local, licensed Tas + OpenStudio 3.10 | NOT RUN |
| Wall time measured, sequential vs parallel | Local | NOT RUN |
| Cancel kills each engine's process tree; no partial results are written to the open model | Local, manual | NOT RUN |
| Licence cap respected (N+1 Tas jobs queue and do not fail) | Local, licensed Tas | NOT RUN |
Activity