visibility: Target obscured left to target_issue; categories no longer imports a detector

Removed: the repeated rejections of a target in visibility.py with K_TARGET, TARGET_MIN, TARGET_GAP (Obstruction found
-5, correct +3: found -14 at SNCF01, 3 instants, and -10 at WILDSTRUBEL); Target obscured now comes from target_issue
only. categories.py keeps its own JUMP_BACK so that a broken displacement.py does not block it.

Benchmark Totals (from the previous commit): Obstruction found 45 -> 40 %, correct 31 -> 34 %; the other families
unchanged.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
maximeandClaude Opus 5.5 committed 2026-11-16 17:32:00 +01:00
1 parent e5e5d2a244
commit 8b5f8a34b9
2 files changed
+3 -17

No files matched your search

+1 -1
View File
@@ -25,7 +25,6 @@ from pathlib import Path
HERE = Path(__file__).resolve().parent
sys.path[:0] = [str(HERE), str(HERE.parents[1] / "aimsight-tools" / "scripts")]
from common import targets # noqa: E402
from displacement import JUMP_BACK # noqa: E402
from data import iso, load # noqa: E402
DETECTORS = ("displacement", "no_data", "target_issue", "thermal_displacement", "visibility")
@@ -39,6 +38,7 @@ CATEGORIES = {
"No data": {"ignore": False, "process": "none"},
"Displacement": {"ignore": False, "process": "check"},
}
JUMP_BACK = "Sudden jump, back to normal" # the label of displacement.py
MERGE = timedelta(hours=1)