asferrer commited on
Commit
5eecc24
·
verified ·
1 Parent(s): 2ac0f22

Upload best LoRA adapter (auto_promote_best)

Browse files
Files changed (1) hide show
  1. README.md +201 -382
README.md CHANGED
@@ -1,391 +1,210 @@
1
  ---
2
- license: apache-2.0
3
- base_model: google/gemma-4-E2B-it
4
  library_name: peft
 
5
  tags:
6
- - vision
7
- - object-detection
8
- - marine-debris
9
- - environmental-ai
10
- - unsloth
11
  - lora
12
- - gemma-4
13
- - peft
14
- - edge-ai
15
- - on-device
16
- - mobile
17
- datasets:
18
- - cleansea
19
- - ocean_garbage
20
- - neural_ocean
21
- language:
22
- - en
23
- pipeline_tag: image-to-text
24
- metrics:
25
- - mAP
26
- model-index:
27
- - name: gemma-4-E2B-it-oceanguard-marine-debris
28
- results:
29
- - task:
30
- type: object-detection
31
- name: Marine Debris Detection (open-vocabulary, 8-class collapse)
32
- dataset:
33
- type: oceanguard-merged-marine-debris
34
- name: OceanGuard merged hold-out (CleanSea + Ocean_garbage + Neural_Ocean)
35
- metrics:
36
- - type: mAP@0.5
37
- value: 0.3253
38
- - type: mAP@0.5_delta_vs_base
39
- value: 0.2329
40
  ---
41
 
