Add data story to presentation
#6
by Lonelyguyse1 - opened
README.md
CHANGED
|
@@ -49,6 +49,19 @@ without cloud inference APIs.
|
|
| 49 |
Fine-tuned vision model:
|
| 50 |
<https://huggingface.co/Lonelyguyse1/halide-vision>
|
| 51 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 52 |
Source repository:
|
| 53 |
<https://github.com/LonelyGuy-SE1/Project-Halide>
|
| 54 |
|
|
|
|
| 49 |
Fine-tuned vision model:
|
| 50 |
<https://huggingface.co/Lonelyguyse1/halide-vision>
|
| 51 |
|
| 52 |
+
Fine-tuning improved the vision stage where it mattered most for the app:
|
| 53 |
+
structured defect JSON, consistent film-defect labels, scratch and
|
| 54 |
+
emulsion-damage vocabulary, and fewer obvious false positives on clean or
|
| 55 |
+
lookalike regions. The runtime still treats model output as candidate evidence
|
| 56 |
+
and validates every box.
|
| 57 |
+
|
| 58 |
+
The data bottleneck was central to the build. Public damaged-film examples are
|
| 59 |
+
scattered, noisy, and often not real negatives, so the training curriculum
|
| 60 |
+
combines FilmDamageSimulator annotations, procedural defect positives, synthetic
|
| 61 |
+
scratches and stains, hard clean negatives, and lookalike counterexamples such
|
| 62 |
+
as grass, subject hair, sprocket holes, borders, and glare. The five private
|
| 63 |
+
negatives stayed held out for evaluation only.
|
| 64 |
+
|
| 65 |
Source repository:
|
| 66 |
<https://github.com/LonelyGuy-SE1/Project-Halide>
|
| 67 |
|