[yt-svn] commit/yt-doc: 2 new changesets

[Bitbucket]

2 new commits in yt-doc:


https://bitbucket.org/yt_analysis/yt-doc/changeset/96329c69ce22/
changeset:   96329c69ce22
user:        MatthewTurk
date:        2012-08-02 17:44:20
summary:     Adding a link to the external IPython notebook file.
affected #:  1 file

diff -r cd383f99a585d5e7def1d41ea97771b8f3bb721a -r 96329c69ce22129101682dc268a86a80c052af54 source/changelog.rst
--- a/source/changelog.rst
+++ b/source/changelog.rst
@@ -47,6 +47,10 @@
 The 2.4 release was particularly large, encompassing nearly a thousand
 changesets and a number of new features.
 
+To help you get up to speed, we've made an IPython notebook file demonstrating
+a few of the changes to the scripting API.  You can
+`download it here <http://yt-project.org/files/yt24.ipynb>`_.
+
 Most Visible Improvements
 ~~~~~~~~~~~~~~~~~~~~~~~~~
 



https://bitbucket.org/yt_analysis/yt-doc/changeset/02cfc68adcc0/
changeset:   02cfc68adcc0
user:        MatthewTurk
date:        2012-08-02 17:46:07
summary:     Merge
affected #:  1 file

diff -r 96329c69ce22129101682dc268a86a80c052af54 -r 02cfc68adcc0694de9cc53f236b43cf984919d3a source/analysis_modules/ellipsoid_analysis.rst
--- a/source/analysis_modules/ellipsoid_analysis.rst
+++ b/source/analysis_modules/ellipsoid_analysis.rst
@@ -13,11 +13,11 @@
 -------
 
 The purpose of creating this feature in YT is to analyze field
-properties that surrounds the dark matter halo.  Originally, this was
+properties that surround dark matter haloes.  Originally, this was
 usually done with the sphere 3D container, but since many halo
 particles are linked together in a more elongated shape, I thought it
 would be better to use an ellipsoid 3D container to wrap around the
-particles.  This way less of the empty-of-particle space around the
+particles.  This way, less of the empty-of-particle space around the
 halo would be included when doing the analysis of field properties
 where the particles are suppose to occupy.
 
@@ -30,9 +30,9 @@
 the y axis that will align the first semi-principle axis with the x
 axis once it is aligned in the x-z plane.)
 
-Once those parameters are determines, the function "ellipsoid" will
+Once those parameters are determined, the function "ellipsoid" will
 return the 3D object, and users will be able to get field attributes
-from the data object just they would from spheres, cylinders etc.
+from the data object just as they would from spheres, cylinders etc.
 
 Example
 -------
@@ -48,7 +48,7 @@
 And calculates the ellipsoid information needed for the 3D container.
 
 What I usually do is get this information from the halo finder output
-files in the .h5 HDF5 binary format. I load them in using the
+files in the .h5 HDF5 binary format. I load them into memory using the
 LoadHaloes() function instead of reading in the ASCII output.
 
 Halo Finding
@@ -73,7 +73,7 @@
   haloes = LoadHaloes(pf, 'MyHaloList')
 
 Once the halo information is saved you can load it into the data
-object haloes, you can get loop over the list of haloes and do
+object "haloes", you can get loop over the list of haloes and do
 
 .. code-block:: python
 
@@ -144,7 +144,8 @@
   smallest ellipsoid that contains the particles as possible.  To
   start at the center of the particles based on position will require
   an O(:math:`N^2`) operation, right now I'm trying to limit
-  everything to O(:math:`N`) operations.
+  everything to O(:math:`N`) operations.  If particle count does not
+  get too large, I may implement the O(:math:`N^2`) operation.
 * Currently the list of haloes can be analyzed using object
   parallelism (one halo per core), but I'm not sure if haloes will get
   big enough soon that other forms of parallelism will be needed to

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.