pymc-devs/pymc

Refactor sampler warnings to a serializable data structure

Open

#6,252 opened on Oct 28, 2022

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Python (1,902 forks)batch import
help wantedtrace-backend

Repository metrics

Stars
 (7,926 stars)
PR merge metrics
 (Avg merge 11d) (7 merged PRs in 30d)

Description

As discussed in this and this comment the sampler warnings should be refactored into a data structure that can accomodate...

  • Hierarchical samplers
  • Samplers of different type (not everything is NUTS)

This is mostly a matter of thinking (hard) about data structures, also with McBackend protobufs and ArviZ InferenceData schema in mind.

Contributor guide

Research direction
Study the current sampler warning mechanism in PyMC, review the linked comments and pull request, understand the McBackend protobufs and ArviZ schema, then design a serializable data structure for hierarchical and heterogeneous samplers.
Tech stack
python
Domain
backend
Issue type
Refactor
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
Python
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
35