Instructions to use togethercomputer/GPT-JT-6B-v1 with libraries, inference providers, notebooks, and local apps. Follow these links to get started.
- Libraries
- Transformers
How to use togethercomputer/GPT-JT-6B-v1 with Transformers:
# Use a pipeline as a high-level helper from transformers import pipeline pipe = pipeline("text-generation", model="togethercomputer/GPT-JT-6B-v1")# Load model directly from transformers import AutoTokenizer, AutoModelForCausalLM tokenizer = AutoTokenizer.from_pretrained("togethercomputer/GPT-JT-6B-v1") model = AutoModelForCausalLM.from_pretrained("togethercomputer/GPT-JT-6B-v1") - Notebooks
- Google Colab
- Kaggle
- Local Apps
- vLLM
How to use togethercomputer/GPT-JT-6B-v1 with vLLM:
Install from pip and serve model
# Install vLLM from pip: pip install vllm # Start the vLLM server: vllm serve "togethercomputer/GPT-JT-6B-v1" # Call the server using curl (OpenAI-compatible API): curl -X POST "http://localhost:8000/v1/completions" \ -H "Content-Type: application/json" \ --data '{ "model": "togethercomputer/GPT-JT-6B-v1", "prompt": "Once upon a time,", "max_tokens": 512, "temperature": 0.5 }'Use Docker
docker model run hf.co/togethercomputer/GPT-JT-6B-v1
- SGLang
How to use togethercomputer/GPT-JT-6B-v1 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 "togethercomputer/GPT-JT-6B-v1" \ --host 0.0.0.0 \ --port 30000 # Call the server using curl (OpenAI-compatible API): curl -X POST "http://localhost:30000/v1/completions" \ -H "Content-Type: application/json" \ --data '{ "model": "togethercomputer/GPT-JT-6B-v1", "prompt": "Once upon a time,", "max_tokens": 512, "temperature": 0.5 }'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 "togethercomputer/GPT-JT-6B-v1" \ --host 0.0.0.0 \ --port 30000 # Call the server using curl (OpenAI-compatible API): curl -X POST "http://localhost:30000/v1/completions" \ -H "Content-Type: application/json" \ --data '{ "model": "togethercomputer/GPT-JT-6B-v1", "prompt": "Once upon a time,", "max_tokens": 512, "temperature": 0.5 }' - Docker Model Runner
How to use togethercomputer/GPT-JT-6B-v1 with Docker Model Runner:
docker model run hf.co/togethercomputer/GPT-JT-6B-v1
PrefixLM finetuning details
Some questions about the final PrefixLM finetuning procedure mentioned in the model card (0.92 billion tokens on a mixture of Pile/COT/NI/P3):
- How was the mixture sampled and packed for sequence length 2048?
- Specifically, does a single 2048-length sequence consist of packed examples from a single dataset, unpacked examples from a single dataset, or packed examples individually sampled from the overall mixture?
- How were NI/P3 examples deduplicated? The original dataset cards mention there are potential duplicate inputs
- NI reference: https://huggingface.co/datasets/Muennighoff/natural-instructions
- P3 reference: https://huggingface.co/datasets/Muennighoff/P3
- Were the instruction datasets (CoT, NI, P3) trained with zero-shot or few-shot prompts?
- a few shot prompt would include an example in the prefix portion of the input, which seems particularly salient for CoT.
Thanks so much!
Hi @jlli , those are all very interesting questions!
Regarding your questions:
How was the mixture sampled and packed for sequence length 2048?
For NI, a single 2048-length sequence consists of examples from a single dataset. For COT and P3, examples are sampled from the overall mixture.
How were NI/P3 examples deduplicated? The original dataset cards mention there are potential duplicate inputs
We used the original NI repo to generate training data. For example with multiple answers, we randomly sample an answer on the fly. So there should not be many duplicate inputs.
We did not intensionally deduplicate Muennighoff's P3. But since we sample data from the entire mixture, it should be less likely to encounter the same input in the same training sequence.
Were the instruction datasets (CoT, NI, P3) trained with zero-shot or few-shot prompts?
The instruction datasets (CoT, NI, P3) were trained by randomly splitting a sequence into the prompt and its target during training.
This ensures coverage of both zero-shot and few-shot type prompts over time.