Hey Stephen and Matt.

Thanks for letting me know. Yeah, too bad the scipy version isn't up to the performance we need.

- Casey

On Tue, Aug 7, 2012 at 4:10 PM, Stephen Skory <s@skory.us> wrote:
Hi Matt,

> Casey was asking about which components use Forthon.  My understanding
> is that it's only an indirect hard requirement, and that the things
> that use it are the merger tree you wrote (not the one that works on
> Enzo-FOF output), the two point functions, and the pHOP halo finder.
> Is that right?

Ah, yes, I forgot to answer that. You're correct, Matt, those are the
places that the Fortran tree is used. In all honesty, the
scipy.spatial kDTree is good enough (in terms of speed) for all but
the halo finding, so that can someday be swapped out for the Fortran
one. Maybe I'll issue myself a ticket...

Stephen Skory
510.621.3687 (google voice)
yt-dev mailing list