SP SLEEC-PATCH Requirement repair
Evaluation

Evaluation Results

Everything SLEEC-PATCH has saved from repair runs: how many patches were proposed, how many passed verification, and what SLEEC experts decided about them.

Export JSON Download LaTeX

Loading saved results…

At a glance

Patches proposed 0  
Passed verification 0  
Repair runs 0  
Average time per run – From diagnosis to verified patch

Where the patches came from

Rule-based (deterministic) repairs versus AI-generated (LLM) repairs.

SLEEC expert verdicts

Verified AI-generated patches are sent to a SLEEC expert for a meaning check.

Open review →

Results by use case

One row per use case. “Rules changed” counts what the saved patches did to the specification.

0 use cases
No results loaded.

Patches by issue type

Which kind of problem each patch was fixing.

Patches by repair operation

How each patch changed the rules.

Patch explorer

Click any row to see the original and proposed rule side by side.

0 patches
No patches loaded.

Technical records

Diagnosis snapshot for each repair run, plus storage and logging counts.

Diagnosis recorded for each repair run

Number of issues found in the input just before the selected issue was repaired. Runs with the same input fingerprint started from the same specification.

0 runs
No diagnoses loaded.

Storage and logs