Finishing up the 2.4 release
Hey everybody, I hope you're all enjoying your weekend and don't mind taking some time out of it to think about yt. Right now there are only three open tickets for the 2.4 release: 1. The entropy field in non-enzo data 2. Transfer function bounds 3. Volume rendering docs I think these tickets are things that are fixable on a short timescale. Sam, please let us know if you need more time or help with the volume rendering docs. We've put a lot of time into updating the cookbook and making sure the scripts produce good-looking images based on a variety of datasets. The latest version of the docs is available here: http://yt-project.org/docs/2.4/ I'm curious how everyone feels about setting a time aside sometime this week to do the official release. I think the release will attract more eyeballs if we can point to screencasts about some of the new functionality, including (but not limited to, see the changelog <http://yt-project.org/docs/2.4/changelog.html#version-2-4> for the full [really extensive and impressive] list of changes): 1. Threaded volume renderer 2. Plot window 3. Improved time series analysis 4. Improved extjs4 reason 5. The new yt hub I'm planning on doing a plot window screencast this afternoon. Does anyone else want to claim one of the features? Lastly, I contacted Kelle Cruz at astrobetter about going a guest post about the yt 2.4 release. She is interested - all she needs from us is a google doc with a draft of the post, including text embedded videos, and urls. I'm going to begin the write up sometime this week and then share the google doc on the yt-dev list so that others can contribute. The end is in sight! This will be by far the best release of yt yet :) Cheers, Nathan
I'm willing to take on the entropy field along the lines of what Greg suggested, but I still wonder if we should try to incorporate spatially varying gammas. I assume this is something that is not possible in Enzo, I guess, but I don't know about other codes. I assume this could be handled by checking whether or not "gamma" is defined as a runtime parameter, or checking the field list for the gamma fields. Thoughts? On Jul 28, 2012, at 6:37 PM, Nathan Goldbaum <nathan12343@gmail.com> wrote:
Hey everybody,
I hope you're all enjoying your weekend and don't mind taking some time out of it to think about yt.
Right now there are only three open tickets for the 2.4 release:
1. The entropy field in non-enzo data 2. Transfer function bounds 3. Volume rendering docs
I think these tickets are things that are fixable on a short timescale. Sam, please let us know if you need more time or help with the volume rendering docs.
We've put a lot of time into updating the cookbook and making sure the scripts produce good-looking images based on a variety of datasets. The latest version of the docs is available here: http://yt-project.org/docs/2.4/
I'm curious how everyone feels about setting a time aside sometime this week to do the official release. I think the release will attract more eyeballs if we can point to screencasts about some of the new functionality, including (but not limited to, see the changelog <http://yt-project.org/docs/2.4/changelog.html#version-2-4> for the full [really extensive and impressive] list of changes):
1. Threaded volume renderer 2. Plot window 3. Improved time series analysis 4. Improved extjs4 reason 5. The new yt hub
I'm planning on doing a plot window screencast this afternoon. Does anyone else want to claim one of the features?
Lastly, I contacted Kelle Cruz at astrobetter about going a guest post about the yt 2.4 release. She is interested - all she needs from us is a google doc with a draft of the post, including text embedded videos, and urls. I'm going to begin the write up sometime this week and then share the google doc on the yt-dev list so that others can contribute.
The end is in sight! This will be by far the best release of yt yet :)
Cheers,
Nathan _______________________________________________ yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
Hi John, On Mon, Jul 30, 2012 at 1:45 AM, John ZuHone <jzuhone@gmail.com> wrote:
I'm willing to take on the entropy field along the lines of what Greg suggested, but I still wonder if we should try to incorporate spatially varying gammas. I assume this is something that is not possible in Enzo, I guess, but I don't know about other codes.
Enzo (when run with multiple species) does have a spatially varying gamma, but it's not written out to the file -- it's calculated from partial pressure and includes contributions from H2 as well. I would say that this shouldn't be dealt with directly, though.
I assume this could be handled by checking whether or not "gamma" is defined as a runtime parameter, or checking the field list for the gamma fields.
Thoughts?
On Jul 28, 2012, at 6:37 PM, Nathan Goldbaum <nathan12343@gmail.com> wrote:
Hey everybody,
I hope you're all enjoying your weekend and don't mind taking some time out of it to think about yt.
Right now there are only three open tickets for the 2.4 release:
1. The entropy field in non-enzo data 2. Transfer function bounds 3. Volume rendering docs
I think these tickets are things that are fixable on a short timescale. Sam, please let us know if you need more time or help with the volume rendering docs.
We've put a lot of time into updating the cookbook and making sure the scripts produce good-looking images based on a variety of datasets. The latest version of the docs is available here: http://yt-project.org/docs/2.4/
I'm curious how everyone feels about setting a time aside sometime this week to do the official release. I think the release will attract more eyeballs if we can point to screencasts about some of the new functionality, including (but not limited to, see the changelog <http://yt-project.org/docs/2.4/changelog.html#version-2-4> for the full [really extensive and impressive] list of changes):
1. Threaded volume renderer 2. Plot window 3. Improved time series analysis 4. Improved extjs4 reason 5. The new yt hub
I'm planning on doing a plot window screencast this afternoon. Does anyone else want to claim one of the features?
Lastly, I contacted Kelle Cruz at astrobetter about going a guest post about the yt 2.4 release. She is interested - all she needs from us is a google doc with a draft of the post, including text embedded videos, and urls. I'm going to begin the write up sometime this week and then share the google doc on the yt-dev list so that others can contribute.
The end is in sight! This will be by far the best release of yt yet :)
Cheers,
Nathan _______________________________________________ yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
_______________________________________________ yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
Hi Matt, You mean just in this Enzo special case or in general? John On Mon, Jul 30, 2012 at 6:58 AM, Matthew Turk <matthewturk@gmail.com> wrote:
Hi John,
On Mon, Jul 30, 2012 at 1:45 AM, John ZuHone <jzuhone@gmail.com> wrote:
I'm willing to take on the entropy field along the lines of what Greg suggested, but I still wonder if we should try to incorporate spatially varying gammas. I assume this is something that is not possible in Enzo, I guess, but I don't know about other codes.
Enzo (when run with multiple species) does have a spatially varying gamma, but it's not written out to the file -- it's calculated from partial pressure and includes contributions from H2 as well. I would say that this shouldn't be dealt with directly, though.
I assume this could be handled by checking whether or not "gamma" is
defined as a runtime parameter, or checking the field list for the gamma fields.
Thoughts?
On Jul 28, 2012, at 6:37 PM, Nathan Goldbaum <nathan12343@gmail.com>
wrote:
Hey everybody,
I hope you're all enjoying your weekend and don't mind taking some time
Right now there are only three open tickets for the 2.4 release:
1. The entropy field in non-enzo data 2. Transfer function bounds 3. Volume rendering docs
I think these tickets are things that are fixable on a short timescale.
Sam, please let us know if you need more time or help with the volume rendering docs.
We've put a lot of time into updating the cookbook and making sure the
I'm curious how everyone feels about setting a time aside sometime this
week to do the official release. I think the release will attract more eyeballs if we can point to screencasts about some of the new functionality, including (but not limited to, see the changelog < http://yt-project.org/docs/2.4/changelog.html#version-2-4> for the full [really extensive and impressive] list of changes):
1. Threaded volume renderer 2. Plot window 3. Improved time series analysis 4. Improved extjs4 reason 5. The new yt hub
I'm planning on doing a plot window screencast this afternoon. Does
anyone else want to claim one of the features?
Lastly, I contacted Kelle Cruz at astrobetter about going a guest post
about the yt 2.4 release. She is interested - all she needs from us is a google doc with a draft of the post, including text embedded videos, and urls. I'm going to begin the write up sometime this week and then share
out of it to think about yt. scripts produce good-looking images based on a variety of datasets. The latest version of the docs is available here: http://yt-project.org/docs/2.4/ the google doc on the yt-dev list so that others can contribute.
The end is in sight! This will be by far the best release of yt yet :)
Cheers,
Nathan _______________________________________________ yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
_______________________________________________ yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
-- John ZuHone Postdoctoral Researcher NASA/Goddard Space Flight Center jzuhone@gmail.com john.zuhone@nasa.gov
On Mon, Jul 30, 2012 at 11:23 AM, John Zuhone <jzuhone@gmail.com> wrote:
Hi Matt,
You mean just in this Enzo special case or in general?
I just meant I don't think we should have a full EOS calculation included right now, but maybe I am misunderstanding.
John
On Mon, Jul 30, 2012 at 6:58 AM, Matthew Turk <matthewturk@gmail.com> wrote:
Hi John,
On Mon, Jul 30, 2012 at 1:45 AM, John ZuHone <jzuhone@gmail.com> wrote:
I'm willing to take on the entropy field along the lines of what Greg suggested, but I still wonder if we should try to incorporate spatially varying gammas. I assume this is something that is not possible in Enzo, I guess, but I don't know about other codes.
Enzo (when run with multiple species) does have a spatially varying gamma, but it's not written out to the file -- it's calculated from partial pressure and includes contributions from H2 as well. I would say that this shouldn't be dealt with directly, though.
I assume this could be handled by checking whether or not "gamma" is defined as a runtime parameter, or checking the field list for the gamma fields.
Thoughts?
On Jul 28, 2012, at 6:37 PM, Nathan Goldbaum <nathan12343@gmail.com> wrote:
Hey everybody,
I hope you're all enjoying your weekend and don't mind taking some time out of it to think about yt.
Right now there are only three open tickets for the 2.4 release:
1. The entropy field in non-enzo data 2. Transfer function bounds 3. Volume rendering docs
I think these tickets are things that are fixable on a short timescale. Sam, please let us know if you need more time or help with the volume rendering docs.
We've put a lot of time into updating the cookbook and making sure the scripts produce good-looking images based on a variety of datasets. The latest version of the docs is available here: http://yt-project.org/docs/2.4/
I'm curious how everyone feels about setting a time aside sometime this week to do the official release. I think the release will attract more eyeballs if we can point to screencasts about some of the new functionality, including (but not limited to, see the changelog <http://yt-project.org/docs/2.4/changelog.html#version-2-4> for the full [really extensive and impressive] list of changes):
1. Threaded volume renderer 2. Plot window 3. Improved time series analysis 4. Improved extjs4 reason 5. The new yt hub
I'm planning on doing a plot window screencast this afternoon. Does anyone else want to claim one of the features?
Lastly, I contacted Kelle Cruz at astrobetter about going a guest post about the yt 2.4 release. She is interested - all she needs from us is a google doc with a draft of the post, including text embedded videos, and urls. I'm going to begin the write up sometime this week and then share the google doc on the yt-dev list so that others can contribute.
The end is in sight! This will be by far the best release of yt yet :)
Cheers,
Nathan _______________________________________________ yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
_______________________________________________ yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
_______________________________________________ yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
-- John ZuHone
Postdoctoral Researcher NASA/Goddard Space Flight Center
jzuhone@gmail.com john.zuhone@nasa.gov
_______________________________________________ yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
Hi all, Quick request: can people who have contributed these portions of the changeset provide brief recipes for how to demonstrate their functionality? It only needs to be a few lines, and nothing too in detail. I'm preparing a demo IPython notebook (in lieu of slides) to show them off. * Camera path creation from keyframes and splines * Particle trajectory calculaton Also, Nathan, is there a way to take an existing Projection or Slice object and make that into a plot window? I'll wrap up all of these into the cookbook as well as into the demo notebook. -Matt On Mon, Jul 30, 2012 at 11:25 AM, Matthew Turk <matthewturk@gmail.com> wrote:
On Mon, Jul 30, 2012 at 11:23 AM, John Zuhone <jzuhone@gmail.com> wrote:
Hi Matt,
You mean just in this Enzo special case or in general?
I just meant I don't think we should have a full EOS calculation included right now, but maybe I am misunderstanding.
John
On Mon, Jul 30, 2012 at 6:58 AM, Matthew Turk <matthewturk@gmail.com> wrote:
Hi John,
On Mon, Jul 30, 2012 at 1:45 AM, John ZuHone <jzuhone@gmail.com> wrote:
I'm willing to take on the entropy field along the lines of what Greg suggested, but I still wonder if we should try to incorporate spatially varying gammas. I assume this is something that is not possible in Enzo, I guess, but I don't know about other codes.
Enzo (when run with multiple species) does have a spatially varying gamma, but it's not written out to the file -- it's calculated from partial pressure and includes contributions from H2 as well. I would say that this shouldn't be dealt with directly, though.
I assume this could be handled by checking whether or not "gamma" is defined as a runtime parameter, or checking the field list for the gamma fields.
Thoughts?
On Jul 28, 2012, at 6:37 PM, Nathan Goldbaum <nathan12343@gmail.com> wrote:
Hey everybody,
I hope you're all enjoying your weekend and don't mind taking some time out of it to think about yt.
Right now there are only three open tickets for the 2.4 release:
1. The entropy field in non-enzo data 2. Transfer function bounds 3. Volume rendering docs
I think these tickets are things that are fixable on a short timescale. Sam, please let us know if you need more time or help with the volume rendering docs.
We've put a lot of time into updating the cookbook and making sure the scripts produce good-looking images based on a variety of datasets. The latest version of the docs is available here: http://yt-project.org/docs/2.4/
I'm curious how everyone feels about setting a time aside sometime this week to do the official release. I think the release will attract more eyeballs if we can point to screencasts about some of the new functionality, including (but not limited to, see the changelog <http://yt-project.org/docs/2.4/changelog.html#version-2-4> for the full [really extensive and impressive] list of changes):
1. Threaded volume renderer 2. Plot window 3. Improved time series analysis 4. Improved extjs4 reason 5. The new yt hub
I'm planning on doing a plot window screencast this afternoon. Does anyone else want to claim one of the features?
Lastly, I contacted Kelle Cruz at astrobetter about going a guest post about the yt 2.4 release. She is interested - all she needs from us is a google doc with a draft of the post, including text embedded videos, and urls. I'm going to begin the write up sometime this week and then share the google doc on the yt-dev list so that others can contribute.
The end is in sight! This will be by far the best release of yt yet :)
Cheers,
Nathan _______________________________________________ yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
_______________________________________________ yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
_______________________________________________ yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
-- John ZuHone
Postdoctoral Researcher NASA/Goddard Space Flight Center
jzuhone@gmail.com john.zuhone@nasa.gov
_______________________________________________ yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
Hi Matt,
Also, Nathan, is there a way to take an existing Projection or Slice object and make that into a plot window?
Not right now, no. I think it would be a simple change to the SlicePlot, ProjectionPlot, and OffAxisSlicePlot classes though. Let me know if you'd like me to take care of that. -Nathan
Hi Nathan, On Mon, Jul 30, 2012 at 1:29 PM, Nathan Goldbaum <nathan12343@gmail.com> wrote:
Hi Matt,
Also, Nathan, is there a way to take an existing Projection or Slice object and make that into a plot window?
Not right now, no. I think it would be a simple change to the SlicePlot, ProjectionPlot, and OffAxisSlicePlot classes though. Let me know if you'd like me to take care of that.
I ended up putting a very simple to_pw() routine in that hangs off objects. It doesn't specify anything, and leaves it up to the caller to zoom and move around. PR: https://bitbucket.org/yt_analysis/yt/pull-request/225/adding-a-to_pw-call-to...
-Nathan
_______________________________________________ yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
Hi Nathan, Thanks for the summary email. On Sat, Jul 28, 2012 at 6:37 PM, Nathan Goldbaum <nathan12343@gmail.com> wrote:
Hey everybody,
I hope you're all enjoying your weekend and don't mind taking some time out of it to think about yt.
Right now there are only three open tickets for the 2.4 release:
1. The entropy field in non-enzo data 2. Transfer function bounds
I spent some time yesterday morning trying to reproduce this and I was not successful. I noted this in my ticket comment: https://bitbucket.org/yt_analysis/yt/issue/390/transfer-function-bounds I think the problem Sam described when he opened it can be fixed by using the f64clip function when evaluating the transfer function inside grid_traversal.pyx. I have avoided this in the past because it adds a considerable slowdown (10% last I looked) and I was hoping we might find a better way to do it. What neds up happening is you interpolate off the ends of the table.
3. Volume rendering docs
I think these tickets are things that are fixable on a short timescale. Sam, please let us know if you need more time or help with the volume rendering docs.
If Sam has too much going on this week, I can also try to address this one. I think the only thing I can't cover is how to handle opaque/semi-opaque surfaces.
We've put a lot of time into updating the cookbook and making sure the scripts produce good-looking images based on a variety of datasets. The latest version of the docs is available here: http://yt-project.org/docs/2.4/
I'm curious how everyone feels about setting a time aside sometime this week to do the official release. I think the release will attract more eyeballs if we can point to screencasts about some of the new functionality, including (but not limited to, see the changelog <http://yt-project.org/docs/2.4/changelog.html#version-2-4> for the full [really extensive and impressive] list of changes):
1. Threaded volume renderer 2. Plot window 3. Improved time series analysis 4. Improved extjs4 reason 5. The new yt hub
I'm planning on doing a plot window screencast this afternoon. Does anyone else want to claim one of the features?
I'll do a screencast about the hub. I still intend to come up with a slide show showing highlights, and the screencasts would fit very nicely into that.
Lastly, I contacted Kelle Cruz at astrobetter about going a guest post about the yt 2.4 release. She is interested - all she needs from us is a google doc with a draft of the post, including text embedded videos, and urls. I'm going to begin the write up sometime this week and then share the google doc on the yt-dev list so that others can contribute.
The end is in sight! This will be by far the best release of yt yet :)
I agree. Looking at the churn statistics, we've had (to date) 1091 revisions between the branch point of yt-2.3 and the current tip: hg churn -c -r "tip:ancestor(tip, 'yt-2.3')" | awk '{SUM += $2} ; END {PRINT $SUM}' Looking over the changes, the theme that stands out to me is just how focused this release was on taking things that were either outdated or broken, and fixing them. And then on top of that, layering higher performance and more capable functionality. As many of you probably know, I'm somewhat ambivalent about focusing on version numbers and release schemes. But I think in this case, it will serve a very useful purpose of sharing with the community where development has led. I'm pretty pleased with that, and I think everyone who contributed (and 20 people contributed patches or changesets for this release) has something to be proud of. -Matt
Cheers,
Nathan _______________________________________________ yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
participants (4)
-
John Zuhone -
John ZuHone
-
Matthew Turk -
Nathan Goldbaum