You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 893964d
Browse filesBrowse the repository at this point in the historyBrowse files
feat(plan-selection)!: let the deployment's accuracy model decide outputs without a guarantee
- Move AccuracyEvidenceProvider and NoAccuracyEvidence to
asap_plan_selection::accuracy, next to AccuracyModel; OperandDomain and
PropagationStats stay in Stage 1.
- Rename DefaultAccuracyModel to BuiltinAccuracyModel. AccuracyModel::propagate
gets a default body (the built-in rules), so a deployment model implements
only satisfies.
- Add AccuracyModel::accepts_output_without_guarantee (default false). Stage 3
asks it only when neither Stage 1 nor the evidence supplies a guarantee;
an output it accepts is recorded with AcceptedAccuracy::accepted_without_guarantee,
and one it does not is rejected with the new RejectionCause::NoAccuracyGuarantee
(was AccuracyTargetMissed).
- Document accuracy::estimators::local_guarantee and
accuracy::composition::propagate, and drop their duplicate re-exports.
- stage_pipeline writes accepted_without_guarantee; the dag-viewer accepts
the new cause; the example fixture is regenerated.
BREAKING CHANGE: AccuracyEvidenceProvider/NoAccuracyEvidence move to
asap_plan_selection; DefaultAccuracyModel is now BuiltinAccuracyModel; a
candidate whose output has no guarantee is rejected as no_accuracy_guarantee
instead of accuracy_target_missed; AcceptedAccuracy gains a field.
0 commit comments