Question: Can't download model checkpoints from Azure blob model registry
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 20/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- azure, python
- Domain
- cloud, machine-learning
Research direction
Start with _model_registry.py and inspect the Azure Blob paths configured for the GPT-2 checkpoints. Verify whether those locations are intended to be publicly readable and document the access requirement or repository-side change needed for checkpoint retrieval; completion requires a confirmed, reproducible access path.
Written by the indexing model from the issue text.
Description
I am attempting to download model checkpoints from the Azure Blob Model Registry associated with this repository. However, access denial errors appear to suggest that there's no public access to that storage, but only access via accounts that are added as external to openAI's tenant.
filename: model_registry.py
_MODEL_SPECS: dict[str, StandardModelSpec] = {
# GPT-2 series
"gpt2-small": StandardModelSpec(
model_path="az://openaipublic/neuron-explainer/subject-models/gpt2/small"
),
"gpt2-medium": StandardModelSpec(
model_path="az://openaipublic/neuron-explainer/subject-models/gpt2/medium"
),
"gpt2-large": StandardModelSpec(
model_path="az://openaipublic/neuron-explainer/subject-models/gpt2/large"
),
"gpt2-xl": StandardModelSpec(
model_path="az://openaipublic/neuron-explainer/subject-models/gpt2/xl"
),
}
Could you please verify whether the aforementioned Azure Blob storage is intended to be publicly accessible for model checkpoint retrieval?
- Dominant language
- Python
- Stars
- 4.1k
- Forks
- 242
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from openai/transformer-debugger
-
Difficulty 3/5 1-2 days Newbie friendliness 25/100
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
-
Difficulty 3/5 1-2 days Newbie friendliness 25/100
openai/transformer-debugger#21 · 5 comments · 1 reaction ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
openai/transformer-debugger#18 · 1 comment · 3 reactions ·
All issues in openai/transformer-debugger
Similar issues
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
fossasia/visdom-dev#77 ·
Maintainers usually reply within 4 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
aws-cloudformation/cfn-lint#4890 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
volcengine/OpenViking#6521 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
AstrBotDevs/AstrBot#10720 ·
Maintainers usually reply within 1 day