[Yt-svn] commit/yt-doc: sskory: Adding docs on the choice of kDtree for parallelHF.

[Bitbucket]

1 new commit in yt-doc:


https://bitbucket.org/yt_analysis/yt-doc/changeset/ece182e303d4/
changeset:   ece182e303d4
user:        sskory
date:        2011-11-04 23:42:06
summary:     Adding docs on the choice of kDtree for parallelHF.
affected #:  1 file

diff -r 32a415868313fe3aaacb91e1d82b34637a67d6e2 -r ece182e303d4ebb80ea339fb983039c2b8ea9e70 source/analysis_modules/running_halofinder.rst
--- a/source/analysis_modules/running_halofinder.rst
+++ b/source/analysis_modules/running_halofinder.rst
@@ -391,6 +391,12 @@
     with this option turned on.  Not all haloes are changed between runs.  This is
     due to the way merging happens in HOP - pre-merging destroys the global
     determinacy of halo merging. Default=True.
+  * ``tree``, string: There are two kD-trees that may be used as part of the
+    halo-finding process. The Fortran ("F") one is (presently) faster, but requires
+    more memory. One based on `scipy.spatial
+    <http://docs.scipy.org/doc/scipy/reference/spatial.html>`_ utilizes
+    Cython ("C") and is (presently) slower, but is more memory efficient.
+    Default = "F".
 
 All the same halo data can be accessed from Parallel HOP haloes as with the other halo finders.
 However, when running in parallel, there are some

Repository URL: https://bitbucket.org/yt_analysis/yt-doc/

--

This is a commit notification from bitbucket.org. You are receiving
this because you have the service enabled, addressing the recipient of
this email.