-
Notifications
You must be signed in to change notification settings - Fork 21
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 Economics (Econ-ARK) #347
Comments
@llorracc - would you, or someone in the Econ-ARK community, be up for writing a short post here? |
Sure! Am cc’ing Alan who would be the right person to do it.
I’ve got a question for you when I locate you (or if you see me).
On Fri, Sep 23, 2022 at 2:41 PM Joe Hamman ***@***.***> wrote:
@llorracc <https://github.com/llorracc> - would you, or someone in the
Econ-ARK community, be up for writing a short post here?
—
Reply to this email directly, view it on GitHub
<#347 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAKCK75HREE44IGOYW5NPHDV7YPZHANCNFSM6AAAAAAQUKRMGE>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
--
Sent from Gmail Mobile
|
I may already have something for this! |
@alanlujan91 - let me know if you have any questions. |
@alanlujan91 - circling back here, are you still up for writing a short post? We're ready to help get it on the site whenever you have a draft. |
Joe, @alanlujan91 has been working on figuring out how to implement some interpolation stuff and has been exploring xarray as part of that. I think there are some questions he has about how xarray interpolations work and whether they can do what we need for our project -- if they do, then we'll probably want to use xarray in our solution to these problems. And if they don't, at least we can post an issue or a question. (My suspicion is that there is a way to do what we want with the existing tools, but it's not easy to figure out how to do it, which would be the perfect subject for a post.) So, can you put Alan in touch with whoever might be most knowledgeable about xarray's interpolation tools and maybe we can have a great outcome for this. |
@alanlujan91 - if you can post your question here, we'll make sure to get some eyes on it. Additionally, the xarray office hours series is starting up soon which you may find useful. |
Have finally pushed this notebook to master, would appreciate some feedback on how we can use xarray better and would be happy to publish this work (or a brief summary) on your site. https://github.com/econ-ark/HARK/blob/master/examples/LabeledModels/LabeledModels.ipynb |
@alanlujan91 - this looks quite interesting, thank you for sharing!. My suggestion for the blog post would be to keep the focus at a slightly higher level, but certainly reference these examples and possibly even bring snapshot over as an example. Do you think you could use this application to write a post that follows the outline above? |
This is a proposal for an economics use case story for Xarray. The story will be published on Xarray's blog (https://xarray.dev/blog).
Why?
We've seen Xarray is used in a number of economics applications (e.g. Econ-ARK) and we've heard its used in other financial modeling context (@max-sixty could likely list a few). A user story blog post showing how Xarray can be used to represent and analyze economics data (in Econ-ARK) would help socialize the concept across the Xarray developer and broader economics communities.
What?
We are targeting a short and non-technical post that illustrates how Xarray is used in the Econ-ARK 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-econ-ark
or whatever makes sense for your application.xref: #272
The text was updated successfully, but these errors were encountered: