Skip to content

Training results: result_4.3.0 - #28

Open
MateoLostanlen wants to merge 5 commits into
mainfrom
result_4.3.0
Open

Training results: result_4.3.0#28
MateoLostanlen wants to merge 5 commits into
mainfrom
result_4.3.0

Conversation

@MateoLostanlen

Copy link
Copy Markdown
Member

Evaluation results on test set

Metric main current Δ
mAP@50 0.7478 0.7292 -0.0186
mAP@50-95 0.4567 0.4603 +0.0036
Precision 0.7802 0.7670 -0.0132
Recall 0.7130 0.7093 -0.0037

Sequential evaluation on test (optimized params: nb_frames=4, conf=0.25)

TP=152 FN=3 FP=8 TN=134

Metric main current Δ
Recall (TP rate) 0.9664 0.9806 +0.0142
FPR 0.1182 0.0563 -0.0619
F1 0.9312 0.9651 +0.0339
Precision 0.8984 0.9500 +0.0516

Engine parameter optimization (top 10 on val)

nb_frames conf TP FN FP TN Recall FPR F1
4 0.25 133 7 7 123 0.95 0.0538 0.95
5 0.25 133 7 7 123 0.95 0.0538 0.95
5 0.3 132 8 6 124 0.9429 0.0462 0.9496
5 0.35 130 10 4 126 0.9286 0.0308 0.9489
6 0.25 132 8 7 123 0.9429 0.0538 0.9462
4 0.3 132 8 7 123 0.9429 0.0538 0.9462
8 0.25 131 9 6 124 0.9357 0.0462 0.9458
4 0.35 130 10 5 125 0.9286 0.0385 0.9455
4 0.2 135 5 11 119 0.9643 0.0846 0.9441
5 0.2 133 7 9 121 0.95 0.0692 0.9433

(vs last committed results on main)
Branch: result_4.3.0 | Test dataset: pyronear/pyro-dataset @ v4.3.0

MateoLostanlen and others added 5 commits September 7, 2026 14:23
Both fetches pointed at yolo_train_val_corrected / yolo_test_corrected at
v4.0.0-corrected. Those are frozen snapshots added by pyro-dataset commit
76eb464 and tracked outside its pipeline: their content hash is identical at
v4.0.0-corrected, v4.1.0, v4.2.0 and v4.3.0. Bumping the tag alone would have
retrained on the same 32201 files and reported it as a v4.3.0 model.

Switches to the pipeline outputs, which do carry the annotator imports —
roughly 18169 train+val images against 16100 in the snapshot, and the test
set grows from 183 to 190 sequences.

The trade is the frame-level annotation corrections from
vision-rd/data-quality, which only ever existed for the v4.0.0 frames.
Reproducing that pass on v4.3.0 would be the way to get both.

The result-PR footer named the old tag too; it would have misreported which
dataset the numbers came from.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant