dynamic traceplot for jupyter notebooks
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- jupyter-notebook, python
- Domain
- data-visualization, tooling
Research direction
Start by reviewing how the tqdm progress bar monitors standard output and how Stan CSV output files expose lp__ across chains. Define the notebook-facing behavior for a dynamic lp__ trace during warmup and sampling; done means the visualization updates across chains without monitoring individual parameters.
Written by the indexing model from the issue text.
Description
Summary:
It would be super cool to provide a dynamic traceplot of the value of lp__ (total joint log probability for the model) across all chains during warmup and sampling - is this possible?
Description:
showed Andrew Gelman Colab jupyter notebooks (R version) and he asked for this dynamic visualization. we could pull this off the output files similar to the way that the tqdm progress bar monitors standard out. given the current Stan csv format, the first column is the lp__ - the total joint log probability. generally, when lp__ converges, all params have converged, conversely, if any params have not converged, lp__ will not converge either, so this would be good enough
we want to discourage folks from trying to monitor a particular param - there are other more appropriate tools that should be used - so simple feature - just monitor lp__ across chains!
Additional Information:
Current Version:
- Dominant language
- Python
- Stars
- 198
- Forks
- 81
- PR merge metrics
- No merged PRs in 30d
Contributor guide
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 stan-dev/cmdstanpy
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
feature
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 55/100
-
feature method outputs
Difficulty 4/5 3-5 days Newbie friendliness 45/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
All issues in stan-dev/cmdstanpy
Similar issues
-
essnmx good first issue
Difficulty 1/5 Under an hour Newbie friendliness 95/100
-
[Feature] 奇物选择添加优先级 Open
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
syfoud/Simulated_Scepter#174 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Giskard-AI/giskard-oss#2840 · 1 comment ·
-
A claim comment carrying the issue number is silently declined while the workflow reports success Openarea: repo bug perceived difficulty: 2
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
yeti-platform/yeti#1380 ·