Text Generation
Transformers
Safetensors
biomedical
genomics
variant-interpretation
lora
clinical-genomics
bioinformatics
research
conversational
Instructions to use Babajaan/KAU-BioMedLLM with libraries, inference providers, notebooks, and local apps. Follow these links to get started.
- Libraries
- Transformers
How to use Babajaan/KAU-BioMedLLM with Transformers:
# Use a pipeline as a high-level helper from transformers import pipeline pipe = pipeline("text-generation", model="Babajaan/KAU-BioMedLLM") messages = [ {"role": "user", "content": "Who are you?"}, ] pipe(messages)# Load model directly from transformers import AutoModel model = AutoModel.from_pretrained("Babajaan/KAU-BioMedLLM", device_map="auto") - Notebooks
- Google Colab
- Kaggle
- Local Apps Settings
- vLLM
How to use Babajaan/KAU-BioMedLLM with vLLM:
Install from pip and serve model
# Install vLLM from pip: pip install vllm # Start the vLLM server: vllm serve "Babajaan/KAU-BioMedLLM" # Call the server using curl (OpenAI-compatible API): curl -X POST "http://localhost:8000/v1/chat/completions" \ -H "Content-Type: application/json" \ --data '{ "model": "Babajaan/KAU-BioMedLLM", "messages": [ { "role": "user", "content": "What is the capital of France?" } ] }'Use Docker
docker model run hf.co/Babajaan/KAU-BioMedLLM
- SGLang
How to use Babajaan/KAU-BioMedLLM with SGLang:
Install from pip and serve model
# Install SGLang from pip: pip install sglang # Start the SGLang server: python3 -m sglang.launch_server \ --model-path "Babajaan/KAU-BioMedLLM" \ --host 0.0.0.0 \ --port 30000 # Call the server using curl (OpenAI-compatible API): curl -X POST "http://localhost:30000/v1/chat/completions" \ -H "Content-Type: application/json" \ --data '{ "model": "Babajaan/KAU-BioMedLLM", "messages": [ { "role": "user", "content": "What is the capital of France?" } ] }'Use Docker images
docker run --gpus all \ --shm-size 32g \ -p 30000:30000 \ -v ~/.cache/huggingface:/root/.cache/huggingface \ --env "HF_TOKEN=<secret>" \ --ipc=host \ lmsysorg/sglang:latest \ python3 -m sglang.launch_server \ --model-path "Babajaan/KAU-BioMedLLM" \ --host 0.0.0.0 \ --port 30000 # Call the server using curl (OpenAI-compatible API): curl -X POST "http://localhost:30000/v1/chat/completions" \ -H "Content-Type: application/json" \ --data '{ "model": "Babajaan/KAU-BioMedLLM", "messages": [ { "role": "user", "content": "What is the capital of France?" } ] }' - Docker Model Runner
How to use Babajaan/KAU-BioMedLLM with Docker Model Runner:
docker model run hf.co/Babajaan/KAU-BioMedLLM
Replace root adapter with Llama-3.1-8B v0.2 LoRA adapter
Browse files
README.md
CHANGED
|
@@ -1,335 +1,207 @@
|
|
| 1 |
---
|
| 2 |
-
license: llama3.1
|
| 3 |
base_model: meta-llama/Llama-3.1-8B-Instruct
|
| 4 |
-
|
| 5 |
-
- biomedical
|
| 6 |
-
- genomics
|
| 7 |
-
- variant-interpretation
|
| 8 |
-
- lora
|
| 9 |
-
- clinical-genomics
|
| 10 |
-
- bioinformatics
|
| 11 |
-
- research
|
| 12 |
-
library_name: transformers
|
| 13 |
pipeline_tag: text-generation
|
|
|
|
|
|
|
|
|
|
|
|
|
| 14 |
---
|
| 15 |
|
| 16 |
-
# Model Card for
|
| 17 |
|
| 18 |
-
|
| 19 |
|
| 20 |
-
This repository does **not** redistribute the full Meta Llama-3.1-8B-Instruct base model. Users must separately have access to the base model according to the Meta Llama 3.1 license terms.
|
| 21 |
|
| 22 |
-
## Table of Contents
|
| 23 |
-
|
| 24 |
-
- [Model Details](#model-details)
|
| 25 |
-
- [Model Description](#model-description)
|
| 26 |
-
- [System Overview](#system-overview)
|
| 27 |
-
- [Uses](#uses)
|
| 28 |
-
- [Out-of-Scope Use](#out-of-scope-use)
|
| 29 |
-
- [Training and Development Data](#training-and-development-data)
|
| 30 |
-
- [Training Procedure](#training-procedure)
|
| 31 |
-
- [Evaluation](#evaluation)
|
| 32 |
-
- [Example Guarded Report](#example-guarded-report)
|
| 33 |
-
- [Limitations](#limitations)
|
| 34 |
-
- [How to Load the Adapter](#how-to-load-the-adapter)
|
| 35 |
-
- [Compute Infrastructure](#compute-infrastructure)
|
| 36 |
-
- [Ethical and Safety Considerations](#ethical-and-safety-considerations)
|
| 37 |
-
- [Citation and Acknowledgement](#citation-and-acknowledgement)
|
| 38 |
|
| 39 |
## Model Details
|
| 40 |
|
| 41 |
-
|
| 42 |
-
- **Repository:** `Babajaan/KAU-BioMedLLM`
|
| 43 |
-
- **Developed by:** Babajan B, King Abdulaziz University research environment
|
| 44 |
-
- **Model type:** Biomedical instruction-tuned LoRA adapter for report generation
|
| 45 |
-
- **Primary base model:** `meta-llama/Llama-3.1-8B-Instruct`
|
| 46 |
-
- **Prototype baseline:** `Qwen/Qwen2.5-1.5B-Instruct`
|
| 47 |
-
- **Language:** English
|
| 48 |
-
- **Domain:** Biomedical variant interpretation, clinical genomics research, bioinformatics evidence synthesis
|
| 49 |
-
- **Release type:** Research-use adapter release
|
| 50 |
-
- **Clinical status:** Not clinically validated; not for diagnosis, treatment, or patient-management decisions
|
| 51 |
-
|
| 52 |
-
## Model Description
|
| 53 |
|
| 54 |
-
|
| 55 |
|
| 56 |
-
1. **Independent score model:** a label-free machine learning model for variant scoring and temporal benchmarking.
|
| 57 |
-
2. **LLM report generator:** a LoRA-adapted instruction model for structured biomedical explanation.
|
| 58 |
|
| 59 |
-
The central design choice is to avoid treating LLM-generated prose as a calibrated pathogenicity score. The numeric score and the narrative interpretation are separated, and the report-generation layer is guarded by schema validation, citation checks, and abstention rules.
|
| 60 |
|
| 61 |
-
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 62 |
|
| 63 |
-
|
| 64 |
|
| 65 |
-
-
|
| 66 |
-
- PubMed and biomedical literature evidence for gene and phenotype context.
|
| 67 |
-
- UniProt for protein/gene functional evidence.
|
| 68 |
-
- AlphaFold structure information for residue-level structural context where mapping is reliable.
|
| 69 |
-
- Ensembl/VEP-style transcript and protein residue mapping.
|
| 70 |
-
- A guarded report pipeline that enforces JSON structure, citation support, and abstention when evidence is missing or ambiguous.
|
| 71 |
|
| 72 |
-
|
|
|
|
|
|
|
| 73 |
|
| 74 |
## Uses
|
| 75 |
|
| 76 |
-
|
| 77 |
|
| 78 |
-
|
| 79 |
|
| 80 |
-
-
|
| 81 |
-
- genomics and bioinformatics report prototyping;
|
| 82 |
-
- source-grounded biomedical evidence synthesis;
|
| 83 |
-
- evaluating guarded LLM reporting pipelines;
|
| 84 |
-
- studying leakage-aware score model design and temporal validation.
|
| 85 |
|
| 86 |
-
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 87 |
|
| 88 |
-
|
| 89 |
|
| 90 |
-
|
| 91 |
|
| 92 |
-
|
| 93 |
|
| 94 |
-
|
| 95 |
-
- variant prioritization interfaces;
|
| 96 |
-
- guarded medical LLM output;
|
| 97 |
-
- separation of statistical score models from narrative explanation;
|
| 98 |
-
- biomedical uncertainty and abstention behavior.
|
| 99 |
|
| 100 |
-
|
| 101 |
|
| 102 |
-
|
| 103 |
|
| 104 |
-
|
| 105 |
-
- a substitute for expert variant curation;
|
| 106 |
-
- a medical advice generator;
|
| 107 |
-
- a system for patient-management or treatment decisions;
|
| 108 |
-
- a standalone pathogenicity classifier for clinical reporting;
|
| 109 |
-
- a validated replacement for ACMG/AMP interpretation workflows.
|
| 110 |
|
| 111 |
-
|
| 112 |
|
| 113 |
-
|
| 114 |
|
| 115 |
-
|
| 116 |
-
- PubMed/literature-derived evidence examples;
|
| 117 |
-
- UniProt protein/gene evidence;
|
| 118 |
-
- AlphaFold structural evidence for selected proteins;
|
| 119 |
-
- Ensembl/VEP-style transcript and residue mapping outputs;
|
| 120 |
-
- internally generated structured instruction examples for report generation.
|
| 121 |
|
| 122 |
-
|
| 123 |
|
| 124 |
-
|
| 125 |
|
| 126 |
-
|
| 127 |
|
| 128 |
-
The report-generation model was trained as a LoRA adapter rather than as a full base-model retraining run.
|
| 129 |
|
| 130 |
-
|
| 131 |
|
| 132 |
-
- **
|
| 133 |
-
- **Llama-3.1-8B-Instruct v0.2:** stronger report-generation baseline selected for improved biomedical reasoning capacity and structured report generation.
|
| 134 |
|
| 135 |
-
|
|
|
|
|
|
|
|
|
|
|
|
|
| 136 |
|
| 137 |
## Evaluation
|
| 138 |
|
| 139 |
-
|
| 140 |
-
|
| 141 |
-
###
|
| 142 |
-
|
| 143 |
-
|
| 144 |
-
|
| 145 |
-
-
|
| 146 |
-
|
| 147 |
-
|
| 148 |
-
|
| 149 |
-
|
| 150 |
-
|
| 151 |
-
|
| 152 |
-
|
| 153 |
-
|
| 154 |
-
|
| 155 |
-
|
| 156 |
-
|
| 157 |
-
|
| 158 |
-
|
| 159 |
-
|
| 160 |
-
|
| 161 |
-
###
|
| 162 |
-
|
| 163 |
-
|
| 164 |
-
|
| 165 |
-
|
| 166 |
-
|
| 167 |
-
|
| 168 |
-
|
| 169 |
-
|
| 170 |
-
|
| 171 |
-
|
| 172 |
-
|
| 173 |
-
|
| 174 |
-
|
| 175 |
-
|
| 176 |
-
|
| 177 |
-
|
| 178 |
-
|
| 179 |
-
|
| 180 |
-
|
| 181 |
-
|
| 182 |
-
|
| 183 |
-
|
| 184 |
-
|
| 185 |
-
|
| 186 |
-
|
| 187 |
-
|
| 188 |
-
|
| 189 |
-
|
| 190 |
-
|
| 191 |
-
|
| 192 |
-
|
| 193 |
-
|
| 194 |
-
|
| 195 |
-
|
| 196 |
-
|
| 197 |
-
###
|
| 198 |
-
|
| 199 |
-
|
| 200 |
-
|
| 201 |
-
|
| 202 |
-
|
| 203 |
-
|
| 204 |
-
|
| 205 |
-
|
| 206 |
-
|
| 207 |
-
|
| 208 |
-
|
| 209 |
-
|
| 210 |
-
|
| 211 |
-
|
| 212 |
-
|
| 213 |
-
|
| 214 |
-
|
| 215 |
-
|
| 216 |
-
|
| 217 |
-
|
| 218 |
-
|
| 219 |
-
|
| 220 |
-
|
| 221 |
-
|
| 222 |
-
|
| 223 |
-
|
| 224 |
-
|
| 225 |
-
|
| 226 |
-
|
| 227 |
-
|
| 228 |
-
|
| 229 |
-
|
| 230 |
-
"source_ids": ["UniProt:P32245", "PMID:12646665", "PMID:32327598", "PMID:33858992"],
|
| 231 |
-
"structure_context": "Use only when transcript, protein accession, and residue mapping can be reconciled."
|
| 232 |
-
},
|
| 233 |
-
"guard_status": {
|
| 234 |
-
"citation_check": "pass",
|
| 235 |
-
"abstention_allowed": true,
|
| 236 |
-
"clinical_use": "not permitted"
|
| 237 |
-
}
|
| 238 |
-
}
|
| 239 |
-
```
|
| 240 |
-
|
| 241 |
-
Full guarded report examples and summaries are included in the repository under `reports/full_reports/`.
|
| 242 |
-
|
| 243 |
-
## Limitations
|
| 244 |
-
|
| 245 |
-
- The current evidence panel is limited and is not a genome-wide production knowledge base.
|
| 246 |
-
- Missense prediction remains below specialist predictors such as REVEL and AlphaMissense.
|
| 247 |
-
- Broad score model performance is partly driven by easier consequence classes.
|
| 248 |
-
- Structure evidence is only used when transcript/protein/residue mapping can be reconciled.
|
| 249 |
-
- Exact historical versions for some external resources require final manual verification before manuscript submission.
|
| 250 |
-
- The model has not been prospectively validated in clinical settings.
|
| 251 |
-
- Generated text can still contain errors and must be reviewed by domain experts.
|
| 252 |
-
- The uploaded artifact is an adapter, not a standalone full model.
|
| 253 |
-
|
| 254 |
-
## How to Load the Adapter
|
| 255 |
-
|
| 256 |
-
```python
|
| 257 |
-
from transformers import AutoModelForCausalLM, AutoTokenizer
|
| 258 |
-
from peft import PeftModel
|
| 259 |
-
import torch
|
| 260 |
-
|
| 261 |
-
base_model = "meta-llama/Llama-3.1-8B-Instruct"
|
| 262 |
-
adapter_model = "Babajaan/KAU-BioMedLLM"
|
| 263 |
-
|
| 264 |
-
tokenizer = AutoTokenizer.from_pretrained(base_model)
|
| 265 |
-
model = AutoModelForCausalLM.from_pretrained(
|
| 266 |
-
base_model,
|
| 267 |
-
torch_dtype=torch.float16,
|
| 268 |
-
device_map="auto",
|
| 269 |
-
)
|
| 270 |
-
model = PeftModel.from_pretrained(model, adapter_model)
|
| 271 |
-
model.eval()
|
| 272 |
-
|
| 273 |
-
messages = [
|
| 274 |
-
{
|
| 275 |
-
"role": "user",
|
| 276 |
-
"content": (
|
| 277 |
-
"For research use only, generate a structured biomedical variant "
|
| 278 |
-
"interpretation report for BRCA1 c.5096G>A p.Arg1699Gln. "
|
| 279 |
-
"Include uncertainty and do not provide clinical advice."
|
| 280 |
-
),
|
| 281 |
-
}
|
| 282 |
-
]
|
| 283 |
-
|
| 284 |
-
prompt = tokenizer.apply_chat_template(
|
| 285 |
-
messages,
|
| 286 |
-
tokenize=False,
|
| 287 |
-
add_generation_prompt=True,
|
| 288 |
-
)
|
| 289 |
-
inputs = tokenizer(prompt, return_tensors="pt").to(model.device)
|
| 290 |
-
|
| 291 |
-
with torch.no_grad():
|
| 292 |
-
outputs = model.generate(
|
| 293 |
-
**inputs,
|
| 294 |
-
max_new_tokens=700,
|
| 295 |
-
temperature=0.2,
|
| 296 |
-
do_sample=True,
|
| 297 |
-
)
|
| 298 |
-
|
| 299 |
-
print(tokenizer.decode(outputs[0], skip_special_tokens=True))
|
| 300 |
-
```
|
| 301 |
-
|
| 302 |
-
## Compute Infrastructure
|
| 303 |
-
|
| 304 |
-
The project was developed and evaluated using the King Abdulaziz University Aziz High Performance Computing environment. The workflow used the Aziz HPC software environment, PBS job scheduling, and GPU resources including A100 GPU jobs where available.
|
| 305 |
-
|
| 306 |
-
KAU Aziz HPC support resources:
|
| 307 |
-
|
| 308 |
-
- Aziz Supercomputer Support Center: https://hpcc-kau.com/support/
|
| 309 |
-
- PBS and GPU job support documentation are available through the Aziz HPC knowledge base.
|
| 310 |
-
|
| 311 |
-
## Ethical and Safety Considerations
|
| 312 |
-
|
| 313 |
-
Biomedical LLM systems can produce fluent but incorrect explanations. KAU-BioMedLLM therefore uses a guard-first design:
|
| 314 |
-
|
| 315 |
-
- numeric score and LLM narrative are separated;
|
| 316 |
-
- citations are required for biomedical claims;
|
| 317 |
-
- reports can abstain when evidence is insufficient;
|
| 318 |
-
- outputs are research-use only;
|
| 319 |
-
- no clinical decision should be made from model output.
|
| 320 |
-
|
| 321 |
-
Users should treat all outputs as draft research interpretations requiring expert review.
|
| 322 |
-
|
| 323 |
-
## Citation and Acknowledgement
|
| 324 |
-
|
| 325 |
-
If you use this model or the associated code/reports, please cite the forthcoming project manuscript or repository when available.
|
| 326 |
-
|
| 327 |
-
Manuscript status: in preparation. A formal citation will be added after manuscript submission or publication.
|
| 328 |
-
|
| 329 |
-
Suggested acknowledgement:
|
| 330 |
|
| 331 |
-
|
| 332 |
|
| 333 |
-
|
|
|
|
| 334 |
|
| 335 |
-
|
|
|
|
| 1 |
---
|
|
|
|
| 2 |
base_model: meta-llama/Llama-3.1-8B-Instruct
|
| 3 |
+
library_name: peft
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 4 |
pipeline_tag: text-generation
|
| 5 |
+
tags:
|
| 6 |
+
- base_model:adapter:meta-llama/Llama-3.1-8B-Instruct
|
| 7 |
+
- lora
|
| 8 |
+
- transformers
|
| 9 |
---
|
| 10 |
|
| 11 |
+
# Model Card for Model ID
|
| 12 |
|
| 13 |
+
<!-- Provide a quick summary of what the model is/does. -->
|
| 14 |
|
|
|
|
| 15 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 16 |
|
| 17 |
## Model Details
|
| 18 |
|
| 19 |
+
### Model Description
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 20 |
|
| 21 |
+
<!-- Provide a longer summary of what this model is. -->
|
| 22 |
|
|
|
|
|
|
|
| 23 |
|
|
|
|
| 24 |
|
| 25 |
+
- **Developed by:** [More Information Needed]
|
| 26 |
+
- **Funded by [optional]:** [More Information Needed]
|
| 27 |
+
- **Shared by [optional]:** [More Information Needed]
|
| 28 |
+
- **Model type:** [More Information Needed]
|
| 29 |
+
- **Language(s) (NLP):** [More Information Needed]
|
| 30 |
+
- **License:** [More Information Needed]
|
| 31 |
+
- **Finetuned from model [optional]:** [More Information Needed]
|
| 32 |
|
| 33 |
+
### Model Sources [optional]
|
| 34 |
|
| 35 |
+
<!-- Provide the basic links for the model. -->
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 36 |
|
| 37 |
+
- **Repository:** [More Information Needed]
|
| 38 |
+
- **Paper [optional]:** [More Information Needed]
|
| 39 |
+
- **Demo [optional]:** [More Information Needed]
|
| 40 |
|
| 41 |
## Uses
|
| 42 |
|
| 43 |
+
<!-- Address questions around how the model is intended to be used, including the foreseeable users of the model and those affected by the model. -->
|
| 44 |
|
| 45 |
+
### Direct Use
|
| 46 |
|
| 47 |
+
<!-- This section is for the model use without fine-tuning or plugging into a larger ecosystem/app. -->
|
|
|
|
|
|
|
|
|
|
|
|
|
| 48 |
|
| 49 |
+
[More Information Needed]
|
| 50 |
+
|
| 51 |
+
### Downstream Use [optional]
|
| 52 |
+
|
| 53 |
+
<!-- This section is for the model use when fine-tuned for a task, or when plugged into a larger ecosystem/app -->
|
| 54 |
+
|
| 55 |
+
[More Information Needed]
|
| 56 |
+
|
| 57 |
+
### Out-of-Scope Use
|
| 58 |
+
|
| 59 |
+
<!-- This section addresses misuse, malicious use, and uses that the model will not work well for. -->
|
| 60 |
+
|
| 61 |
+
[More Information Needed]
|
| 62 |
+
|
| 63 |
+
## Bias, Risks, and Limitations
|
| 64 |
+
|
| 65 |
+
<!-- This section is meant to convey both technical and sociotechnical limitations. -->
|
| 66 |
+
|
| 67 |
+
[More Information Needed]
|
| 68 |
+
|
| 69 |
+
### Recommendations
|
| 70 |
|
| 71 |
+
<!-- This section is meant to convey recommendations with respect to the bias, risk, and technical limitations. -->
|
| 72 |
|
| 73 |
+
Users (both direct and downstream) should be made aware of the risks, biases and limitations of the model. More information needed for further recommendations.
|
| 74 |
|
| 75 |
+
## How to Get Started with the Model
|
| 76 |
|
| 77 |
+
Use the code below to get started with the model.
|
|
|
|
|
|
|
|
|
|
|
|
|
| 78 |
|
| 79 |
+
[More Information Needed]
|
| 80 |
|
| 81 |
+
## Training Details
|
| 82 |
|
| 83 |
+
### Training Data
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 84 |
|
| 85 |
+
<!-- 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. -->
|
| 86 |
|
| 87 |
+
[More Information Needed]
|
| 88 |
|
| 89 |
+
### Training Procedure
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 90 |
|
| 91 |
+
<!-- This relates heavily to the Technical Specifications. Content here should link to that section when it is relevant to the training procedure. -->
|
| 92 |
|
| 93 |
+
#### Preprocessing [optional]
|
| 94 |
|
| 95 |
+
[More Information Needed]
|
| 96 |
|
|
|
|
| 97 |
|
| 98 |
+
#### Training Hyperparameters
|
| 99 |
|
| 100 |
+
- **Training regime:** [More Information Needed] <!--fp32, fp16 mixed precision, bf16 mixed precision, bf16 non-mixed precision, fp16 non-mixed precision, fp8 mixed precision -->
|
|
|
|
| 101 |
|
| 102 |
+
#### Speeds, Sizes, Times [optional]
|
| 103 |
+
|
| 104 |
+
<!-- This section provides information about throughput, start/end time, checkpoint size if relevant, etc. -->
|
| 105 |
+
|
| 106 |
+
[More Information Needed]
|
| 107 |
|
| 108 |
## Evaluation
|
| 109 |
|
| 110 |
+
<!-- This section describes the evaluation protocols and provides the results. -->
|
| 111 |
+
|
| 112 |
+
### Testing Data, Factors & Metrics
|
| 113 |
+
|
| 114 |
+
#### Testing Data
|
| 115 |
+
|
| 116 |
+
<!-- This should link to a Dataset Card if possible. -->
|
| 117 |
+
|
| 118 |
+
[More Information Needed]
|
| 119 |
+
|
| 120 |
+
#### Factors
|
| 121 |
+
|
| 122 |
+
<!-- These are the things the evaluation is disaggregating by, e.g., subpopulations or domains. -->
|
| 123 |
+
|
| 124 |
+
[More Information Needed]
|
| 125 |
+
|
| 126 |
+
#### Metrics
|
| 127 |
+
|
| 128 |
+
<!-- These are the evaluation metrics being used, ideally with a description of why. -->
|
| 129 |
+
|
| 130 |
+
[More Information Needed]
|
| 131 |
+
|
| 132 |
+
### Results
|
| 133 |
+
|
| 134 |
+
[More Information Needed]
|
| 135 |
+
|
| 136 |
+
#### Summary
|
| 137 |
+
|
| 138 |
+
|
| 139 |
+
|
| 140 |
+
## Model Examination [optional]
|
| 141 |
+
|
| 142 |
+
<!-- Relevant interpretability work for the model goes here -->
|
| 143 |
+
|
| 144 |
+
[More Information Needed]
|
| 145 |
+
|
| 146 |
+
## Environmental Impact
|
| 147 |
+
|
| 148 |
+
<!-- Total emissions (in grams of CO2eq) and additional considerations, such as electricity usage, go here. Edit the suggested text below accordingly -->
|
| 149 |
+
|
| 150 |
+
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).
|
| 151 |
+
|
| 152 |
+
- **Hardware Type:** [More Information Needed]
|
| 153 |
+
- **Hours used:** [More Information Needed]
|
| 154 |
+
- **Cloud Provider:** [More Information Needed]
|
| 155 |
+
- **Compute Region:** [More Information Needed]
|
| 156 |
+
- **Carbon Emitted:** [More Information Needed]
|
| 157 |
+
|
| 158 |
+
## Technical Specifications [optional]
|
| 159 |
+
|
| 160 |
+
### Model Architecture and Objective
|
| 161 |
+
|
| 162 |
+
[More Information Needed]
|
| 163 |
+
|
| 164 |
+
### Compute Infrastructure
|
| 165 |
+
|
| 166 |
+
[More Information Needed]
|
| 167 |
+
|
| 168 |
+
#### Hardware
|
| 169 |
+
|
| 170 |
+
[More Information Needed]
|
| 171 |
+
|
| 172 |
+
#### Software
|
| 173 |
+
|
| 174 |
+
[More Information Needed]
|
| 175 |
+
|
| 176 |
+
## Citation [optional]
|
| 177 |
+
|
| 178 |
+
<!-- If there is a paper or blog post introducing the model, the APA and Bibtex information for that should go in this section. -->
|
| 179 |
+
|
| 180 |
+
**BibTeX:**
|
| 181 |
+
|
| 182 |
+
[More Information Needed]
|
| 183 |
+
|
| 184 |
+
**APA:**
|
| 185 |
+
|
| 186 |
+
[More Information Needed]
|
| 187 |
+
|
| 188 |
+
## Glossary [optional]
|
| 189 |
+
|
| 190 |
+
<!-- If relevant, include terms and calculations in this section that can help readers understand the model or model card. -->
|
| 191 |
+
|
| 192 |
+
[More Information Needed]
|
| 193 |
+
|
| 194 |
+
## More Information [optional]
|
| 195 |
+
|
| 196 |
+
[More Information Needed]
|
| 197 |
+
|
| 198 |
+
## Model Card Authors [optional]
|
| 199 |
+
|
| 200 |
+
[More Information Needed]
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 201 |
|
| 202 |
+
## Model Card Contact
|
| 203 |
|
| 204 |
+
[More Information Needed]
|
| 205 |
+
### Framework versions
|
| 206 |
|
| 207 |
+
- PEFT 0.19.1
|