Dear yt developers, At the team meeting today, we discussed having a mini-sprint to finish off the remaining VR refactor stuff in preparation for a 3.3 release. I've gone through the open issues, and sorted them into the following categories. The first five categories are for issues that, IMO, represent significant usability concerns and block a 3.3 release: 1) Improved Narrative Docs and Cookbook Recipes: Issues 1110 <https://bitbucket.org/yt_analysis/yt/issues/1110/experimental-vr-camera-move...>, 1112 <https://bitbucket.org/yt_analysis/yt/issues/1112/experimental-document-how-t...>, 1128 <https://bitbucket.org/yt_analysis/yt/issues/1128/experimental-describe-using...> 2) Transfer Function Usability Issues: 1098 <https://bitbucket.org/yt_analysis/yt/issues/1098/experimental-enhanced-docum...>, 1104 <https://bitbucket.org/yt_analysis/yt/issues/1104/experimental-transfer-funct...> 3) Alpha Issues with Render Sources: 1129 <https://bitbucket.org/yt_analysis/yt/issues/1133/experimental-alpha-seems-no...>, 1133 <https://bitbucket.org/yt_analysis/yt/issues/1133/experimental-alpha-seems-no...> 4) Units Issue with the Camera: 1132 <https://bitbucket.org/yt_analysis/yt/issues/1132/experimental-camerawidth-is...> 5) Manual Use of the Off-Axis Projection transfer function: 1103 <https://bitbucket.org/yt_analysis/yt/issues/1103/experimental-render-with> There are a few categories of issues that, while they would certainly be nice to include, do not IMO *need* to be included in 3.3. These are: 1) Camera Path stuff: 1115 <https://bitbucket.org/yt_analysis/yt/issues/1115/experimental-add-in-keyfram...>, 1116 <https://bitbucket.org/yt_analysis/yt/issues/1116/experimental-making-vr-work...> , 2) new VR annotations for lines and rays: 1126 <https://bitbucket.org/yt_analysis/yt/issues/1126/experimental-add-annotate_r...> 3) Speed up the Perspective Lens and make it the default in the docs. 1121 <https://bitbucket.org/yt_analysis/yt/issues/1121/experimental-speed-up-persp...> If you disagree with any of these classifications, or if I've left something out, please let me know. Some time in the coming weeks, I think it would be good to dedicate a few person-days of effort to a mini-sprint to finish these issues off. I'd be game for such an effort myself, and I know that Nathan mentioned at the hangout that he'd be willing to help, too. If anyone else would like to contribute, please let me know be responding to this email. We can decide on a precise set of dates later. Of course, there's no reason we have to wait for the sprint to start crossing these off, but in practice having a dedicated block of time set aside always helps. Thanks, Andrew
Hi Andrew, I’m in. Due to some issue of my VISA for re-entering US, I just got back last week, and am able to do some work from now. Best wishes, -- Suoqing JI Ph.D Candidate Department of Physics University of California, Santa Barbara http://web.physics.ucsb.edu/~suoqing
On Feb 2, 2016, at 1:04 PM, Andrew Myers <atmyers2@gmail.com> wrote:
Dear yt developers,
At the team meeting today, we discussed having a mini-sprint to finish off the remaining VR refactor stuff in preparation for a 3.3 release. I've gone through the open issues, and sorted them into the following categories. The first five categories are for issues that, IMO, represent significant usability concerns and block a 3.3 release:
1) Improved Narrative Docs and Cookbook Recipes: Issues 1110 <https://bitbucket.org/yt_analysis/yt/issues/1110/experimental-vr-camera-move...>, 1112 <https://bitbucket.org/yt_analysis/yt/issues/1112/experimental-document-how-t...>, 1128 <https://bitbucket.org/yt_analysis/yt/issues/1128/experimental-describe-using...> 2) Transfer Function Usability Issues: 1098 <https://bitbucket.org/yt_analysis/yt/issues/1098/experimental-enhanced-docum...>, 1104 <https://bitbucket.org/yt_analysis/yt/issues/1104/experimental-transfer-funct...> 3) Alpha Issues with Render Sources: 1129 <https://bitbucket.org/yt_analysis/yt/issues/1133/experimental-alpha-seems-no...>, 1133 <https://bitbucket.org/yt_analysis/yt/issues/1133/experimental-alpha-seems-no...> 4) Units Issue with the Camera: 1132 <https://bitbucket.org/yt_analysis/yt/issues/1132/experimental-camerawidth-is...> 5) Manual Use of the Off-Axis Projection transfer function: 1103 <https://bitbucket.org/yt_analysis/yt/issues/1103/experimental-render-with>
There are a few categories of issues that, while they would certainly be nice to include, do not IMO *need* to be included in 3.3. These are:
1) Camera Path stuff: 1115 <https://bitbucket.org/yt_analysis/yt/issues/1115/experimental-add-in-keyfram...>, 1116 <https://bitbucket.org/yt_analysis/yt/issues/1116/experimental-making-vr-work...>, 2) new VR annotations for lines and rays: 1126 <https://bitbucket.org/yt_analysis/yt/issues/1126/experimental-add-annotate_r...> 3) Speed up the Perspective Lens and make it the default in the docs. 1121 <https://bitbucket.org/yt_analysis/yt/issues/1121/experimental-speed-up-persp...>
If you disagree with any of these classifications, or if I've left something out, please let me know.
Some time in the coming weeks, I think it would be good to dedicate a few person-days of effort to a mini-sprint to finish these issues off. I'd be game for such an effort myself, and I know that Nathan mentioned at the hangout that he'd be willing to help, too. If anyone else would like to contribute, please let me know be responding to this email. We can decide on a precise set of dates later. Of course, there's no reason we have to wait for the sprint to start crossing these off, but in practice having a dedicated block of time set aside always helps.
Thanks, Andrew _______________________________________________ yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
I've been meaning to reengage on yt hacking for a while, so I'd happily participate in a mini-sprint. Because of teaching, Thurs and Friday works best for me, so if it overlaps with one of those days, I'll try to clear my day to contribute. On Tue, Feb 2, 2016 at 4:04 PM, Andrew Myers <atmyers2@gmail.com> wrote:
Dear yt developers,
At the team meeting today, we discussed having a mini-sprint to finish off the remaining VR refactor stuff in preparation for a 3.3 release. I've gone through the open issues, and sorted them into the following categories. The first five categories are for issues that, IMO, represent significant usability concerns and block a 3.3 release:
1) Improved Narrative Docs and Cookbook Recipes: Issues 1110 <https://bitbucket.org/yt_analysis/yt/issues/1110/experimental-vr-camera-move...>, 1112 <https://bitbucket.org/yt_analysis/yt/issues/1112/experimental-document-how-t...>, 1128 <https://bitbucket.org/yt_analysis/yt/issues/1128/experimental-describe-using...> 2) Transfer Function Usability Issues: 1098 <https://bitbucket.org/yt_analysis/yt/issues/1098/experimental-enhanced-docum...>, 1104 <https://bitbucket.org/yt_analysis/yt/issues/1104/experimental-transfer-funct...> 3) Alpha Issues with Render Sources: 1129 <https://bitbucket.org/yt_analysis/yt/issues/1133/experimental-alpha-seems-no...>, 1133 <https://bitbucket.org/yt_analysis/yt/issues/1133/experimental-alpha-seems-no...> 4) Units Issue with the Camera: 1132 <https://bitbucket.org/yt_analysis/yt/issues/1132/experimental-camerawidth-is...> 5) Manual Use of the Off-Axis Projection transfer function: 1103 <https://bitbucket.org/yt_analysis/yt/issues/1103/experimental-render-with>
There are a few categories of issues that, while they would certainly be nice to include, do not IMO *need* to be included in 3.3. These are:
1) Camera Path stuff: 1115 <https://bitbucket.org/yt_analysis/yt/issues/1115/experimental-add-in-keyfram...>, 1116 <https://bitbucket.org/yt_analysis/yt/issues/1116/experimental-making-vr-work...> , 2) new VR annotations for lines and rays: 1126 <https://bitbucket.org/yt_analysis/yt/issues/1126/experimental-add-annotate_r...> 3) Speed up the Perspective Lens and make it the default in the docs. 1121 <https://bitbucket.org/yt_analysis/yt/issues/1121/experimental-speed-up-persp...>
If you disagree with any of these classifications, or if I've left something out, please let me know.
Some time in the coming weeks, I think it would be good to dedicate a few person-days of effort to a mini-sprint to finish these issues off. I'd be game for such an effort myself, and I know that Nathan mentioned at the hangout that he'd be willing to help, too. If anyone else would like to contribute, please let me know be responding to this email. We can decide on a precise set of dates later. Of course, there's no reason we have to wait for the sprint to start crossing these off, but in practice having a dedicated block of time set aside always helps.
Thanks, Andrew
_______________________________________________ yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
-- Michael Zingale Associate Professor Dept. of Physics & Astronomy • Stony Brook University • Stony Brook, NY 11794-3800 *phone*: 631-632-8225 *e-mail*: Michael.Zingale@stonybrook.edu *web*: http://www.astro.sunysb.edu/mzingale github: http://github.com/zingale
Hi Andrew, I've recently had to do a bunch with manual/semi-manual scaling of alpha and lines and whatnot, so I'd like to tackle those. I think the hardest one is going to be the color transfer function and the log/lin limits. I spent some time working on this with Sam and I think we came to the conclusion that the best way forward is to make some backwards-incompatible new object that was a hybrid of CTF and TFHelper, so that it can correctly manage stuff. I will try to leave some comments on the bug about why this is tricky. -Matt On Tue, Feb 2, 2016 at 3:04 PM, Andrew Myers <atmyers2@gmail.com> wrote:
Dear yt developers,
At the team meeting today, we discussed having a mini-sprint to finish off the remaining VR refactor stuff in preparation for a 3.3 release. I've gone through the open issues, and sorted them into the following categories. The first five categories are for issues that, IMO, represent significant usability concerns and block a 3.3 release:
1) Improved Narrative Docs and Cookbook Recipes: Issues 1110 <https://bitbucket.org/yt_analysis/yt/issues/1110/experimental-vr-camera-move...>, 1112 <https://bitbucket.org/yt_analysis/yt/issues/1112/experimental-document-how-t...>, 1128 <https://bitbucket.org/yt_analysis/yt/issues/1128/experimental-describe-using...> 2) Transfer Function Usability Issues: 1098 <https://bitbucket.org/yt_analysis/yt/issues/1098/experimental-enhanced-docum...>, 1104 <https://bitbucket.org/yt_analysis/yt/issues/1104/experimental-transfer-funct...> 3) Alpha Issues with Render Sources: 1129 <https://bitbucket.org/yt_analysis/yt/issues/1133/experimental-alpha-seems-no...>, 1133 <https://bitbucket.org/yt_analysis/yt/issues/1133/experimental-alpha-seems-no...> 4) Units Issue with the Camera: 1132 <https://bitbucket.org/yt_analysis/yt/issues/1132/experimental-camerawidth-is...> 5) Manual Use of the Off-Axis Projection transfer function: 1103 <https://bitbucket.org/yt_analysis/yt/issues/1103/experimental-render-with>
There are a few categories of issues that, while they would certainly be nice to include, do not IMO *need* to be included in 3.3. These are:
1) Camera Path stuff: 1115 <https://bitbucket.org/yt_analysis/yt/issues/1115/experimental-add-in-keyfram...>, 1116 <https://bitbucket.org/yt_analysis/yt/issues/1116/experimental-making-vr-work...> , 2) new VR annotations for lines and rays: 1126 <https://bitbucket.org/yt_analysis/yt/issues/1126/experimental-add-annotate_r...> 3) Speed up the Perspective Lens and make it the default in the docs. 1121 <https://bitbucket.org/yt_analysis/yt/issues/1121/experimental-speed-up-persp...>
If you disagree with any of these classifications, or if I've left something out, please let me know.
Some time in the coming weeks, I think it would be good to dedicate a few person-days of effort to a mini-sprint to finish these issues off. I'd be game for such an effort myself, and I know that Nathan mentioned at the hangout that he'd be willing to help, too. If anyone else would like to contribute, please let me know be responding to this email. We can decide on a precise set of dates later. Of course, there's no reason we have to wait for the sprint to start crossing these off, but in practice having a dedicated block of time set aside always helps.
Thanks, Andrew
_______________________________________________ yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
participants (4)
-
Andrew Myers -
Matthew Turk -
Michael Zingale -
Suoqing Ji