Score Analysis

Score analysis answers the question: “Why does my solution have this score?” It breaks down the total score by constraint, helping you debug constraints and explain results to users.

ScoreAnalysis

Types that derive #[planning_solution] with a constraints path automatically implement the Analyzable trait, which provides the analyze method.

use solverforge::prelude::*;

let analysis = analyze(&solution);

println!("Total score: {:?}", analysis.score);

for constraint in &analysis.constraints {
    println!(
        "{}: {:?} (count: {})",
        constraint.constraint_ref.name,
        constraint.score,
        constraint.match_count,
    );
}

ConstraintAnalysis

Each ConstraintAnalysis contains:

DetailedConstraintMatch

Each match includes a ConstraintJustification with the entities involved:

for constraint in &analysis.constraints {
    for m in &constraint.matches {
        println!(
            "  {} -> {:?} (entities: {:?})",
            m.constraint_ref.name,
            m.score,
            m.justification.entities.iter()
                .map(|e| e.short_type_name())
                .collect::<Vec<_>>(),
        );
    }
}

Use Cases

• Debugging constraints: Find which constraints fire and why
• User-facing explanations: Show users why a schedule looks the way it does
• Constraint tuning: Identify which constraints dominate the score

See Also

• Score Types — Available score types
• Constraint Streams — Defining constraints