Platypus Models by garage-bAInd
About
The Platypus family is a series of cutting-edge large language models (LLMs) developed by researchers at Boston University, achieving top performance on Hugging Face's Open LLM Leaderboard. These models are characterized by their impactful use of the Open-Platypus dataset, a curated collection focusing on STEM and logic, which enables high performance with minimal fine-tuning. By integrating Low-Rank Adaptation (LoRA) modules, Platypus models effectively combine pre-trained strengths with domain-specific insights. This innovative approach facilitates significant reductions in training time and resource usage, as a 13B Platypus model can be trained in just 5 hours using a single A100 GPU. Furthermore, the research team has addressed data contamination issues during training to ensure reliable outcomes. 123.
Current Variants
Use-when guidance is derived from seed capabilities, context, release, and replacement fields.
Use when the workload needs 2k context and 30B parameters.
| Model | Use when | Released | Signals | Status |
|---|---|---|---|---|
| Platypus 30B | Use when the workload needs 2k context and 30B parameters. | 2023-07 | 2k context30B parameters | Current |
Release Timeline
1 release groupSpecifications(1 models)
| Model | Released | Context | Parameters |
|---|---|---|---|
| Platypus 30B | 2023-07 | 2k | 30B |
Frequently Asked Questions
- What is Platypus used for?
- The Platypus family is a series of cutting-edge large language models (LLMs) developed by researchers at Boston University, achieving top performance on Hugging Face's Open LLM Leaderboard.
- How does Platypus compare to Platypus2?
- Platypus by garage-bAInd is strongest where you need its listed use cases, while Platypus2 by garage-bAInd is the closest related family to check for structured outputs. Platypus has 1 listed variant and reaches up to 2k context, so compare the specs and pricing tables before choosing a production model.
- Which Platypus model should I use?
- If price is the main constraint, use the pricing table first because Platypus does not have complete provider pricing in the local data. For the most capable/latest local choice, evaluate Platypus 30B with 2k context.
