[yt-svn] commit/yt: 3 new changesets
commits-noreply at bitbucket.org
commits-noreply at bitbucket.org
Wed Jul 30 09:16:37 PDT 2014
3 new commits in yt:
https://bitbucket.org/yt_analysis/yt/commits/d957650f2e74/
Changeset: d957650f2e74
Branch: yt-3.0
User: brittonsmith
Date: 2014-07-30 17:36:03
Summary: Small doc update.
Affected #: 1 file
diff -r c259c6a5f8ac42834e77c4056bdb635de93620c8 -r d957650f2e744f3afb10c083bd042b8454a0e5f9 doc/source/analyzing/objects.rst
--- a/doc/source/analyzing/objects.rst
+++ b/doc/source/analyzing/objects.rst
@@ -440,14 +440,8 @@
Often, when operating interactively or via the scripting interface, it is
convenient to save an object or multiple objects out to disk and then restart
-the calculation later. Personally, I found this most useful when dealing with
-identification of clumps and contours (see :ref:`cookbook` for a recipe on how
-to find clumps and the API documentation for both
-:mod:`~yt.analysis_modules.level_sets.contour_finder.identify_contours`
-and :mod:`~yt.analysis_modules.level_sets.clump_handling.Clump`) where
-the identification step can be quite time-consuming, but the analysis
-may be relatively fast.
-
+the calculation later. For example, this is useful after clump finding
+(:ref:`clump_finding`), which can be very time consuming.
Typically, the save and load operations are used on 3D data objects. ``yt``
has a separate set of serialization operations for 2D objects such as
projections.
@@ -461,13 +455,6 @@
difficult; the object, when reloaded, must be able to reconstruct a dataset
from whatever limited information it has in the save file.
-To do this, ``yt`` is able to identify datasets based on a "hash"
-generated from the base file name, the "CurrentTimeIdentifier", and the
-simulation time. These three characteristics should never be changed outside
-of a simulation, they are independent of the file location on disk, and in
-conjunction they should be uniquely identifying. (This process is all done in
-:mod:`~yt.utilities.ParameterFileStorage` via :class:`~yt.utilities.ParameterFileStorage.ParameterFileStore`.)
-
You can save objects to an output file using the function
:meth:`~yt.data_objects.index.save_object`:
https://bitbucket.org/yt_analysis/yt/commits/e1de4628570d/
Changeset: e1de4628570d
Branch: yt-3.0
User: brittonsmith
Date: 2014-07-30 17:45:22
Summary: A little more.
Affected #: 1 file
diff -r d957650f2e744f3afb10c083bd042b8454a0e5f9 -r e1de4628570dd8a0b2130b2e02cc3a7bd44781ef doc/source/analyzing/objects.rst
--- a/doc/source/analyzing/objects.rst
+++ b/doc/source/analyzing/objects.rst
@@ -431,7 +431,11 @@
The key for the first (outer) dict is the level of the contour, corresponding
to ``contour_values``. The inner dict returned is keyed by the contour ID. It
contains :class:`~yt.data_objects.selection_data_containers.YTCutRegionBase`
-objects. These can be queried just as any other data object.
+objects. These can be queried just as any other data object. The clump finder
+(:ref:`clump_finding`) differs from the above method in that the contour
+identification is performed recursively within each individual structure, and
+structures can be kept or remerged later based on additional criteria, such as
+gravitational boundedness.
.. _object-serialization:
https://bitbucket.org/yt_analysis/yt/commits/cde920145491/
Changeset: cde920145491
Branch: yt-3.0
User: ngoldbaum
Date: 2014-07-30 18:16:31
Summary: Merged in brittonsmith/yt/yt-3.0 (pull request #1105)
Contour and object saving docs updates.
Affected #: 1 file
diff -r 7a4a92f8887989509680ce553cb982ea205479de -r cde920145491deec2aeb335e7dbec901a51fd356 doc/source/analyzing/objects.rst
--- a/doc/source/analyzing/objects.rst
+++ b/doc/source/analyzing/objects.rst
@@ -431,7 +431,11 @@
The key for the first (outer) dict is the level of the contour, corresponding
to ``contour_values``. The inner dict returned is keyed by the contour ID. It
contains :class:`~yt.data_objects.selection_data_containers.YTCutRegionBase`
-objects. These can be queried just as any other data object.
+objects. These can be queried just as any other data object. The clump finder
+(:ref:`clump_finding`) differs from the above method in that the contour
+identification is performed recursively within each individual structure, and
+structures can be kept or remerged later based on additional criteria, such as
+gravitational boundedness.
.. _object-serialization:
@@ -440,14 +444,8 @@
Often, when operating interactively or via the scripting interface, it is
convenient to save an object or multiple objects out to disk and then restart
-the calculation later. Personally, I found this most useful when dealing with
-identification of clumps and contours (see :ref:`cookbook` for a recipe on how
-to find clumps and the API documentation for both
-:mod:`~yt.analysis_modules.level_sets.contour_finder.identify_contours`
-and :mod:`~yt.analysis_modules.level_sets.clump_handling.Clump`) where
-the identification step can be quite time-consuming, but the analysis
-may be relatively fast.
-
+the calculation later. For example, this is useful after clump finding
+(:ref:`clump_finding`), which can be very time consuming.
Typically, the save and load operations are used on 3D data objects. ``yt``
has a separate set of serialization operations for 2D objects such as
projections.
@@ -461,13 +459,6 @@
difficult; the object, when reloaded, must be able to reconstruct a dataset
from whatever limited information it has in the save file.
-To do this, ``yt`` is able to identify datasets based on a "hash"
-generated from the base file name, the "CurrentTimeIdentifier", and the
-simulation time. These three characteristics should never be changed outside
-of a simulation, they are independent of the file location on disk, and in
-conjunction they should be uniquely identifying. (This process is all done in
-:mod:`~yt.utilities.ParameterFileStorage` via :class:`~yt.utilities.ParameterFileStorage.ParameterFileStore`.)
-
You can save objects to an output file using the function
:meth:`~yt.data_objects.index.save_object`:
Repository URL: https://bitbucket.org/yt_analysis/yt/
--
This is a commit notification from bitbucket.org. You are receiving
this because you have the service enabled, addressing the recipient of
this email.
More information about the yt-svn
mailing list