r/datascience • • 5d ago

Statistics What would a fully Bayesian programming environment look like?

https://statmodeling.stat.columbia.edu/2026/11/11/the-challenge-of-truly-probabilistic-programming/
95 Upvotes

13 comments sorted by

426

u/Yourdataisunclean 5d ago • Bravo

Depends on what happened prior.

26

u/Spiggots 5d ago

Shut up and take my upvote

5

u/BeardySam 5d ago

“Well, I know what it doesn’t look like”

3

u/big_data_mike 5d ago

Hello fellow dad

2

u/wdebakker 5d ago

Amazing

2

u/Think-Culture-4740 2d ago

What if what happened prior was uninformed

20

u/Synthetic-Meat-2000 5d ago

Are you asking about running Markov Chain Monte-Carlo simulations and developing hierarchical models? It will R with some extensions, if you are fluent in R, otherwise PyMC in Python.

With PyMC, it's worth learning to configure the backend to your CPU or GPU to get the max performance

4

u/TakenSadFace 4d ago

multiprocessor goes brrrr

11

u/selfintersection 5d ago

So Gelman wants to be able to work with the outputs of the model without needing to worry about the fact that you're doing the algebra per-draw. I don't quite understand why the generated quantities block doesn't work for him, because it works just like that. But maybe the issue is that he wants to do it more interactively, in R or something afterward.

2

u/a_brown_125 2d ago

If the pain is post-fit exploration, draw-aware transforms seem key: define derived quantities interactively while keeping the draw axis explicit, so uncertainty stays visible through each operation.

7

u/hendrik0806 5d ago

I can kind of relate - although I have in generell mixed feelings about vectorisation beside from its efficiency. Thinking about the model and parameters in iterations gives me a feeling for the data flow - especially when the model contains multiple modules with measurement and structural parts. This is why I kind of dislike when indexes falls away using vectorisation in stan. In R parameters as vectors are pretty simple to handle especially with tidyverse functions and storing them as lists in tibbles through nest. I don’t really see any necessity for packages that abstract away important details when handling those samples.

3

u/StephenSRMMartin 4d ago

I tend to start building out a model in terms of single logical units at a time (row, or group, or whatever makes sense), to get the structure. Then change it to matrix notation for brevity (with superscripts denoting matrix dimensions), then it's a pretty direct translation to Stan.