<div dir="ltr">Awesome!! This is great news! I've poked around at some of them, but there are many dark corners of the code that I don't necessarily understand, so having you take a shot will help immensely. Thanks, Matt!<div>
<br></div><div>Cameron</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Jun 25, 2014 at 12:18 PM, 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 Cameron,<br>
<div class=""><br>
On Tue, Jun 24, 2014 at 8:35 PM, Cameron Hummels <<a href="mailto:chummels@gmail.com">chummels@gmail.com</a>> wrote:<br>
> I will continue to work on these, but you're right, we need more people<br>
> working on these little issues or this will continue to be a big blocker and<br>
> not get done. I can assign specific bugs to the specialists on those<br>
> issues, if it is helpful (see below).<br>
><br>
> For all issues, see this page:<br>
> <a href="https://trello.com/c/NJMfoXdl/22-be-able-to-run-the-cookbook" target="_blank">https://trello.com/c/NJMfoXdl/22-be-able-to-run-the-cookbook</a> . Reading the<br>
> description can give you some clues as to the source of the error, but the<br>
> best way to diagnose it is simply to go into the doc cookbook directory and<br>
> try to run the python script:<br>
><br>
> e.g.<br>
> $ cd $YT_DEST/doc/source/cookbook<br>
> $ python script.py<br>
><br>
><br>
><br>
> * VR - KDTree issues (Sam Skillman? Matt Turk?)<br>
> ----amrkdtree_downsampling.py<br>
> ----camera_movement.py -- something going on with statusbar in brick<br>
> counting!<br>
> ----opaque_rendering.py -- same as camera_movement.py<br>
> ----render_with_box_and_grids.py<br>
<br>
</div>Sam and I will work out which goes to which of us, but I will probably<br>
take these on.<br>
<div class=""><br>
><br>
> * Light Rays and Light Cones (Britton Smith, John Zuhone, Devin Silvia)<br>
> ----make_light_ray.py<br>
> ----unique_light_cone_projections.py<br>
> ----light_cone_projection.py<br>
> ----light_cone_with_halo_mask.py<br>
><br>
> * Profiles (Matt Turk, Nathan Goldbaum, other?)<br>
> ----global_phase_plots.py<br>
> ----profile_with_variance.py<br>
> ----rad_velocity.py<br>
> ----radial_profile_styles.py?<br>
> ----simple_profile.py<br>
> ----time_series_profiles.py<br>
> ----save_profiles.py<br>
<br>
</div>I will take all of these.<br>
<div class=""><br>
><br>
> * Units working with everything in yt (Nathan Goldbaum, Matt Turk, John<br>
> Zuhone)<br>
> ----hse_field.py<br>
> ----simple_off_axis_projection.py<br>
><br>
<br>
</div>I think either Nathan or John, if they have time, might be good for<br>
these. Failing that, I will.<br>
<div class=""><br>
> * Miscellany<br>
> ----aligned_cutting_plane.py -- something is wrong with the derived quantity<br>
> AngularMomentumVector() in that it doesn't work fully for gas, but seems to<br>
> work OK for particles.<br>
> ----free_free_field.py--creating a new derived field (Matt Turk, Nathan<br>
> Goldbaum)<br>
> ----simple_slice_with_multiple_fields.py -- vorticity_squared fails as a<br>
> field.<br>
<br>
</div>I'll do these.<br>
<br>
To summarize, here are the recipes I have committed to fixing:<br>
<br>
global_phase_plots.py<br>
profile_with_variance.py<br>
rad_velocity.py<br>
radial_profile_styles.py?<br>
simple_profile.py<br>
time_series_profiles.py<br>
save_profiles.py<br>
aligned_cutting_plane.py<br>
free_free_field.py<br>
simple_slice_with_multiple_fields.py<br>
<br>
and probably also:<br>
<br>
amrkdtree_downsampling.py<br>
camera_movement.py<br>
opaque_rendering.py<br>
render_with_box_and_grids.py<br>
<br>
-Matt<br>
<div class="HOEnZb"><div class="h5"><br>
><br>
><br>
> This is by no means a requirement to work on this, but it would help to take<br>
> a look at it to see if you can help correct a small bug here and there if<br>
> your name is listed here (or even if it isn't!)<br>
><br>
> Cameron<br>
><br>
><br>
><br>
> On Tue, Jun 24, 2014 at 6:09 PM, Nathan Goldbaum <<a href="mailto:nathan12343@gmail.com">nathan12343@gmail.com</a>><br>
> wrote:<br>
>><br>
>> Ah - I see that now.<br>
>><br>
>> Yes, I agree that fixing the cookbook should be a blocker. FWIW that card<br>
>> is marked as such. As I said the other day, the blockers are on the yt-3.0<br>
>> and the documentation board. We won't do the yt-3.0 release until all the<br>
>> cards marked as blockers are cleared.<br>
>><br>
>> This is a big task - any help we can get on this from anyone following<br>
>> along would be much appreciated. There are a lot of little tasks or tasks<br>
>> that can be completed in a couple hours by anyone that has a little with<br>
>> yt-3.0.<br>
>><br>
>><br>
>> On Tue, Jun 24, 2014 at 6:04 PM, Cameron Hummels <<a href="mailto:chummels@gmail.com">chummels@gmail.com</a>><br>
>> wrote:<br>
>>><br>
>>> I think all of the cookbook items are blockers to be honest, because the<br>
>>> cookbook recipes should be tests that are seen as failing.<br>
>>><br>
>>> <a href="https://trello.com/c/NJMfoXdl/22-be-able-to-run-the-cookbook" target="_blank">https://trello.com/c/NJMfoXdl/22-be-able-to-run-the-cookbook</a><br>
>>><br>
>>><br>
>>> On Tue, Jun 24, 2014 at 5:32 PM, Nathan Goldbaum <<a href="mailto:nathan12343@gmail.com">nathan12343@gmail.com</a>><br>
>>> wrote:<br>
>>>><br>
>>>><br>
>>>><br>
>>>> On Tuesday, June 24, 2014, Cameron Hummels <<a href="mailto:chummels@gmail.com">chummels@gmail.com</a>> wrote:<br>
>>>>><br>
>>>>> I think there remain some issues in the VR working in 3.0, which I<br>
>>>>> identified on the cookbook post on the trello board for yt-3.0. For<br>
>>>>> example, I know the overlaying grids and overlaying boundaries does not<br>
>>>>> currently work.<br>
>>>><br>
>>>><br>
>>>> I don't see this on trello. Can you make a card and mark it as a<br>
>>>> blocker?<br>
>>>><br>
>>>>><br>
>>>>> That may be an easy fix, but it's something to keep in mind. I was<br>
>>>>> going to work on it last week as I was doing the cookbook update, but I<br>
>>>>> figured it was just going to get replaced with the scene interface, so it<br>
>>>>> wasn't worth the time.<br>
>>>>><br>
>>>>> I guess I'd still like to have all of the API breakage occur in the big<br>
>>>>> jump from 2.x to 3.0, but if people really want to get 3.0 out the door<br>
>>>>> asap, then perhaps that isn't compatible. Personally, I'm +1 on waiting to<br>
>>>>> have all the halo+VR stuff in 3.0 instead of 3.1, but if everyone else wants<br>
>>>>> a 3.0 out sooner, I will not block it. I think having a super fancy VR and<br>
>>>>> awesome halo interface is one of the big pulls to getting people who have<br>
>>>>> not yet switched to join 3.0 (from both 2.x as well as non-users) even if it<br>
>>>>> takes a few more months, but I may be the minority here.<br>
>>>>><br>
>>>>> Cameron<br>
>>>>><br>
>>>>><br>
>>>>> On Tue, Jun 24, 2014 at 10:08 AM, Nathan Goldbaum<br>
>>>>> <<a href="mailto:nathan12343@gmail.com">nathan12343@gmail.com</a>> wrote:<br>
>>>>>><br>
>>>>>> Ok - I think the script in the issue description is sufficient. Let<br>
>>>>>> me know if you need something more detailed.<br>
>>>>>><br>
>>>>>><br>
>>>>>> On Tue, Jun 24, 2014 at 10:07 AM, Matthew Turk <<a href="mailto:matthewturk@gmail.com">matthewturk@gmail.com</a>><br>
>>>>>> wrote:<br>
>>>>>>><br>
>>>>>>> That's the one -- you mentioned it in a blockers email a few days<br>
>>>>>>> ago.<br>
>>>>>>><br>
>>>>>>> On Tue, Jun 24, 2014 at 12:06 PM, Nathan Goldbaum<br>
>>>>>>> <<a href="mailto:nathan12343@gmail.com">nathan12343@gmail.com</a>> wrote:<br>
>>>>>>> > Sorry - not sure which issue you're talking about - this one maybe?<br>
>>>>>>> ><br>
>>>>>>> ><br>
>>>>>>> > <a href="https://bitbucket.org/yt_analysis/yt/issue/827/enzo-particle-fields-work-differently-than" target="_blank">https://bitbucket.org/yt_analysis/yt/issue/827/enzo-particle-fields-work-differently-than</a><br>
>>>>>>> ><br>
>>>>>>> ><br>
>>>>>>> ><br>
>>>>>>> ><br>
>>>>>>> > On Tue, Jun 24, 2014 at 10:02 AM, Matthew Turk<br>
>>>>>>> > <<a href="mailto:matthewturk@gmail.com">matthewturk@gmail.com</a>><br>
>>>>>>> > wrote:<br>
>>>>>>> >><br>
>>>>>>> >> Related to that, do you have a reproducible script for the<br>
>>>>>>> >> particle<br>
>>>>>>> >> issue you reported? If so, could you add that to either an issue<br>
>>>>>>> >> or a<br>
>>>>>>> >> trello card so I can work on it?<br>
>>>>>>> >><br>
>>>>>>> >> On Tue, Jun 24, 2014 at 11:58 AM, Nathan Goldbaum<br>
>>>>>>> >> <<a href="mailto:nathan12343@gmail.com">nathan12343@gmail.com</a>><br>
>>>>>>> >> wrote:<br>
>>>>>>> >> > I'd be +1 on this plan, although we should note that this is the<br>
>>>>>>> >> > plan in<br>
>>>>>>> >> > the<br>
>>>>>>> >> > release announcement. We may also want to note that there are<br>
>>>>>>> >> > some<br>
>>>>>>> >> > issues<br>
>>>>>>> >> > with volume rendering of oct and particle data at the moment (I<br>
>>>>>>> >> > believe<br>
>>>>>>> >> > that's the case - let me know if I'm wrong there).<br>
>>>>>>> >> ><br>
>>>>>>> >> > I think that leaves analysis modules and documentation as the<br>
>>>>>>> >> > main<br>
>>>>>>> >> > blockers<br>
>>>>>>> >> > for a 3.0 release.<br>
>>>>>>> >> ><br>
>>>>>>> >> > -Nathan<br>
>>>>>>> >> ><br>
>>>>>>> >> ><br>
>>>>>>> >> ><br>
>>>>>>> >> > On Tue, Jun 24, 2014 at 9:53 AM, John ZuHone <<a href="mailto:jzuhone@gmail.com">jzuhone@gmail.com</a>><br>
>>>>>>> >> > wrote:<br>
>>>>>>> >> >><br>
>>>>>>> >> >> +1 on Matt's proposal. -1 on a beta.<br>
>>>>>>> >> >><br>
>>>>>>> >> >> My worry about a beta release is that it will slow adoption,<br>
>>>>>>> >> >> whether<br>
>>>>>>> >> >> rightly or wrongly. I think we agree that we're ready to<br>
>>>>>>> >> >> encourage<br>
>>>>>>> >> >> adoption<br>
>>>>>>> >> >> of 3.0.<br>
>>>>>>> >> >><br>
>>>>>>> >> >> John ZuHone<br>
>>>>>>> >> >> Laboratory for High-Energy Astrophysics<br>
>>>>>>> >> >> NASA/Goddard Space Flight Center<br>
>>>>>>> >> >> 8800 Greenbelt Rd., Mail Code 662<br>
>>>>>>> >> >> Greenbelt, MD 20771<br>
>>>>>>> >> >> (w) <a href="tel:301-286-2531" value="+13012862531">301-286-2531</a><br>
>>>>>>> >> >> (m) <a href="tel:781-708-5004" value="+17817085004">781-708-5004</a><br>
>>>>>>> >> >> <a href="mailto:john.zuhone@nasa.gov">john.zuhone@nasa.gov</a><br>
>>>>>>> >> >> <a href="mailto:jzuhone@gmail.com">jzuhone@gmail.com</a><br>
>>>>>>> >> >><br>
>>>>>>> >> >> > On Jun 24, 2014, at 12:38 PM, Matthew Turk<br>
>>>>>>> >> >> > <<a href="mailto:matthewturk@gmail.com">matthewturk@gmail.com</a>><br>
>>>>>>> >> >> > wrote:<br>
>>>>>>> >> >> ><br>
>>>>>>> >> >> > I think Britton covered the halos, but the VR works as-is.<br>
>>>>>>> >> >> > As far as<br>
>>>>>>> >> >> > 3.0beta, I'm a bit nervous about that as we want to avoid the<br>
>>>>>>> >> >> > situation where we are in beta for 1+ years... I am worried<br>
>>>>>>> >> >> > about the<br>
>>>>>>> >> >> > perception of a "beta" tag. Is that overblown? Would<br>
>>>>>>> >> >> > calling it<br>
>>>>>>> >> >> > "yt-3.0-2014" work?<br>
>>>>>>> >> >> ><br>
>>>>>>> >> >> >> On Tue, Jun 24, 2014 at 10:32 AM, Nathan Goldbaum<br>
>>>>>>> >> >> >> <<a href="mailto:nathan12343@gmail.com">nathan12343@gmail.com</a>> wrote:<br>
>>>>>>> >> >> >> Do the old VR and halo interfaces work? Not much effort has<br>
>>>>>>> >> >> >> gone<br>
>>>>>>> >> >> >> into<br>
>>>>>>> >> >> >> porting them, I think.<br>
>>>>>>> >> >> >><br>
>>>>>>> >> >> >><br>
>>>>>>> >> >> >>> On Tuesday, June 24, 2014, Sam Skillman<br>
>>>>>>> >> >> >>> <<a href="mailto:samskillman@gmail.com">samskillman@gmail.com</a>><br>
>>>>>>> >> >> >>> wrote:<br>
>>>>>>> >> >> >>><br>
>>>>>>> >> >> >>> I'm +1 on this, particularly since I'm at fault for not<br>
>>>>>>> >> >> >>> pushing on<br>
>>>>>>> >> >> >>> the<br>
>>>>>>> >> >> >>> VR<br>
>>>>>>> >> >> >>> as much as I'd like to.<br>
>>>>>>> >> >> >>><br>
>>>>>>> >> >> >>><br>
>>>>>>> >> >> >>> On Tue, Jun 24, 2014 at 7:44 AM, Matthew Turk<br>
>>>>>>> >> >> >>> <<a href="mailto:matthewturk@gmail.com">matthewturk@gmail.com</a>><br>
>>>>>>> >> >> >>> wrote:<br>
>>>>>>> >> >> >>>><br>
>>>>>>> >> >> >>>> Hi all,<br>
>>>>>>> >> >> >>>><br>
>>>>>>> >> >> >>>> One thing we really tried to do with 3.0 was break all the<br>
>>>>>>> >> >> >>>> APIs we<br>
>>>>>>> >> >> >>>> thought we'd need to before release. This included things<br>
>>>>>>> >> >> >>>> like<br>
>>>>>>> >> >> >>>> ds/pf,<br>
>>>>>>> >> >> >>>> index/hierarchy, the way data selections were made, etc.<br>
>>>>>>> >> >> >>>><br>
>>>>>>> >> >> >>>> It's starting to become clear that we are approaching<br>
>>>>>>> >> >> >>>> maturity at<br>
>>>>>>> >> >> >>>> different rates in these initiatives. I am wondering if<br>
>>>>>>> >> >> >>>> perhaps<br>
>>>>>>> >> >> >>>> we<br>
>>>>>>> >> >> >>>> should de-couple the release from all of the API<br>
>>>>>>> >> >> >>>> breakages, and<br>
>>>>>>> >> >> >>>> instead note which interfaces we know are going to change<br>
>>>>>>> >> >> >>>> in the<br>
>>>>>>> >> >> >>>> future.<br>
>>>>>>> >> >> >>>><br>
>>>>>>> >> >> >>>> Pragmatically, what this would mean is:<br>
>>>>>>> >> >> >>>><br>
>>>>>>> >> >> >>>> * Release a 3.0 with the old VR and halo finding<br>
>>>>>>> >> >> >>>> interfaces<br>
>>>>>>> >> >> >>>> * Release a 3.1 with either the new VR or the new halo<br>
>>>>>>> >> >> >>>> finding (or<br>
>>>>>>> >> >> >>>> both)<br>
>>>>>>> >> >> >>>> * Do the same for 3.2<br>
>>>>>>> >> >> >>>><br>
>>>>>>> >> >> >>>> This doesn't fit with the usual "major numbers are where<br>
>>>>>>> >> >> >>>> APIs<br>
>>>>>>> >> >> >>>> break"<br>
>>>>>>> >> >> >>>> philosophy that comes from semantic versioning, but I<br>
>>>>>>> >> >> >>>> think from<br>
>>>>>>> >> >> >>>> the<br>
>>>>>>> >> >> >>>> perspective of pragmatism, if we identify those sections<br>
>>>>>>> >> >> >>>> of the<br>
>>>>>>> >> >> >>>> code<br>
>>>>>>> >> >> >>>> that are *going* to change, and we pitch 3.0 as the first<br>
>>>>>>> >> >> >>>> part of<br>
>>>>>>> >> >> >>>> a<br>
>>>>>>> >> >> >>>> staged release of totally rewritten infrastructure, we can<br>
>>>>>>> >> >> >>>> likely<br>
>>>>>>> >> >> >>>> come<br>
>>>>>>> >> >> >>>> out okay.<br>
>>>>>>> >> >> >>>><br>
>>>>>>> >> >> >>>> I'd like to put this out there for discussion.<br>
>>>>>>> >> >> >>>><br>
>>>>>>> >> >> >>>> -Matt<br>
>>>>>>> >> >> >>>> _______________________________________________<br>
>>>>>>> >> >> >>>> yt-dev mailing list<br>
>>>>>>> >> >> >>>> <a href="mailto:yt-dev@lists.spacepope.org">yt-dev@lists.spacepope.org</a><br>
>>>>>>> >> >> >>>><br>
>>>>>>> >> >> >>>> <a href="http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org" target="_blank">http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org</a><br>
>>>>>>> >> >> >><br>
>>>>>>> >> >> >> _______________________________________________<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" target="_blank">http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org</a><br>
>>>>>>> >> >> > _______________________________________________<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" target="_blank">http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org</a><br>
>>>>>>> >> >> _______________________________________________<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" target="_blank">http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org</a><br>
>>>>>>> >> ><br>
>>>>>>> >> ><br>
>>>>>>> >> ><br>
>>>>>>> >> > _______________________________________________<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" target="_blank">http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org</a><br>
>>>>>>> >> ><br>
>>>>>>> >> _______________________________________________<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" target="_blank">http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org</a><br>
>>>>>>> ><br>
>>>>>>> ><br>
>>>>>>> ><br>
>>>>>>> > _______________________________________________<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" target="_blank">http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org</a><br>
>>>>>>> ><br>
>>>>>>> _______________________________________________<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" target="_blank">http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org</a><br>
>>>>>><br>
>>>>>><br>
>>>>>><br>
>>>>>> _______________________________________________<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" target="_blank">http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org</a><br>
>>>>>><br>
>>>>><br>
>>>>><br>
>>>>><br>
>>>>> --<br>
>>>>> Cameron Hummels<br>
>>>>> Postdoctoral Researcher<br>
>>>>> Steward Observatory<br>
>>>>> University of Arizona<br>
>>>>> <a href="http://chummels.org" target="_blank">http://chummels.org</a><br>
>>>><br>
>>>><br>
>>>> _______________________________________________<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" target="_blank">http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org</a><br>
>>>><br>
>>><br>
>>><br>
>>><br>
>>> --<br>
>>> Cameron Hummels<br>
>>> Postdoctoral Researcher<br>
>>> Steward Observatory<br>
>>> University of Arizona<br>
>>> <a href="http://chummels.org" target="_blank">http://chummels.org</a><br>
>>><br>
>>> _______________________________________________<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" target="_blank">http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org</a><br>
>>><br>
>><br>
>><br>
>> _______________________________________________<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" target="_blank">http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org</a><br>
>><br>
><br>
><br>
><br>
> --<br>
> Cameron Hummels<br>
> Postdoctoral Researcher<br>
> Steward Observatory<br>
> University of Arizona<br>
> <a href="http://chummels.org" target="_blank">http://chummels.org</a><br>
><br>
> _______________________________________________<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" target="_blank">http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org</a><br>
><br>
_______________________________________________<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" target="_blank">http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org</a><br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br>Cameron Hummels<div>Postdoctoral Researcher</div><div>Steward Observatory</div><div>University of Arizona</div><div><a href="http://chummels.org" target="_blank">http://chummels.org</a></div>
</div>