Hi all,

Definitely.  I'm working on it right now actually.  I've nearly finished cleaning out the bugs from the merge with the yt (2.0) branch, and once that's done I'll get going on the docs.  Since my original kd-rendering branch was a branch off of what became "stable", there is a big merge changeset in there.  What I plan on doing is finishing the merge/docs today or tomorrow, and pushing the kd-rendering branch.  I don't quite feel comfortable merging that and the yt branch together, so I'll probably look for some help from Matt to make sure that it's all getting done the right way.  

The other option I see to "closing" the kd-rendering branch is to just add the functionality to the yt branch without going through the merging process.  Since the kd-tree stuff is mostly additions, the only merging has to do with camera.py and a function or two in the parallel_analysis_interface, this wouldn't be that difficult.  So, the question is: would you all (mostly Matt) rather just get rid of the kd-rendering branch and have me add what is needed to the "yt" branch or would you rather have me commit the rather huge merges, possibly making the stable->yt merge more complicated.  I'm happy doing either.

Anyways, I'm looking forward to this migration, and I think after a couple of updates to various user scripts it should be a great improvement!

Sam

--
Samuel W. Skillman
DOE Computational Science Graduate Fellow
Center for Astrophysics and Space Astronomy
University of Colorado at Boulder
samuel.skillman[at]colorado.edu