-
-
Notifications
You must be signed in to change notification settings - Fork 477
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Pystan example model - comparing two groups #108
Comments
The case studies eventually go on the web site repo. Your Stan model has lots of problems you can see in just this fragment:
The code itself has some problems:
The doc also has some issues
|
@bob-carpenter Thanks for the feedback! I'll work on correcting this. This is a learning process for me. |
For the moment, we're trying to keep the case studies to best practices recommendations for Stan. We're working on establishing a place for more community oriented sharing of work we wouldn't need to vet so closely. There are prior recommendations on the stan-dev/stan wiki and in the manual regression chapter. |
You also don't need blocks with nothing in them and you can vectorize everything. This model should look like this:
It'd be even easier if we had ragged arrays. |
Thanks again @bob-carpenter ! I am working on how to vectorize data. I appreciate the model re-write. ara |
Hello,
I asked over on the Pystan group about submitting juypter notebook example models using Pystan. I was directed to over here. I am in the process of moving our models into Pystan so this is a learning process for me.
I created a jupyter notebook here:
https://github.com/bioinfonm/bioinfonm.github.io/blob/master/_posts/pystan_musings_part1_img/pystan_three_centirues_english_grain_data.ipynb
The notebook, raw data, and images are all:
https://github.com/bioinfonm/bioinfonm.github.io/tree/master/_posts/pystan_musings_part1_img
I was wondering what was the best way to get this vetted and then hosted here as an example for PyStan.
Thank you for the time and consideration,
Ara
The text was updated successfully, but these errors were encountered: