-
Notifications
You must be signed in to change notification settings - Fork 20
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
[User story proposal] Xarray for Bayesian modeling (PyMC, ArviZ) #348
Comments
@OriolAbril and/or @canyon289 - would either (or both) of you be up for contributing a blog post here? |
I sure would |
@canyon289 - Circling back here. Are you still up for writing a post? We're ready to help get it on the site whenever you are ready. |
Yes, what's the best way to coordinate? |
@jhamman dont want to lose track of this. Should I just copy the template from say this post and make a PR? https://github.com/xarray-contrib/xarray.dev/tree/main/src/posts/introducing-pint-xarray |
@canyon289 - that would be great! |
@jhamman Sorry for the delay. I am actively working on this. looking to get you a draft in the next week |
This is a proposal for a bayesian modeling use case story for Xarray. The story will be published on Xarray's blog (https://xarray.dev/blog).
Why?
Xarray is used as the underlying data structure in ArviZ (and PyMC?) today. A user story blog post showing how Xarray is used used to represent and analyze bayesian model data would help socialize the concept across the Xarray developer and broader Bayesian modeling communities.
What?
We are targeting a short and non-technical post that illustrates how Xarray is used in the ArviZ context. Below is a template outline that you should feel free to modify:
Feel free to insert images or short code blocks if they help you tell your story.
How?
Xarray's blog using Markdown with some front-matter. You can copy one of the existing posts to get started or you can write in a google-doc-like-thing and ask us to do the markdown formatting. If you copy a previous post, use a name like
user-story-arviz
or whatever makes sense for your application.xref: #272
The text was updated successfully, but these errors were encountered: