<div dir="ltr">Congratulations to you guys for the award! A great honor!<div><br></div><div>Looking forward to making yt more general for a larger audience!<br><div><br></div><div>Cameron</div></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Aug 10, 2017 at 9:31 AM, Matthew Turk <span dir="ltr"><<a href="mailto:matthewturk@gmail.com" target="_blank">matthewturk@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi folks,<br>
<br>
We (Nathan, Meagan, Kacper and I) wanted to share some good news.<br>
We've recently received a grant from the NSF SI2 program; NCSA put out<br>
a press release here:<br>
<br>
<a href="http://www.ncsa.illinois.edu/news/story/the_yt_project_awarded_nsf_grant_to_expand_to_multiple_new_science_domains" rel="noreferrer" target="_blank">http://www.ncsa.illinois.edu/<wbr>news/story/the_yt_project_<wbr>awarded_nsf_grant_to_expand_<wbr>to_multiple_new_science_<wbr>domains</a><br>
<br>
(This includes a link to the full proposal, which goes into some detail.)<br>
<br>
This is a five year grant, supporting part or all of a couple postdocs<br>
(UIUC, Columbia, Wisconsin), a research scientist, some PI time and a<br>
graduate student (along with some workshops). It has a couple areas<br>
of development that we'll be working on. The strictly technical ones<br>
will be related to improving non-spatial indexing, enabling "path"<br>
queries in a more full way (think advanced streamlines) and an<br>
all-new, symbolic field system. In a sense, these are things we're<br>
already kind of familiar with how to work on -- YTEPs, code reivew,<br>
documentation, testing, etc.<br>
<br>
The part that's going to be harder -- from the social perspective --<br>
is that we're going to be working harder to make yt an attractive<br>
analysis and visualization system outside of astronomy, without losing<br>
its attractiveness *within* astronomy.<br>
<br>
This cross-domain effort ties into things like Britton's recent work<br>
on splitting out yt_astro_analysis, and the idea of compartmentalizing<br>
things a bit more within the frontends and whatnot.<br>
<br>
We've identified an advisory board with folks from geophysics,<br>
weather, oceanography, nuclear engineering, plasma physics and<br>
observational astro, and we're going to spin up a couple new mailing<br>
lists for this purpose:<br>
<br>
* yt-advisory: advisory board discussions<br>
* yt-ssi: administrative info for the grant (possibly boring?)<br>
<br>
I'm working to get our lists moved to the <a href="http://yt-project.org" rel="noreferrer" target="_blank">yt-project.org</a> domain before<br>
doing this, though. All of these will be open, although I suspect not<br>
of broad interest (and thus why we're creating new ones.) It might<br>
turn out that domain-specific discussion ends up overwhelming<br>
discussion on yt-dev or yt-users, in which case we can split it out,<br>
but for now yt-dev seems like the right place to put that.<br>
<br>
Anyhow, the main takeaway I want to give from this is: I'm pretty<br>
excited, and I am really, really looking forward to the work we're<br>
going to do with this. We could not have gotten this far without the<br>
amazing community that has grown up around yt. We're going to work on<br>
this project in an open, collaborative way in keeping with the spirit<br>
of what we've done with yt already.<br>
<br>
In the proposal itself, we detail the ways in which we will follow the<br>
standard yt community norms (for design, review, upstream, etc) and<br>
before it was submitted, we discussed it with the yt steering<br>
committee to make sure that the language we included did not sideline<br>
or "squeeze out" anyone in the community. Ensuring that this<br>
*supports*, rather than *detracts from*, the community is absolutely<br>
essential to its success, and we will not be doing anything to<br>
jeopardize that success: this means more effort on yt, but it does not<br>
mean that yt will suddenly become a "professionalized" project that<br>
loses sight of how it got here. And, we would welcome feedback --<br>
especially if it seems that we're missing the mark.<br>
<br>
We're still figuring out how to most effectively do project management<br>
for it, but it's going to all be above board, and we'd absolutely<br>
*love* to collaborate with interested folks on it.<br>
<br>
More soon!<br>
<br>
-Matt & Nathan<br>
______________________________<wbr>_________________<br>
yt-dev mailing list<br>
<a href="mailto:yt-dev@lists.spacepope.org">yt-dev@lists.spacepope.org</a><br>
<a href="http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org" rel="noreferrer" target="_blank">http://lists.spacepope.org/<wbr>listinfo.cgi/yt-dev-spacepope.<wbr>org</a><br>
</blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div>Cameron Hummels<div><span style="font-size:12.8000001907349px">NSF Postdoctoral Fellow</span></div><div><span style="font-size:12.8000001907349px">Department of Astronomy</span></div><div><span style="font-size:12.8000001907349px">California Institute of Technology</span><br></div><div><a href="http://chummels.org" style="font-size:12.8000001907349px" target="_blank">http://chummels.org</a><br></div></div></div></div>
</div>