[yt-svn] commit/yt: 3 new changesets

commits-noreply at bitbucket.org commits-noreply at bitbucket.org
Tue Jul 29 20:56:27 PDT 2014


3 new commits in yt:

https://bitbucket.org/yt_analysis/yt/commits/e18513649bb6/
Changeset:   e18513649bb6
Branch:      yt-3.0
User:        MatthewTurk
Date:        2014-07-30 05:02:51
Summary:     Adding grids note.
Affected #:  1 file

diff -r cf0ab6db87aec986ff11bd5968c0e9203d90a5cf -r e18513649bb65e553e5c419212053eb4544e965e doc/source/yt3differences.rst
--- a/doc/source/yt3differences.rst
+++ b/doc/source/yt3differences.rst
@@ -57,6 +57,9 @@
     ``dd.quantities.total_mass()`` to do the same thing. All derived quantities
     can be accessed via a function that hangs off of the `quantities` attribute
     of data objects.
+  * You can't get the ``grids`` attribute of data objects.  To get this
+    information, you have to use spatial chunking and then access them.  (An
+    example is below.)
 
 Cool New Things
 ---------------
@@ -204,3 +207,21 @@
 +++++++++++++++
 
 Boolean regions are not yet implemented in yt 3.0.
+
+Grids
++++++
+
+It used to be that one could get access to the grids that belonged to a data
+object.  Because we no longer have just grid-based data in yt, this attribute
+does not make sense.  If you need to determine which grids contribute to a
+given object, you can either query the ``grid_indices`` field, or mandate
+spatial chunking like so:
+
+.. code-block:: python
+
+   for chunk in obj.chunks([], "spatial"):
+       for grid in chunk._current_chunk.objs:
+           print grid
+
+This will "spatially" chunk the ``obj`` object and print out all the grids
+included.


https://bitbucket.org/yt_analysis/yt/commits/8d61fa49fe61/
Changeset:   8d61fa49fe61
Branch:      yt-3.0
User:        MatthewTurk
Date:        2014-07-30 05:04:25
Summary:     Adding field deprecation note.
Affected #:  1 file

diff -r e18513649bb65e553e5c419212053eb4544e965e -r 8d61fa49fe6172bf4f131e8c823015da341f97c8 doc/source/yt3differences.rst
--- a/doc/source/yt3differences.rst
+++ b/doc/source/yt3differences.rst
@@ -144,6 +144,16 @@
 
    my_object["density"]
 
+To enable a compatibility layer, on the dataset you simply need to call the
+method ``setup_deprecated_fields`` like so:
+
+.. code-block:: python
+
+   ds = yt.load("MyData")
+   ds.setup_deprecated_fields()
+
+This sets up aliases from the old names to the new.
+
 Units of Fields
 +++++++++++++++
 


https://bitbucket.org/yt_analysis/yt/commits/d2c88a547e71/
Changeset:   d2c88a547e71
Branch:      yt-3.0
User:        ngoldbaum
Date:        2014-07-30 05:56:20
Summary:     Merged in MatthewTurk/yt/yt-3.0 (pull request #1101)

Extend yt23 differences file
Affected #:  1 file

diff -r 5c66a578b2470c405cd465bc1ca05bc400d696c9 -r d2c88a547e71b223491ca4a00fda7bc783eb2c3a doc/source/yt3differences.rst
--- a/doc/source/yt3differences.rst
+++ b/doc/source/yt3differences.rst
@@ -57,6 +57,9 @@
     ``dd.quantities.total_mass()`` to do the same thing. All derived quantities
     can be accessed via a function that hangs off of the `quantities` attribute
     of data objects.
+  * You can't get the ``grids`` attribute of data objects.  To get this
+    information, you have to use spatial chunking and then access them.  (An
+    example is below.)
 
 Cool New Things
 ---------------
@@ -141,6 +144,16 @@
 
    my_object["density"]
 
+To enable a compatibility layer, on the dataset you simply need to call the
+method ``setup_deprecated_fields`` like so:
+
+.. code-block:: python
+
+   ds = yt.load("MyData")
+   ds.setup_deprecated_fields()
+
+This sets up aliases from the old names to the new.
+
 Units of Fields
 +++++++++++++++
 
@@ -204,3 +217,21 @@
 +++++++++++++++
 
 Boolean regions are not yet implemented in yt 3.0.
+
+Grids
++++++
+
+It used to be that one could get access to the grids that belonged to a data
+object.  Because we no longer have just grid-based data in yt, this attribute
+does not make sense.  If you need to determine which grids contribute to a
+given object, you can either query the ``grid_indices`` field, or mandate
+spatial chunking like so:
+
+.. code-block:: python
+
+   for chunk in obj.chunks([], "spatial"):
+       for grid in chunk._current_chunk.objs:
+           print grid
+
+This will "spatially" chunk the ``obj`` object and print out all the grids
+included.

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