42
- # Gemma 4 E2B OceanGuard Marine Debris LoRA Adapter
43
-
44
- A LoRA fine-tune of [`google/gemma-4-E2B-it`](https://huggingface.co/google/gemma-4-E2B-it)
45
- that adapts the model to open-vocabulary detection of anthropogenic marine debris on
46
- consumer mobile hardware. The adapter is the training artefact behind the
47
- [OceanGuard AI](https://github.com/asferrer/OceanguardAI) Android application — a fully
48
- offline marine-debris intelligence toolkit submitted to the **Kaggle Gemma 4 Good
49
- Hackathon** (Global Resilience track, Unsloth $10 K bonus) and built on top of two prior
50
- peer-reviewed publications on underwater debris detection ([Sánchez-Ferrer et al., PRL
51
- 2023](https://www.sciencedirect.com/science/article/pii/S0167865522003889?via%3Dihub);
52
- [IbPRIA 2022](https://link.springer.com/chapter/10.1007/978-3-031-04881-4_49)).
53
-
54
- > **Headline result.** On a held-out 200-image evaluation set the LoRA fine-tune reaches
55
- > **mAP@0.5 = 0.325**, against **0.092** for the unmodified base model
56
- > (Δ = **+0.233**, a **+252 %** relative improvement) while maintaining
57
- > **94.5 %** JSON-validity on the structured detection output.
58
-
59
- ## Model Description
60
-
61
- OceanGuard AI runs **Gemma 4 E2B** fully on-device on a Samsung Galaxy S22 Ultra
62
- (Exynos 2200, CPU + Vulkan/Xclipse 920) for open-vocabulary deep analysis of marine debris
63
- over a 50-class taxonomy that collapses down to **11 canonical ecological-impact families**
64
- (`BOTTLE`, `CAN`, `FISHING_NET`, `GLOVE`, `MASK`, `METAL_DEBRIS`, `PLASTIC_DEBRIS`, `TIRE`,
65
- `FABRIC_DEBRIS`, `GLASS_DEBRIS`, `OTHER`).
66
-
67
- This adapter aligns Gemma 4 E2B with the exact structured output contract that the Android
68
- application consumes a JSON array of `{box_2d, label, material}` objects — and reduces the
69
- rate at which detections fall through to the generic `PLASTIC_DEBRIS` catch-all. The same
70
- LoRA also improves material attribution for the downstream ecological-impact lookup that
71
- drives the app's health-score and report-generation pipelines.
72
-
73
- The adapter is distributed as a standard PEFT LoRA (≈120 MB, `r=16`, `α=32`) attached to a
74
- bf16 base model. End-to-end reproduction fits comfortably on a single consumer GPU (the
75
- ablation grid below was run on an RTX 5090, but the recipe also runs on Kaggle T4 with
76
- 4-bit quantisation).
77
-
78
- ## Intended Use
79
-
80
- **In-scope use cases.**
81
-
82
- - Mobile and edge marine-debris detection for citizen science, NGO field operations, and
83
- coastal monitoring campaigns.
84
- - Research baselines for open-vocabulary detection over specialised environmental
85
- taxonomies.
86
- - A grounding component for tool-augmented reporting pipelines (see the OceanGuard
87
- two-phase tool-calling architecture).
88
-
89
- **Out-of-scope use cases.**
90
-
91
- - Autonomous decision-making (cleanup dispatch, regulatory enforcement, environmental
92
- fines). This model is a triage and reporting aid; final decisions must remain with a
93
- qualified human.
94
- - Real-time safety-critical detection (collision avoidance, navigation). End-to-end
95
- latency on the reference device is on the order of seconds per image.
96
- - General-purpose object detection outside the marine-debris domain the adapter narrows
97
- the visual prior towards marine debris and may degrade on unrelated tasks.
98
-
99
- ## Training Data
100
-
101
- The training set is a permissive-license merge of three open marine-debris datasets,
102
- including the **CleanSea** corpus introduced by the model author ([IbPRIA
103
- 2022](https://link.springer.com/chapter/10.1007/978-3-031-04881-4_49)):
104
-
105
- | Source | License | Annotations | Used in |
106
- |---|---|---|---|
107
- | CleanSea | Research-friendly (per dataset card) | COCO bbox, 8-class | All experiments |
108
- | Ocean_garbage | Research-friendly (per dataset card) | COCO bbox, 8-class | All experiments |
109
- | Neural_Ocean | Research-friendly (per dataset card) | COCO bbox, 8-class | All experiments |
110
-
111
- The ablation grid (see §Evaluation) was run over **eleven dataset compositions** that vary
112
- the ratio of synthetic-to-real images. The published adapter corresponds to experiment
113
- `exp10_real_full`, which uses **13 637 real-image training samples** stratified by class
114
- across the three source datasets. The 8-class taxonomy
115
- (`Bottle`, `Can`, `Fishing_Net`, `Glove`, `Mask`, `Metal_Debris`, `Plastic_Debris`, `Tire`)
116
- is extended at inference time to a 50-class fine-grained vocabulary that is mapped back to
117
- the 11 canonical families through a deterministic lookup table; see
118
- `Gemma4VisionDetector.LABEL_TO_TYPE` in the Android source for the full mapping.
119
-
120
- **Geographic coverage.** The three source datasets were collected predominantly in
121
- coastal waters around Japan and the wider north-western Pacific. As a result the
122
- training distribution is biased towards the debris taxonomy, water clarity, lighting
123
- and sediment patterns of that region. This is reflected in the §Limitations and §Bias
124
- sections below; users surveying outside Japan-Pacific waters should expect a measurable
125
- domain shift and validate the adapter on a local hold-out before operational use.
126
-
127
- Re-distributors of the merged dataset must comply with the original dataset licenses.
128
-
129
- ## Training Procedure
130
-
131
- The published adapter is the winner of an 11-experiment LoRA ablation grid. All runs used
132
- **Unsloth FastVisionModel 2026.5.2** on a single workstation GPU, in bf16.
133
-
134
- ### Configuration (best: `exp10_real_full`)
135
-
136
- | Hyper-parameter | Value |
137
- |---|---|
138
- | Base model | `unsloth/gemma-4-E2B-it` |
139
- | LoRA `r` / `α` / dropout | 16 / 32 / 0 |
140
- | Trainable parameters | 31 039 488 (0.60 % of the 5.15 B base) |
141
- | Target modules | language head linear layers; vision tower frozen |
142
- | Optimiser | `adamw_8bit` (Unsloth fused), `lr = 1e-4` cosine schedule, `weight_decay = 0.01`, `warmup_ratio = 0.1` |
143
- | Batch size | 1 per device × 32 gradient accumulation = effective 32 |
144
- | Sequence length / image token budget | 1 536 / 128 |
145
- | Precision | bf16 |
146
- | Epochs | 3 |
147
- | Steps | 1 281 |
148
- | Seed | 42 |
149
- | Loss | causal-LM over the `box_2d`+`label`+`material` JSON tokens |
150
-
151
- ### Convergence
152
-
153
- Loss decreased monotonically from **15.01** at step 10 to **0.456** at step 1 281; the
154
- last 20 logging windows had a standard deviation of **0.0092** and a minimum loss of
155
- **0.446** at step 1 230, indicating a clean cosine landing with no late-stage divergence.
156
-
157
- ### Hardware and wall-clock
158
-
159
- - 1× NVIDIA RTX 5090 (32 GiB GDDR7), Windows 11, CUDA 12.8, PyTorch 2.7
160
- - Training wall-clock: **6 h 53 min** (24 777 s) for `exp10_real_full`
161
- - Deployment target: Samsung Galaxy S22 Ultra (Exynos 2200) via
162
- [LiteRT-LM 0.11.0](https://github.com/google-ai-edge/LiteRT-LM)
163
-
164
- ### Software
165
-
166
- `unsloth` 2026.5.2 · `transformers` 5.5.0 · `peft` · `trl` · `accelerate` · `bitsandbytes` ·
167
- `torch` 2.7.0+cu128.
168
-
169
- The complete reproducible pipeline (`prepare_datasets → generate_configs → run_experiments
170
- → eval_grid → collect_results → auto_promote_best`) is published in the source repository
171
- under `OceanguardAI-App/finetune/experiments/`.
172
 
173
  ## Evaluation
174
 
175
- All runs are evaluated on a **200-image held-out test split** of the merged dataset, with
176
- the same JSON contract and post-processing as the production Android app
177
- (`temperature = 0.0`, `max_new_tokens = 256`).
178
-
179
- ### Aggregate
180
-
181
- | Metric | Base Gemma 4 E2B | OceanGuard LoRA (`exp10_real_full`) |
182
- |---|---|---|
183
- | **mAP@0.5** | **0.0924** | **0.3253** *(+0.2329)* |
184
- | Predictions emitted | 47 | 292 |
185
- | JSON validity | 1.000 | 0.945 |
186
- | Mean inference latency (RTX 5090) | 1.96 s | 5.43 s |
187
-
188
- ### Per-class mAP@0.5
189
-
190
- | Class | Base | LoRA | Δ |
191
- |---|---|---|---|
192
- | Plastic Debris | 0.112 | **0.608** | **+0.496** |
193
- | Fishing Net | 0.091 | **0.448** | **+0.357** |
194
- | Tire | 0.091 | **0.403** | **+0.312** |
195
- | Glove | 0.309 | **0.463** | **+0.154** |
196
- | Bottle | 0.045 | **0.312** | **+0.266** |
197
- | Mask | 0.091 | **0.308** | **+0.217** |
198
- | Can | 0.000 | 0.061 | +0.061 |
199
- | Metal Debris | 0.000 | 0.000 | 0.000 |
200
-
201
- The fine-tune produces the largest absolute gains on `Plastic_Debris`, `Fishing_Net` and
202
- `Tire` — three of the most ecologically harmful categories in the OceanGuard impact
203
- hierarchy. `Metal_Debris` remains unlearned in this run (99 ground-truth instances in the
204
- training set is the known floor); a class-balanced data campaign is planned. The ablation
205
- grid (`exp01 exp10`) and class-wise comparison against the base model are recorded in
206
- `finetune/experiments/results/results.md` in the source repository.
207
-
208
- ## Deployment
209
-
210
- The adapter targets **LiteRT-LM 0.11.0** on Exynos 2200 once the upstream
211
- LoRA-to-`.litertlm` conversion path lands.
212
-
213
- | Step | Tooling | Status |
214
- |---|---|---|
215
- | Train LoRA on RTX 5090 | Unsloth FastVisionModel | Done |
216
- | Publish adapter on HuggingFace | `huggingface-cli` | ✅ Done |
217
- | Use adapter via Transformers / PEFT | `model.load_adapter(...)` | ✅ Done — see notebook |
218
- | Merge LoRA into base | `peft_model.merge_and_unload()` | ✅ Documented |
219
- | Export merged model to `.litertlm` | `ai-edge-torch.generative` | Blocked on upstream PEFT-export support (in progress, May 2026) |
220
- | Sideload to Android | `adb push` + `VlmModelManager` | ✅ Documented |
221
-
222
- Once the conversion path is unblocked the published adapter is the exact artefact that
223
- will ship on-device — no retraining required. Until then, the adapter is consumed through
224
- Unsloth or stock PEFT in the companion notebook
225
- ([`docs/submission/notebook_finetune.ipynb`](https://github.com/asferrer/OceanguardAI-App/blob/main/docs/submission/notebook_finetune.ipynb)),
226
- and the shipped APK uses the **base** Gemma 4 E2B for single-shot deep analysis. This
227
- is disclosed honestly in the submission write-up.
228
-
229
- Reference benchmarks on the deployment target
230
- (Galaxy S22 Ultra, Exynos 2200, LiteRT-LM 0.11.0, Vulkan via Xclipse 920):
231
-
232
- - Decode throughput: 5.1 tok/s
233
- - Time to first token (warm / cold first load): 2.33 s / 17.34 s
234
- - Prefill throughput: 48.7 tok/s
235
- - Single-shot detection, ~100-token JSON output: ≈ 22 s end-to-end
236
-
237
- ## Limitations
238
-
239
- - **Fixed-with-fallback taxonomy.** The fine-tune adheres to an 8-class core extended to
240
- 50 fine-grained classes. Out-of-distribution debris (polar microplastic, deep-sea
241
- anthropogenic objects) is not represented in the training data and will be mapped to
242
- the generic catch-all classes.
243
- - **CPU + Vulkan-only inference on the reference device.** The Exynos 2200 GPU pass via
244
- Vulkan improves correctness but not throughput; on this hardware Gemma 4 E2B is
245
- reserved for single-shot deep analysis (≈ 20 s end-to-end per image), not for
246
- continuous live-camera operation.
247
- - **Geographic bias.** The training imagery is predominantly sourced from coastal
248
- waters around Japan and the broader north-western Pacific. Performance on the
249
- Mediterranean, tropical reefs, polar seas, the south Atlantic and freshwater debris
250
- surveys is expected to be lower and is **not yet measured**. Users surveying outside
251
- Japan-Pacific waters should treat the model as a baseline and validate against a
252
- local hold-out set before drawing conclusions.
253
- - **Lighting and capture bias.** Synthetic-augmentation passes can inject lighting biases
254
- that may degrade under poor underwater visibility.
255
- - **Underrepresented classes.** `Metal_Debris` (99 ground-truth instances) is not learned
256
- at the current data scale; `Can` improves only marginally. Cross-checks are advised on
257
- predictions for these classes until a class-balanced campaign is shipped.
258
- - **JSON validity is 94.5 %, not 100 %.** Roughly 1 in 18 detections in the eval set
259
- emerge in malformed JSON and are dropped by the parser. The Android app handles
260
- these gracefully by surfacing an empty detection set to the user rather than
261
- fabricating boxes.
262
- - **Not certified.** This model is not certified for legal, regulatory or environmental
263
- enforcement reporting. The OceanGuard app produces draft reports that a human reviews
264
- before any official use.
265
- - **Function-calling head untouched.** The fine-tune is intentionally scoped to the
266
- detection head and does **not** rewrite tool-calling syntax, to avoid regressing the
267
- two-phase tool-calling pipeline that the Android app depends on for grounded report
268
- generation.
269
-
270
- ## Bias, Risks and Safety
271
-
272
- - **Spurious-correlation risk.** Marine-debris classes co-occur with characteristic
273
- backgrounds (e.g. fishing nets with rocky shorelines). The model may exploit context
274
- cues that do not generalise across geographies.
275
- - **Sensitive categories.** The `syringe` / `medical waste` class is rare and high-stakes;
276
- positive detections should trigger human handling protocols rather than autonomous
277
- action.
278
- - **Citizen-science abuse vectors.** As with any open-vocabulary detector, the model can
279
- be prompted to label arbitrary objects; downstream applications should constrain
280
- inputs to the marine-debris domain and filter implausible outputs (the OceanGuard app
281
- does this via `LABEL_TO_TYPE` and the canonical 11-class projection in
282
- `EnvironmentalImpact.IMPACT_MAP`).
283
- - **Privacy.** Photos analysed on-device in OceanGuard never leave the phone; this
284
- adapter itself processes no user data. When used outside the app, downstream operators
285
- are responsible for compliance with applicable privacy regulation.
286
-
287
- ## How to Use
288
-
289
- ```python
290
- from unsloth import FastVisionModel
291
-
292
- model, tokenizer = FastVisionModel.from_pretrained(
293
- "unsloth/gemma-4-E2B-it",
294
- load_in_4bit=True,
295
- )
296
- model.load_adapter(
297
- "asferrer/gemma-4-E2B-it-oceanguard-marine-debris",
298
- adapter_name="oceanguard",
299
- )
300
- model.set_adapter("oceanguard")
301
- FastVisionModel.for_inference(model)
302
-
303
- # Use the exact DETECTION_PROMPT shipped in the Android app — see
304
- # docs/submission/notebook_finetune.ipynb for the verbatim string and helper.
305
- ```
306
-
307
- A fully reproducible end-to-end example (image loading, inference, JSON parsing,
308
- visualisation and quantitative evaluation) lives at
309
- [`docs/submission/notebook_finetune.ipynb`](https://github.com/asferrer/OceanguardAI-App/blob/main/docs/submission/notebook_finetune.ipynb)
310
- in the source repository.
311
-
312
- ## License and Citation
313
-
314
- - **LoRA adapter** — Apache 2.0
315
- - **Base model** — `google/gemma-4-E2B-it`, subject to the Gemma Terms of Use
316
- - **Training datasets** — source-dataset licenses apply (CC-BY or equivalent; see dataset
317
- cards)
318
-
319
- ```bibtex
320
- @misc{sanchezferrer2026oceanguard_adapter,
321
- author = {S{\'a}nchez-Ferrer, Alejandro},
322
- title = {{Gemma 4 E2B OceanGuard Marine Debris LoRA Adapter}},
323
- year = {2026},
324
- howpublished = {HuggingFace Model Hub},
325
- note = {LoRA adapter for google/gemma-4-E2B-it. Apache 2.0.},
326
- url = {https://huggingface.co/asferrer/gemma-4-E2B-it-oceanguard-marine-debris}
327
- }
328
-
329
- @misc{sanchezferrer2026oceanguard_app,
330
- author = {S{\'a}nchez-Ferrer, Alejandro},
331
- title = {{OceanGuard AI: Fully Offline Marine Debris Intelligence with Gemma 4 and Two-Phase Tool Calling}},
332
- year = {2026},
333
- howpublished = {Kaggle Gemma 4 Good Hackathon (Global Resilience track)},
334
- url = {https://github.com/asferrer/OceanguardAI}
335
- }
336
- ```
337
-
338
- ## Related Publications by the Author
339
-
340
- This adapter is the latest iteration of an ongoing line of research on automated
341
- detection and recognition of underwater anthropogenic debris.
342
-
343
- ### Peer-reviewed papers
344
-
345
- 1. **Sánchez-Ferrer, A.**, Valero-Mas, J. J., Gallego, A. J., & Calvo-Zaragoza, J. (2023).
346
- *An experimental study on marine debris location and recognition using object
347
- detection.*
348
- **Pattern Recognition Letters**, 168, 154–161.
349
- [https://doi.org/10.1016/j.patrec.2022.12.019](https://www.sciencedirect.com/science/article/pii/S0167865522003889?via%3Dihub)
350
-
351
- 2. **Sánchez-Ferrer, A.**, Gallego, A. J., Valero-Mas, J. J., & Calvo-Zaragoza, J. (2022).
352
- *The CleanSea Set: A Benchmark Corpus for Underwater Debris Detection and
353
- Recognition.*
354
- In *Iberian Conference on Pattern Recognition and Image Analysis (IbPRIA 2022)*,
355
- Lecture Notes in Computer Science, Springer.
356
- [doi.org/10.1007/978-3-031-04881-4_49](https://link.springer.com/chapter/10.1007/978-3-031-04881-4_49)
357
-
358
- ### Theses
359
-
360
- 3. **Sánchez-Ferrer, A.** (2024). *Modelos de difusión aplicados a la detección de
361
- objetos en el fondo marino.* Master's Thesis, Universidad de Alicante.
362
- [rua.ua.es/…/88244474](https://rua.ua.es/entities/publication/88244474-6165-4cd9-a4af-68eff29d65c6)
363
-
364
- 4. **Sánchez-Ferrer, A.** (2021). *Deep Learning aplicado a la detección de residuos en
365
- el fondo marino.* Bachelor's Thesis, Universidad de Alicante.
366
- [rua.ua.es/…/92c34588](https://rua.ua.es/entities/publication/92c34588-9842-4ec3-8b15-97a8ce718e04)
367
-
368
- ### Applied research
369
-
370
- 5. **Sánchez-Ferrer, A.** (2025). *OceanGuard AI: Mapping and Mitigating Marine
371
- Pollution.* Kaggle hackathon write-up.
372
- [Kaggle write-up](https://www.kaggle.com/competitions/google-gemma-3n-hackathon/writeups/oceanguard-ai-mapping-and-mitigating-marine-pollut)
373
-
374
- The CleanSea corpus introduced in (2) is one of the three sources used to train this
375
- adapter; the detection methodology developed in (1) defines the marine-debris recognition
376
- task that this fine-tune operationalises on-device with Gemma 4 E2B; (3) and (4) lay the
377
- foundational work on which the present model card builds.
378
-
379
- ## Acknowledgments
380
-
381
- - **Google DeepMind** for releasing Gemma 4 under terms that enable open research and
382
- on-device deployment.
383
- - **The Unsloth team** for the FastVisionModel implementation that makes a Gemma 4
384
- vision-language fine-tune tractable on a single workstation GPU.
385
- - **CleanSea, Ocean_garbage and Neural_Ocean** dataset authors for releasing
386
- marine-debris annotations under permissive terms.
387
- - **Google AI Edge / LiteRT-LM** team for the on-device runtime that hosts the base model
388
- in the OceanGuard Android app.
389
- - **Pattern Recognition and Artificial Intelligence (PRAI) group, Universidad de
390
- Alicante** — research group hosting the doctoral programme under which this work is
391
- carried out, and co-authors of the prior publications cited above.
 
1
  ---
2
+ base_model: unsloth/gemma-4-e2b-it-unsloth-bnb-4bit
 
3
  library_name: peft
4
+ pipeline_tag: text-generation
5
  tags:
6
+ - base_model:adapter:unsloth/gemma-4-e2b-it-unsloth-bnb-4bit
 
 
 
 
7
  - lora
8
+ - sft
9
+ - transformers
10
+ - trl
11
+ - unsloth
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
12
  ---
13
 
14
+ # Model Card for Model ID
15
+
16
+ <!-- Provide a quick summary of what the model is/does. -->
17
+
18
+
19
+
20
+ ## Model Details
21
+
22
+ ### Model Description
23
+
24
+ <!-- Provide a longer summary of what this model is. -->
25
+
26
+
27
+
28
+ - **Developed by:** [More Information Needed]
29
+ - **Funded by [optional]:** [More Information Needed]
30
+ - **Shared by [optional]:** [More Information Needed]
31
+ - **Model type:** [More Information Needed]
32
+ - **Language(s) (NLP):** [More Information Needed]
33
+ - **License:** [More Information Needed]
34
+ - **Finetuned from model [optional]:** [More Information Needed]
35
+
36
+ ### Model Sources [optional]
37
+
38
+ <!-- Provide the basic links for the model. -->
39
+
40
+ - **Repository:** [More Information Needed]
41
+ - **Paper [optional]:** [More Information Needed]
42
+ - **Demo [optional]:** [More Information Needed]
43
+
44
+ ## Uses
45
+
46
+ <!-- Address questions around how the model is intended to be used, including the foreseeable users of the model and those affected by the model. -->
47
+
48
+ ### Direct Use
49
+
50
+ <!-- This section is for the model use without fine-tuning or plugging into a larger ecosystem/app. -->
51
+
52
+ [More Information Needed]
53
+
54
+ ### Downstream Use [optional]
55
+
56
+ <!-- This section is for the model use when fine-tuned for a task, or when plugged into a larger ecosystem/app -->
57
+
58
+ [More Information Needed]
59
+
60
+ ### Out-of-Scope Use
61
+
62
+ <!-- This section addresses misuse, malicious use, and uses that the model will not work well for. -->
63
+
64
+ [More Information Needed]
65
+
66
+ ## Bias, Risks, and Limitations
67
+
68
+ <!-- This section is meant to convey both technical and sociotechnical limitations. -->
69
+
70
+ [More Information Needed]
71
+
72
+ ### Recommendations
73
+
74
+ <!-- This section is meant to convey recommendations with respect to the bias, risk, and technical limitations. -->
75
+
76
+ Users (both direct and downstream) should be made aware of the risks, biases and limitations of the model. More information needed for further recommendations.
77
+
78
+ ## How to Get Started with the Model
79
+
80
+ Use the code below to get started with the model.
81
+
82
+ [More Information Needed]
83
+
84
+ ## Training Details
85
+
86
+ ### Training Data
87
+
88
+ <!-- This should link to a Dataset Card, perhaps with a short stub of information on what the training data is all about as well as documentation related to data pre-processing or additional filtering. -->
89
+
90
+ [More Information Needed]
91
+
92
+ ### Training Procedure
93
+
94
+ <!-- This relates heavily to the Technical Specifications. Content here should link to that section when it is relevant to the training procedure. -->
95
+
96
+ #### Preprocessing [optional]
97
+
98
+ [More Information Needed]
99
+
100
+
101
+ #### Training Hyperparameters
102
+
103
+ - **Training regime:** [More Information Needed] <!--fp32, fp16 mixed precision, bf16 mixed precision, bf16 non-mixed precision, fp16 non-mixed precision, fp8 mixed precision -->
104
+
105
+ #### Speeds, Sizes, Times [optional]
106
+
107
+ <!-- This section provides information about throughput, start/end time, checkpoint size if relevant, etc. -->
108
+
109
+ [More Information Needed]
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
110
 
111
  ## Evaluation
112
 
113
+ <!-- This section describes the evaluation protocols and provides the results. -->
114
+
115
+ ### Testing Data, Factors & Metrics
116
+
117
+ #### Testing Data
118
+
119
+ <!-- This should link to a Dataset Card if possible. -->
120
+
121
+ [More Information Needed]
122
+
123
+ #### Factors
124
+
125
+ <!-- These are the things the evaluation is disaggregating by, e.g., subpopulations or domains. -->
126
+
127
+ [More Information Needed]
128
+
129
+ #### Metrics
130
+
131
+ <!-- These are the evaluation metrics being used, ideally with a description of why. -->
132
+
133
+ [More Information Needed]
134
+
135
+ ### Results
136
+
137
+ [More Information Needed]
138
+
139
+ #### Summary
140
+
141
+
142
+
143
+ ## Model Examination [optional]
144
+
145
+ <!-- Relevant interpretability work for the model goes here -->
146
+
147
+ [More Information Needed]
148
+
149
+ ## Environmental Impact
150
+
151
+ <!-- Total emissions (in grams of CO2eq) and additional considerations, such as electricity usage, go here. Edit the suggested text below accordingly -->
152
+
153
+ Carbon emissions can be estimated using the [Machine Learning Impact calculator](https://mlco2.github.io/impact#compute) presented in [Lacoste et al. (2019)](https://arxiv.org/abs/1910.09700).
154
+
155
+ - **Hardware Type:** [More Information Needed]
156
+ - **Hours used:** [More Information Needed]
157
+ - **Cloud Provider:** [More Information Needed]
158
+ - **Compute Region:** [More Information Needed]
159
+ - **Carbon Emitted:** [More Information Needed]
160
+
161
+ ## Technical Specifications [optional]
162
+
163
+ ### Model Architecture and Objective
164
+
165
+ [More Information Needed]
166
+
167
+ ### Compute Infrastructure
168
+
169
+ [More Information Needed]
170
+
171
+ #### Hardware
172
+
173
+ [More Information Needed]
174
+
175
+ #### Software
176
+
177
+ [More Information Needed]
178
+
179
+ ## Citation [optional]
180
+
181
+ <!-- If there is a paper or blog post introducing the model, the APA and Bibtex information for that should go in this section. -->
182
+
183
+ **BibTeX:**
184
+
185
+ [More Information Needed]
186
+
187
+ **APA:**
188
+
189
+ [More Information Needed]
190
+
191
+ ## Glossary [optional]
192
+
193
+ <!-- If relevant, include terms and calculations in this section that can help readers understand the model or model card. -->
194
+
195
+ [More Information Needed]
196
+
197
+ ## More Information [optional]
198
+
199
+ [More Information Needed]
200
+
201
+ ## Model Card Authors [optional]
202
+
203
+ [More Information Needed]
204
+
205
+ ## Model Card Contact
206
+
207
+ [More Information Needed]
208
+ ### Framework versions
209
+
210
+ - PEFT 0.19.1