Repository navigation
FAQ
During single-event setup or at multi-event tournament creation. A tournament's children inherit the choice. Nothing is selected by default, and the first numeric operation locks it. See Engine selection.
Yes, with the separately configured Linux competition runtime: STRATHEX 7.4.3 and
STRATHMARK 3.0.0rc7, labeled LINUX READY. Older numeric previews cannot issue or
settle, and Windows V7 production qualification remains incomplete.
V2 uses local Python by default. Linux V3 runs in a separate local Python process. Both need their dependencies and data installed in advance. V2 HTTP and the V7 service are separate configured transports; neither is an automatic fallback.
It is a seeding forecast. Exact heats and stands must exist before field marks are calculated. Review, approval and separate issue confirmation come afterward.
Marks belong to a complete field. A final has different competitors, so the engine recalculates and rebases the field rather than copying earlier marks.
V2 keeps its original exclusive date cutoff and excludes same-day results. Linux V3 freezes evidence within a round, then can learn from valid settled completions at the next round boundary. Neither uses the old 97/3 tournament blend.
No. V2 accepts quality as compatibility context but ignores it numerically. Do not assume V2's inactive-input rules describe every V3 component; see Prediction methods.
There is no hidden STRATHEX-side prediction selector. V2 uses its reviewed hierarchical core. Linux V3 uses Formula and trained CatBoost ML; its LLM council is unavailable. Retained local council experiments are diagnostic candidates.
Yes, in the separate Accuracy Preview program. They are not enabled in competition predictions. Its historical 2.81% gain misses the 5% qualification target and has no independent future validation.
The forecast interval describes uncertainty in predicted cutting time. Performance spread describes expected race-to-race variation and drives simulation. They are not interchangeable.
Keep the workbook result. Excel is canonical; ResultStore is a separate best-effort write. Preserve the warning and reconcile the derived store without duplicating rows.
No. It shows outcomes under the supplied predictions and assumptions. Officials still review the field and apply the governing rules. See Fairness.
V7 moved numerical prediction to STRATHMARK 2's dated-history core and joint mark optimizer. The old local XGBoost/LLM selector and QAA scaling are historical.
Home · Quick start · FAQ · Repository
Run a competition
- Home
- Quick start
- Choose V2 or V3
- Shared managed events
- Tournament workflow
- Multi-event days
- Brackets
- Backups and recovery
- Troubleshooting
- FAQ
Understand the system
- Handicaps explained
- Workbook and data
- Prediction methods
- Championship simulator
- Simulation and fairness
- Rules and officials
Develop and integrate