New issue 1315: Place for domain-specific fields in the field documentation
https://bitbucket.org/yt_analysis/yt/issues/1315/place-for-domain-specifi...
Nathan Goldbaum:
Right now most of this sort of documentation lives in the analysis modules. We'd like to split off most of the analysis modules into their own packages but one or two will stay in the main yt package because all they do is add a few fields. We should move the documentation for these analysis modules into the field documentation.

Hi all,
Would anyone be interested in putting together some project ideas for
google summer of code?
OpenAstronomy will likely be applying to be an umbrella org and they've
asked me to indicate whether we'd like to participate again this year. Last
year we didn't end up getting many applications, so we should try to think
hard about writing good project ideas. We could also think about applying
under the NumFocus org instead of OpenAstronomy, since yt is increasingly
not only for astronomical simulation data.
Applications are due Feb 9, so please try to get back to me either here or
off-list so I can let the OpenAstronomy organizers know. If there's enough
interest I'll try to put together a video call so we can discuss our
portion of the application process.
-Nathan

Hi
Organizations can start submitting applications for Google Summer of Code
2017 on January 19 (and the deadline is February 9)
https://developers.google.com/open-source/gsoc/timeline?hl=en
NumFOCUS will be applying again this year. If you want to work with us
please let me know and if you apply as an organization yourself or under a
different umbrella organization please tell me as well. If you participate
with us it would be great if you start to add possible projects to the
ideas page on github soon. We some general information for mentors on
github.
https://github.com/numfocus/gsoc/blob/master/CONTRIBUTING-mentors.md
We also have a template for ideas that might help. It lists the things
Google likes to see.
https://github.com/numfocus/gsoc/blob/master/2017/ideas-list-skeleton.md
In case you participated in earlier years with NumFOCUS there are some
small changes this year. Raniere won't be the admin this year. Instead I'm
going to be the admin. We are also planning to include two explicit rules
when a student should be failed, they have to communicate regularly and
commit code into your development branch at the end of the summer.
best, Max

New issue 1311: [Ramses] add possibility to force cosmological
https://bitbucket.org/yt_analysis/yt/issues/1311/ramses-add-possibility-t...
Corentin Cadiou:
Regarding discussions on pull request 2491, it would be great to be able to tell yt whether a simulation is a cosmological one by implementing an extra `force_cosmological` flag into the RAMSES data loader.
The code would override any detection of the nature of the simulation using the value given in the flag. This can be useful for some cosmological simulations running down to `z<0` with `H0=1` that are detected as non-cosmological ones.

Hi all,
I just rolled out new version of hub.yt. Most notable changes:
* girder API was upgraded to 2.1.0.
* hub can now spawn different containers.
The latter is probably the most interesting feature. Before the update,
all you could do with the data was launching jupyter notebook that had
the proper files mounted. Right now when you try to run the notebook,
you'll be instead asked about your preferred "frontend" to expose the
data with.
Currently available frontends are: Jupyter Notebook and Jupyter Lab.
I know it's not really much of a choice, but it merely serves as a proof
of concept. The bottom line is: if you have a specific software that
you'd like to run with the data hosted on hub.yt, we can make that happen!
As always, if you notice anything not working, please let me know.
Cheers,
Kacper