pyro-ppl / pyro-ppl/numpyro

feature: Pydantic to validate configurations

Open
#2,238 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

discussion
Dominant language
Python
Stars
2.8k
Forks
316
Avg merge
3d 9h
Merged PRs (30d)
27

Description

A realization after this comment: there are many cases where configurations fail, and tracking all will be too much. Why don't we embrace Pydantic to validate them?

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the linked pull-request review comment and the Pydantic validation documentation. Identify which NumPyro configurations need validation and where they enter the library before proposing an approach. Done means the intended configuration cases are validated consistently, with the behavior and coverage documented.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
tooling
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.