[Yt-svn] commit/yt-doc: MatthewTurk: Fixed some build errors

[Bitbucket]

1 new changeset in yt-doc:

http://bitbucket.org/yt_analysis/yt-doc/changeset/fbaff21b4eb5/
changeset:   fbaff21b4eb5
user:        MatthewTurk
date:        2011-08-26 04:39:17
summary:     Fixed some build errors
affected #:  2 files (35 bytes)

--- a/source/analysis_modules/halo_profiling.rst	Thu Aug 25 22:00:08 2011 -0400
+++ b/source/analysis_modules/halo_profiling.rst	Thu Aug 25 22:39:17 2011 -0400
@@ -16,7 +16,7 @@
 your script inside an mpirun call with the --parallel flag at the end.
 
 Configuring the Halo Profiler
-----------------------------
+-----------------------------
 
 A sample script to run the halo profiler can be found in :ref:`cookbook-run_halo_profiler`.  
 In order to run the halo profiler on a dataset, a halo profiler object must be instantiated 
@@ -97,12 +97,9 @@
  * **velocity_center** (*list*): the method in which the halo bulk velocity is
    calculated (used for calculation of radial and tangential velocities.  Valid
    options are:
-     	- ["bulk", "halo"] (Default): the velocity provided in the halo list
-        - ["bulk", "sphere"]: the bulk velocity of the sphere centered on the
-          halo center.
-    	- ["max", field]: the velocity of the cell that is the location of
-    	  the maximum of the field specified (used only when halos set to
-    	  single).
+   - ["bulk", "halo"] (Default): the velocity provided in the halo list
+   - ["bulk", "sphere"]: the bulk velocity of the sphere centered on the halo center.
+   - ["max", field]: the velocity of the cell that is the location of the maximum of the field specified (used only when halos set to single).
 
  * **filter_quantities** (*list*): quantities from the original halo list
    file to be written out in the filtered list file.  Default: ['id','center'].


--- a/source/analysis_modules/running_halofinder.rst	Thu Aug 25 22:00:08 2011 -0400
+++ b/source/analysis_modules/running_halofinder.rst	Thu Aug 25 22:39:17 2011 -0400
@@ -148,19 +148,18 @@
     are the 2D projected distance.
 
 .. _load_haloes:
+
 Loading Haloes Off Disk
 -----------------------
 
 It is possible to load haloes off disk and use them as if they had just been
-located by the halo finder. This has at least two advantages.
-Quite obviously this
-means that if the halos are properly saved (e.g. ``haloes.dump()``, see above
-and below),
-halo finding does not need to be run again, saving time. Another benefit is
-loaded haloes only use as much memory as needed because the particle data for
-the haloes is loaded off disk on demand. If only a few haloes are being
-examined, a dataset that required parallel analysis for halo finding can be
-analyzed in serial, interactively.
+located by the halo finder. This has at least two advantages.  Quite obviously
+this means that if the halos are properly saved (e.g. ``haloes.dump()``, see
+above and below), halo finding does not need to be run again, saving time.
+Another benefit is loaded haloes only use as much memory as needed because the
+particle data for the haloes is loaded off disk on demand. If only a few haloes
+are being examined, a dataset that required parallel analysis for halo finding
+can be analyzed in serial, interactively.
 
 The first step is to save the haloes in a consistent manner, which is made
 simple with the ``.dump()`` function:

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.