Daemontatox commited on
Commit
ff16650
·
verified ·
1 Parent(s): b12e145

Update README.md

Browse files
Files changed (1) hide show
  1. README.md +194 -349
README.md CHANGED
@@ -1,355 +1,200 @@
1
  ---
2
- library_name: transformers
3
- license: apache-2.0
4
- license_link: https://huggingface.co/Qwen/Qwen3-30B-A3B/blob/main/LICENSE
5
- pipeline_tag: text-generation
6
- base_model:
7
- - Qwen/Qwen3-30B-A3B-Base
8
  ---
9
 
10
- # Qwen3-30B-A3B
11
- <a href="https://chat.qwen.ai/" target="_blank" style="margin: 2px;">
12
- <img alt="Chat" src="https://img.shields.io/badge/%F0%9F%92%9C%EF%B8%8F%20Qwen%20Chat%20-536af5" style="display: inline-block; vertical-align: middle;"/>
13
- </a>
14
-
15
- ## Qwen3 Highlights
16
-
17
- Qwen3 is the latest generation of large language models in Qwen series, offering a comprehensive suite of dense and mixture-of-experts (MoE) models. Built upon extensive training, Qwen3 delivers groundbreaking advancements in reasoning, instruction-following, agent capabilities, and multilingual support, with the following key features:
18
-
19
- - **Uniquely support of seamless switching between thinking mode** (for complex logical reasoning, math, and coding) and **non-thinking mode** (for efficient, general-purpose dialogue) **within single model**, ensuring optimal performance across various scenarios.
20
- - **Significantly enhancement in its reasoning capabilities**, surpassing previous QwQ (in thinking mode) and Qwen2.5 instruct models (in non-thinking mode) on mathematics, code generation, and commonsense logical reasoning.
21
- - **Superior human preference alignment**, excelling in creative writing, role-playing, multi-turn dialogues, and instruction following, to deliver a more natural, engaging, and immersive conversational experience.
22
- - **Expertise in agent capabilities**, enabling precise integration with external tools in both thinking and unthinking modes and achieving leading performance among open-source models in complex agent-based tasks.
23
- - **Support of 100+ languages and dialects** with strong capabilities for **multilingual instruction following** and **translation**.
24
-
25
- ## Model Overview
26
-
27
- **Qwen3-30B-A3B** has the following features:
28
- - Type: Causal Language Models
29
- - Training Stage: Pretraining & Post-training
30
- - Number of Parameters: 30.5B in total and 3.3B activated
31
- - Number of Paramaters (Non-Embedding): 29.9B
32
- - Number of Layers: 48
33
- - Number of Attention Heads (GQA): 32 for Q and 4 for KV
34
- - Number of Experts: 128
35
- - Number of Activated Experts: 8
36
- - Context Length: 32,768 natively and [131,072 tokens with YaRN](#processing-long-texts).
37
-
38
- For more details, including benchmark evaluation, hardware requirements, and inference performance, please refer to our [blog](https://qwenlm.github.io/blog/qwen3/), [GitHub](https://github.com/QwenLM/Qwen3), and [Documentation](https://qwen.readthedocs.io/en/latest/).
39
-
40
- ## Quickstart
41
-
42
- The code of Qwen3-MoE has been in the latest Hugging Face `transformers` and we advise you to use the latest version of `transformers`.
43
-
44
- With `transformers<4.51.0`, you will encounter the following error:
45
- ```
46
- KeyError: 'qwen3_moe'
47
- ```
48
-
49
- The following contains a code snippet illustrating how to use the model generate content based on given inputs.
50
- ```python
51
- from transformers import AutoModelForCausalLM, AutoTokenizer
52
-
53
- model_name = "Qwen/Qwen3-30B-A3B"
54
-
55
- # load the tokenizer and the model
56
- tokenizer = AutoTokenizer.from_pretrained(model_name)
57
- model = AutoModelForCausalLM.from_pretrained(
58
- model_name,
59
- torch_dtype="auto",
60
- device_map="auto"
61
- )
62
 
63
- # prepare the model input
64
- prompt = "Give me a short introduction to large language model."
65
- messages = [
66
- {"role": "user", "content": prompt}
67
- ]
68
- text = tokenizer.apply_chat_template(
69
- messages,
70
- tokenize=False,
71
- add_generation_prompt=True,
72
- enable_thinking=True # Switches between thinking and non-thinking modes. Default is True.
73
- )
74
- model_inputs = tokenizer([text], return_tensors="pt").to(model.device)
75
 
76
- # conduct text completion
77
- generated_ids = model.generate(
78
- **model_inputs,
79
- max_new_tokens=32768
80
- )
81
- output_ids = generated_ids[0][len(model_inputs.input_ids[0]):].tolist()
82
-
83
- # parsing thinking content
84
- try:
85
- # rindex finding 151668 (</think>)
86
- index = len(output_ids) - output_ids[::-1].index(151668)
87
- except ValueError:
88
- index = 0
89
 
90
- thinking_content = tokenizer.decode(output_ids[:index], skip_special_tokens=True).strip("\n")
91
- content = tokenizer.decode(output_ids[index:], skip_special_tokens=True).strip("\n")
92
-
93
- print("thinking content:", thinking_content)
94
- print("content:", content)
95
- ```
96
-
97
- For deployment, you can use `sglang>=0.4.6.post1` or `vllm>=0.8.5` or to create an OpenAI-compatible API endpoint:
98
- - SGLang:
99
- ```shell
100
- python -m sglang.launch_server --model-path Qwen/Qwen3-30B-A3B --reasoning-parser qwen3
101
- ```
102
- - vLLM:
103
- ```shell
104
- vllm serve Qwen/Qwen3-30B-A3B --enable-reasoning --reasoning-parser deepseek_r1
105
- ```
106
-
107
- For local use, applications such as Ollama, LMStudio, MLX-LM, llama.cpp, and KTransformers have also supported Qwen3.
108
-
109
- ## Switching Between Thinking and Non-Thinking Mode
110
-
111
- > [!TIP]
112
- > The `enable_thinking` switch is also available in APIs created by SGLang and vLLM.
113
- > Please refer to our documentation for [SGLang](https://qwen.readthedocs.io/en/latest/deployment/sglang.html#thinking-non-thinking-modes) and [vLLM](https://qwen.readthedocs.io/en/latest/deployment/vllm.html#thinking-non-thinking-modes) users.
114
-
115
- ### `enable_thinking=True`
116
-
117
- By default, Qwen3 has thinking capabilities enabled, similar to QwQ-32B. This means the model will use its reasoning abilities to enhance the quality of generated responses. For example, when explicitly setting `enable_thinking=True` or leaving it as the default value in `tokenizer.apply_chat_template`, the model will engage its thinking mode.
118
-
119
- ```python
120
- text = tokenizer.apply_chat_template(
121
- messages,
122
- tokenize=False,
123
- add_generation_prompt=True,
124
- enable_thinking=True # True is the default value for enable_thinking
125
- )
126
- ```
127
-
128
- In this mode, the model will generate think content wrapped in a `<think>...</think>` block, followed by the final response.
129
-
130
- > [!NOTE]
131
- > For thinking mode, use `Temperature=0.6`, `TopP=0.95`, `TopK=20`, and `MinP=0` (the default setting in `generation_config.json`). **DO NOT use greedy decoding**, as it can lead to performance degradation and endless repetitions. For more detailed guidance, please refer to the [Best Practices](#best-practices) section.
132
-
133
-
134
- ### `enable_thinking=False`
135
-
136
- We provide a hard switch to strictly disable the model's thinking behavior, aligning its functionality with the previous Qwen2.5-Instruct models. This mode is particularly useful in scenarios where disabling thinking is essential for enhancing efficiency.
137
-
138
- ```python
139
- text = tokenizer.apply_chat_template(
140
- messages,
141
- tokenize=False,
142
- add_generation_prompt=True,
143
- enable_thinking=False # Setting enable_thinking=False disables thinking mode
144
- )
145
- ```
146
-
147
- In this mode, the model will not generate any think content and will not include a `<think>...</think>` block.
148
-
149
- > [!NOTE]
150
- > For non-thinking mode, we suggest using `Temperature=0.7`, `TopP=0.8`, `TopK=20`, and `MinP=0`. For more detailed guidance, please refer to the [Best Practices](#best-practices) section.
151
-
152
- ### Advanced Usage: Switching Between Thinking and Non-Thinking Modes via User Input
153
-
154
- We provide a soft switch mechanism that allows users to dynamically control the model's behavior when `enable_thinking=True`. Specifically, you can add `/think` and `/no_think` to user prompts or system messages to switch the model's thinking mode from turn to turn. The model will follow the most recent instruction in multi-turn conversations.
155
-
156
- Here is an example of a multi-turn conversation:
157
-
158
- ```python
159
- from transformers import AutoModelForCausalLM, AutoTokenizer
160
-
161
- class QwenChatbot:
162
- def __init__(self, model_name="Qwen/Qwen3-30B-A3B"):
163
- self.tokenizer = AutoTokenizer.from_pretrained(model_name)
164
- self.model = AutoModelForCausalLM.from_pretrained(model_name)
165
- self.history = []
166
-
167
- def generate_response(self, user_input):
168
- messages = self.history + [{"role": "user", "content": user_input}]
169
-
170
- text = self.tokenizer.apply_chat_template(
171
- messages,
172
- tokenize=False,
173
- add_generation_prompt=True
174
- )
175
-
176
- inputs = self.tokenizer(text, return_tensors="pt")
177
- response_ids = self.model.generate(**inputs, max_new_tokens=32768)[0][len(inputs.input_ids[0]):].tolist()
178
- response = self.tokenizer.decode(response_ids, skip_special_tokens=True)
179
-
180
- # Update history
181
- self.history.append({"role": "user", "content": user_input})
182
- self.history.append({"role": "assistant", "content": response})
183
-
184
- return response
185
-
186
- # Example Usage
187
- if __name__ == "__main__":
188
- chatbot = QwenChatbot()
189
-
190
- # First input (without /think or /no_think tags, thinking mode is enabled by default)
191
- user_input_1 = "How many r's in strawberries?"
192
- print(f"User: {user_input_1}")
193
- response_1 = chatbot.generate_response(user_input_1)
194
- print(f"Bot: {response_1}")
195
- print("----------------------")
196
-
197
- # Second input with /no_think
198
- user_input_2 = "Then, how many r's in blueberries? /no_think"
199
- print(f"User: {user_input_2}")
200
- response_2 = chatbot.generate_response(user_input_2)
201
- print(f"Bot: {response_2}")
202
- print("----------------------")
203
-
204
- # Third input with /think
205
- user_input_3 = "Really? /think"
206
- print(f"User: {user_input_3}")
207
- response_3 = chatbot.generate_response(user_input_3)
208
- print(f"Bot: {response_3}")
209
- ```
210
-
211
- > [!NOTE]
212
- > For API compatibility, when `enable_thinking=True`, regardless of whether the user uses `/think` or `/no_think`, the model will always output a block wrapped in `<think>...</think>`. However, the content inside this block may be empty if thinking is disabled.
213
- > When `enable_thinking=False`, the soft switches are not valid. Regardless of any `/think` or `/no_think` tags input by the user, the model will not generate think content and will not include a `<think>...</think>` block.
214
-
215
- ## Agentic Use
216
-
217
- Qwen3 excels in tool calling capabilities. We recommend using [Qwen-Agent](https://github.com/QwenLM/Qwen-Agent) to make the best use of agentic ability of Qwen3. Qwen-Agent encapsulates tool-calling templates and tool-calling parsers internally, greatly reducing coding complexity.
218
-
219
- To define the available tools, you can use the MCP configuration file, use the integrated tool of Qwen-Agent, or integrate other tools by yourself.
220
- ```python
221
- from qwen_agent.agents import Assistant
222
-
223
- # Define LLM
224
- llm_cfg = {
225
- 'model': 'Qwen3-30B-A3B',
226
-
227
- # Use the endpoint provided by Alibaba Model Studio:
228
- # 'model_type': 'qwen_dashscope',
229
- # 'api_key': os.getenv('DASHSCOPE_API_KEY'),
230
-
231
- # Use a custom endpoint compatible with OpenAI API:
232
- 'model_server': 'http://localhost:8000/v1', # api_base
233
- 'api_key': 'EMPTY',
234
-
235
- # Other parameters:
236
- # 'generate_cfg': {
237
- # # Add: When the response content is `<think>this is the thought</think>this is the answer;
238
- # # Do not add: When the response has been separated by reasoning_content and content.
239
- # 'thought_in_content': True,
240
- # },
241
- }
242
-
243
- # Define Tools
244
- tools = [
245
- {'mcpServers': { # You can specify the MCP configuration file
246
- 'time': {
247
- 'command': 'uvx',
248
- 'args': ['mcp-server-time', '--local-timezone=Asia/Shanghai']
249
- },
250
- "fetch": {
251
- "command": "uvx",
252
- "args": ["mcp-server-fetch"]
253
- }
254
- }
255
- },
256
- 'code_interpreter', # Built-in tools
257
- ]
258
-
259
- # Define Agent
260
- bot = Assistant(llm=llm_cfg, function_list=tools)
261
-
262
- # Streaming generation
263
- messages = [{'role': 'user', 'content': 'https://qwenlm.github.io/blog/ Introduce the latest developments of Qwen'}]
264
- for responses in bot.run(messages=messages):
265
- pass
266
- print(responses)
267
- ```
268
-
269
- ## Processing Long Texts
270
-
271
- Qwen3 natively supports context lengths of up to 32,768 tokens. For conversations where the total length (including both input and output) significantly exceeds this limit, we recommend using RoPE scaling techniques to handle long texts effectively. We have validated the model's performance on context lengths of up to 131,072 tokens using the [YaRN](https://arxiv.org/abs/2309.00071) method.
272
-
273
- YaRN is currently supported by several inference frameworks, e.g., `transformers` and `llama.cpp` for local use, `vllm` and `sglang` for deployment. In general, there are two approaches to enabling YaRN for supported frameworks:
274
-
275
- - Modifying the model files:
276
- In the `config.json` file, add the `rope_scaling` fields:
277
- ```json
278
- {
279
- ...,
280
- "rope_scaling": {
281
- "rope_type": "yarn",
282
- "factor": 4.0,
283
- "original_max_position_embeddings": 32768
284
- }
285
- }
286
- ```
287
- For `llama.cpp`, you need to regenerate the GGUF file after the modification.
288
-
289
- - Passing command line arguments:
290
-
291
- For `vllm`, you can use
292
- ```shell
293
- vllm serve ... --rope-scaling '{"rope_type":"yarn","factor":4.0,"original_max_position_embeddings":32768}' --max-model-len 131072
294
- ```
295
-
296
- For `sglang`, you can use
297
- ```shell
298
- python -m sglang.launch_server ... --json-model-override-args '{"rope_scaling":{"rope_type":"yarn","factor":4.0,"original_max_position_embeddings":32768}}'
299
- ```
300
-
301
- For `llama-server` from `llama.cpp`, you can use
302
- ```shell
303
- llama-server ... --rope-scaling yarn --rope-scale 4 --yarn-orig-ctx 32768
304
- ```
305
-
306
- > [!IMPORTANT]
307
- > If you encounter the following warning
308
- > ```
309
- > Unrecognized keys in `rope_scaling` for 'rope_type'='yarn': {'original_max_position_embeddings'}
310
- > ```
311
- > please upgrade `transformers>=4.51.0`.
312
-
313
- > [!NOTE]
314
- > All the notable open-source frameworks implement static YaRN, which means the scaling factor remains constant regardless of input length, **potentially impacting performance on shorter texts.**
315
- > We advise adding the `rope_scaling` configuration only when processing long contexts is required.
316
- > It is also recommended to modify the `factor` as needed. For example, if the typical context length for your application is 65,536 tokens, it would be better to set `factor` as 2.0.
317
-
318
- > [!NOTE]
319
- > The default `max_position_embeddings` in `config.json` is set to 40,960. This allocation includes reserving 32,768 tokens for outputs and 8,192 tokens for typical prompts, which is sufficient for most scenarios involving short text processing. If the average context length does not exceed 32,768 tokens, we do not recommend enabling YaRN in this scenario, as it may potentially degrade model performance.
320
-
321
- > [!TIP]
322
- > The endpoint provided by Alibaba Model Studio supports dynamic YaRN by default and no extra configuration is needed.
323
-
324
- ## Best Practices
325
-
326
- To achieve optimal performance, we recommend the following settings:
327
-
328
- 1. **Sampling Parameters**:
329
- - For thinking mode (`enable_thinking=True`), use `Temperature=0.6`, `TopP=0.95`, `TopK=20`, and `MinP=0`. **DO NOT use greedy decoding**, as it can lead to performance degradation and endless repetitions.
330
- - For non-thinking mode (`enable_thinking=False`), we suggest using `Temperature=0.7`, `TopP=0.8`, `TopK=20`, and `MinP=0`.
331
- - For supported frameworks, you can adjust the `presence_penalty` parameter between 0 and 2 to reduce endless repetitions. However, using a higher value may occasionally result in language mixing and a slight decrease in model performance.
332
-
333
- 2. **Adequate Output Length**: We recommend using an output length of 32,768 tokens for most queries. For benchmarking on highly complex problems, such as those found in math and programming competitions, we suggest setting the max output length to 38,912 tokens. This provides the model with sufficient space to generate detailed and comprehensive responses, thereby enhancing its overall performance.
334
-
335
- 3. **Standardize Output Format**: We recommend using prompts to standardize model outputs when benchmarking.
336
- - **Math Problems**: Include "Please reason step by step, and put your final answer within \boxed{}." in the prompt.
337
- - **Multiple-Choice Questions**: Add the following JSON structure to the prompt to standardize responses: "Please show your choice in the `answer` field with only the choice letter, e.g., `"answer": "C"`."
338
-
339
- 4. **No Thinking Content in History**: In multi-turn conversations, the historical model output should only include the final output part and does not need to include the thinking content. It is implemented in the provided chat template in Jinja2. However, for frameworks that do not directly use the Jinja2 chat template, it is up to the developers to ensure that the best practice is followed.
340
-
341
- ### Citation
342
-
343
- If you find our work helpful, feel free to give us a cite.
344
-
345
- ```
346
- @misc{qwen3technicalreport,
347
- title={Qwen3 Technical Report},
348
- author={Qwen Team},
349
- year={2025},
350
- eprint={2505.09388},
351
- archivePrefix={arXiv},
352
- primaryClass={cs.CL},
353
- url={https://arxiv.org/abs/2505.09388},
354
- }
355
- ```
 
1
  ---
2
+ # For reference on model card metadata, see the spec: https://github.com/huggingface/hub-docs/blob/main/modelcard.md?plain=1
3
+ # Doc / guide: https://huggingface.co/docs/hub/model-cards
4
+ {}
 
 
 
5
  ---
6
 
7
+ # Model Card for Model ID
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
8
 
9
+ <!-- Provide a quick summary of what the model is/does. -->
 
 
 
 
 
 
 
 
 
 
 
10
 
11
+ This modelcard aims to be a base template for new models. It has been generated using [this raw template](https://github.com/huggingface/huggingface_hub/blob/main/src/huggingface_hub/templates/modelcard_template.md?plain=1).
 
 
 
 
 
 
 
 
 
 
 
 
12
 
13
+ ## Model Details
14
+
15
+ ### Model Description
16
+
17
+ <!-- Provide a longer summary of what this model is. -->
18
+
19
+
20
+
21
+ - **Developed by:** [More Information Needed]
22
+ - **Funded by [optional]:** [More Information Needed]
23
+ - **Shared by [optional]:** [More Information Needed]
24
+ - **Model type:** [More Information Needed]
25
+ - **Language(s) (NLP):** [More Information Needed]
26
+ - **License:** [More Information Needed]
27
+ - **Finetuned from model [optional]:** [More Information Needed]
28
+
29
+ ### Model Sources [optional]
30
+
31
+ <!-- Provide the basic links for the model. -->
32
+
33
+ - **Repository:** [More Information Needed]
34
+ - **Paper [optional]:** [More Information Needed]
35
+ - **Demo [optional]:** [More Information Needed]
36
+
37
+ ## Uses
38
+
39
+ <!-- Address questions around how the model is intended to be used, including the foreseeable users of the model and those affected by the model. -->
40
+
41
+ ### Direct Use
42
+
43
+ <!-- This section is for the model use without fine-tuning or plugging into a larger ecosystem/app. -->
44
+
45
+ [More Information Needed]
46
+
47
+ ### Downstream Use [optional]
48
+
49
+ <!-- This section is for the model use when fine-tuned for a task, or when plugged into a larger ecosystem/app -->
50
+
51
+ [More Information Needed]
52
+
53
+ ### Out-of-Scope Use
54
+
55
+ <!-- This section addresses misuse, malicious use, and uses that the model will not work well for. -->
56
+
57
+ [More Information Needed]
58
+
59
+ ## Bias, Risks, and Limitations
60
+
61
+ <!-- This section is meant to convey both technical and sociotechnical limitations. -->
62
+
63
+ [More Information Needed]
64
+
65
+ ### Recommendations
66
+
67
+ <!-- This section is meant to convey recommendations with respect to the bias, risk, and technical limitations. -->
68
+
69
+ Users (both direct and downstream) should be made aware of the risks, biases and limitations of the model. More information needed for further recommendations.
70
+
71
+ ## How to Get Started with the Model
72
+
73
+ Use the code below to get started with the model.
74
+
75
+ [More Information Needed]
76
+
77
+ ## Training Details
78
+
79
+ ### Training Data
80
+
81
+ <!-- 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. -->
82
+
83
+ [More Information Needed]
84
+
85
+ ### Training Procedure
86
+
87
+ <!-- This relates heavily to the Technical Specifications. Content here should link to that section when it is relevant to the training procedure. -->
88
+
89
+ #### Preprocessing [optional]
90
+
91
+ [More Information Needed]
92
+
93
+
94
+ #### Training Hyperparameters
95
+
96
+ - **Training regime:** [More Information Needed] <!--fp32, fp16 mixed precision, bf16 mixed precision, bf16 non-mixed precision, fp16 non-mixed precision, fp8 mixed precision -->
97
+
98
+ #### Speeds, Sizes, Times [optional]
99
+
100
+ <!-- This section provides information about throughput, start/end time, checkpoint size if relevant, etc. -->
101
+
102
+ [More Information Needed]
103
+
104
+ ## Evaluation
105
+
106
+ <!-- This section describes the evaluation protocols and provides the results. -->
107
+
108
+ ### Testing Data, Factors & Metrics
109
+
110
+ #### Testing Data
111
+
112
+ <!-- This should link to a Dataset Card if possible. -->
113
+
114
+ [More Information Needed]
115
+
116
+ #### Factors
117
+
118
+ <!-- These are the things the evaluation is disaggregating by, e.g., subpopulations or domains. -->
119
+
120
+ [More Information Needed]
121
+
122
+ #### Metrics
123
+
124
+ <!-- These are the evaluation metrics being used, ideally with a description of why. -->
125
+
126
+ [More Information Needed]
127
+
128
+ ### Results
129
+
130
+ [More Information Needed]
131
+
132
+ #### Summary
133
+
134
+
135
+
136
+ ## Model Examination [optional]
137
+
138
+ <!-- Relevant interpretability work for the model goes here -->
139
+
140
+ [More Information Needed]
141
+
142
+ ## Environmental Impact
143
+
144
+ <!-- Total emissions (in grams of CO2eq) and additional considerations, such as electricity usage, go here. Edit the suggested text below accordingly -->
145
+
146
+ 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).
147
+
148
+ - **Hardware Type:** [More Information Needed]
149
+ - **Hours used:** [More Information Needed]
150
+ - **Cloud Provider:** [More Information Needed]
151
+ - **Compute Region:** [More Information Needed]
152
+ - **Carbon Emitted:** [More Information Needed]
153
+
154
+ ## Technical Specifications [optional]
155
+
156
+ ### Model Architecture and Objective
157
+
158
+ [More Information Needed]
159
+
160
+ ### Compute Infrastructure
161
+
162
+ [More Information Needed]
163
+
164
+ #### Hardware
165
+
166
+ [More Information Needed]
167
+
168
+ #### Software
169
+
170
+ [More Information Needed]
171
+
172
+ ## Citation [optional]
173
+
174
+ <!-- If there is a paper or blog post introducing the model, the APA and Bibtex information for that should go in this section. -->
175
+
176
+ **BibTeX:**
177
+
178
+ [More Information Needed]
179
+
180
+ **APA:**
181
+
182
+ [More Information Needed]
183
+
184
+ ## Glossary [optional]
185
+
186
+ <!-- If relevant, include terms and calculations in this section that can help readers understand the model or model card. -->
187
+
188
+ [More Information Needed]
189
+
190
+ ## More Information [optional]
191
+
192
+ [More Information Needed]
193
+
194
+ ## Model Card Authors [optional]
195
+
196
+ [More Information Needed]
197
+
198
+ ## Model Card Contact
199
+
200
+ [More Information Needed]