Slenser0 commited on
Commit
e740fcb
·
verified ·
1 Parent(s): ac7c35b

upload submissions/README.md

Browse files
Files changed (1) hide show
  1. submissions/README.md +81 -0
submissions/README.md ADDED
@@ -0,0 +1,81 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ # Benchmark Submissions
2
+
3
+ To submit a result, you'll upload two files (no git clone required):
4
+
5
+ 1. **`scores.txt`** to **your own HF model repo** under `.eval_results/SpeechAntiSpoofingBenchmarks/ASVspoof2019_LA/scores.txt`.
6
+ 2. **`<your-slug>.yaml`** as a pull request to **this dataset repo** under `submissions/<your-slug>.yaml`.
7
+
8
+ The YAML in this repo carries a pinned URL pointing at your `scores.txt`, plus its sha256. Scores files do not live in this repo.
9
+
10
+ ## Submitter workflow
11
+
12
+ ### 1. Generate `scores.txt` locally
13
+
14
+ ```bash
15
+ speech-spoof-bench run \
16
+ --model-module <your_package>:<YourModelClass> \
17
+ --datasets SpeechAntiSpoofingBenchmarks/ASVspoof2019_LA
18
+ ```
19
+
20
+ Output: `results/ASVspoof2019_LA/scores.txt` (one line per utterance, `<utterance_id> <score>`, higher = more bonafide).
21
+
22
+ ### 2. Upload `scores.txt` to your model repo
23
+
24
+ ```bash
25
+ huggingface-cli upload <your-owner>/<your-model-repo> \
26
+ results/ASVspoof2019_LA/scores.txt \
27
+ .eval_results/SpeechAntiSpoofingBenchmarks/ASVspoof2019_LA/scores.txt \
28
+ --repo-type=model \
29
+ --commit-message="Add ASVspoof2019_LA scores"
30
+ ```
31
+
32
+ **Note the commit sha** the CLI prints — you'll need it in the next step.
33
+
34
+ ### 3. Fill in the submission YAML
35
+
36
+ Copy `results_template.yaml` to `<your-slug>.yaml` and fill in every field. The two most important fields:
37
+
38
+ - `artifact.scores_url`: the **pinned** URL to your uploaded scores file. Use the commit sha from step 2, not `main`:
39
+ ```
40
+ https://huggingface.co/<your-owner>/<your-model-repo>/resolve/<commit-sha-from-step-2>/.eval_results/SpeechAntiSpoofingBenchmarks/ASVspoof2019_LA/scores.txt
41
+ ```
42
+ URLs with `/resolve/main/` are rejected because they're mutable.
43
+ - `artifact.scores_sha256`: `sha256sum results/ASVspoof2019_LA/scores.txt | awk '{print $1}'`.
44
+
45
+ Leave the `reproduction:` block empty — the maintainer fills it in at merge time.
46
+
47
+ ### 4. Open the PR via HF CLI
48
+
49
+ ```bash
50
+ huggingface-cli upload \
51
+ SpeechAntiSpoofingBenchmarks/ASVspoof2019_LA \
52
+ <your-slug>.yaml submissions/<your-slug>.yaml \
53
+ --repo-type=dataset \
54
+ --create-pr \
55
+ --commit-message="Add <your-slug> submission"
56
+ ```
57
+
58
+ The CLI prints a PR URL. That's it.
59
+
60
+ ### 5. Wait for maintainer reproduction
61
+
62
+ A maintainer runs `speech-spoof-bench reproduce --scoring <PR-branch>`, which:
63
+ - Fetches `scores_url`.
64
+ - Verifies the sha256 against `artifact.scores_sha256`.
65
+ - Recomputes EER from the file.
66
+ - Compares to your claimed `scores.eer_percent` (must match within 1e-6).
67
+
68
+ If it passes, the maintainer fills in `reproduction:` and merges. If it fails, you get a comment on the PR explaining why.
69
+
70
+ ## Verification levels
71
+
72
+ | Level | What the maintainer checks | Cost |
73
+ |---|---|---|
74
+ | `scoring` (default) | sha + recomputed EER from your `scores.txt`. | Seconds. |
75
+ | `inference` (optional, follow-up) | Re-runs your checkpoint end-to-end and regenerates `scores.txt`. Must match within 0.05% EER. | Expensive. |
76
+
77
+ Submissions without a `reproduction:` block never appear in the arena.
78
+
79
+ ## What about git clone + push?
80
+
81
+ You can do it that way too, but for a single 2 KB YAML it's massively heavier. The HF CLI path is the documented one.