[yt-svn] commit/yt: 4 new changesets
commits-noreply at bitbucket.org
commits-noreply at bitbucket.org
Fri Aug 4 23:47:26 PDT 2017
4 new commits in yt:
https://bitbucket.org/yt_analysis/yt/commits/956ffd925f35/
Changeset: 956ffd925f35
User: xarthisius
Date: 2017-08-05 01:15:59+00:00
Summary: Replace unicode double quotation mark with ascii
Affected #: 4 files
diff -r 73d27659e3b280ec7f665210eb712704c6f698b9 -r 956ffd925f35bb29ac7edb365dc3f1b31e6d66f2 doc/source/analyzing/analysis_modules/halo_catalogs.rst
--- a/doc/source/analyzing/analysis_modules/halo_catalogs.rst
+++ b/doc/source/analyzing/analysis_modules/halo_catalogs.rst
@@ -309,7 +309,7 @@
^^^^^^^^^^
A quantity is a call back that returns a value or values. The return values
-are stored within the halo object in a dictionary called “quantities.” At
+are stored within the halo object in a dictionary called "quantities." At
the end of the analysis, all of these quantities will be written to disk as
the final form of the generated halo catalog.
diff -r 73d27659e3b280ec7f665210eb712704c6f698b9 -r 956ffd925f35bb29ac7edb365dc3f1b31e6d66f2 doc/source/analyzing/units/3)_Comoving_units_and_code_units.ipynb
--- a/doc/source/analyzing/units/3)_Comoving_units_and_code_units.ipynb
+++ b/doc/source/analyzing/units/3)_Comoving_units_and_code_units.ipynb
@@ -171,7 +171,7 @@
"\n",
"As an aside, Darren Croton's [research note](http://arxiv.org/abs/1308.4150) on the history, use, and interpretation of $h$ as it appears in the astronomical literature is pretty much required reading for anyone who has to deal with factors of $h$ every now and then.\n",
"\n",
- "In yt, comoving length unit symbols are named following the pattern “(length symbol)cm”, i.e. `pccm` for comoving parsec or `mcm` for a comoving meter. A comoving length unit is different from the normal length unit by a factor of $(1+z)$:"
+ "In yt, comoving length unit symbols are named following the pattern `(length symbol)cm`, i.e. `pccm` for comoving parsec or `mcm` for a comoving meter. A comoving length unit is different from the normal length unit by a factor of $(1+z)$:"
]
},
{
diff -r 73d27659e3b280ec7f665210eb712704c6f698b9 -r 956ffd925f35bb29ac7edb365dc3f1b31e6d66f2 doc/source/reference/changelog.rst
--- a/doc/source/reference/changelog.rst
+++ b/doc/source/reference/changelog.rst
@@ -941,7 +941,7 @@
* An order of magnitude speed improvement in the RAMSES support
* Quad-tree projections, speeding up the process of projecting by up to an
order of magnitude and providing better load balancing
- * “mapserver” for in-browser, Google Maps-style slice and projection
+ * "mapserver" for in-browser, Google Maps-style slice and projection
visualization (see :ref:`mapserver`)
* Many bug fixes and performance improvements
* Halo loader
diff -r 73d27659e3b280ec7f665210eb712704c6f698b9 -r 956ffd925f35bb29ac7edb365dc3f1b31e6d66f2 yt/utilities/grid_data_format/docs/gdf_specification.txt
--- a/yt/utilities/grid_data_format/docs/gdf_specification.txt
+++ b/yt/utilities/grid_data_format/docs/gdf_specification.txt
@@ -13,7 +13,7 @@
#. We avoid having many attributes on many nodes, as access can be quite slow
#. Cartesian data only for now
#. All grids must have the same number of ghost zones.
-#. If “/grid_parent” does not exist, parentage relationships will be
+#. If "/grid_parent" does not exist, parentage relationships will be
reconstructed and assumed to allow multiple grids
#. No parentage can skip levels
#. All grids are at the same time
@@ -173,7 +173,7 @@
``domain_dimensions``
dimensions in the top grid
``current_time``
- current time in simulation, in seconds, from “start” of simulation
+ current time in simulation, in seconds, from "start" of simulation
``domain_left_edge``
the left edge of the domain, in cm
``domain_right_edge``
https://bitbucket.org/yt_analysis/yt/commits/c813b7c735b8/
Changeset: c813b7c735b8
User: xarthisius
Date: 2017-08-05 02:13:33+00:00
Summary: Fix yt.LinePlot call in docs
Affected #: 1 file
diff -r 956ffd925f35bb29ac7edb365dc3f1b31e6d66f2 -r c813b7c735b81d62c3a594d30d3c87944a17c37e doc/source/visualizing/plots.rst
--- a/doc/source/visualizing/plots.rst
+++ b/doc/source/visualizing/plots.rst
@@ -1146,7 +1146,8 @@
ds = yt.load("SecondOrderTris/RZ_p_no_parts_do_nothing_bcs_cone_out.e", step=-1)
plot = yt.LinePlot(ds, [('all', 'v'), ('all', 'u')], [0, 0, 0], [0, 1, 0],
- 100, labels={('all', 'u') : r"v$_x$", ('all', 'v') : r"v$_y$"})
+ 100, field_labels={('all', 'u') : r"v$_x$",
+ ('all', 'v') : r"v$_y$"})
plot.annotate_legend(('all', 'u'))
plot.save()
https://bitbucket.org/yt_analysis/yt/commits/8933c88740e4/
Changeset: 8933c88740e4
User: ngoldbaum
Date: 2017-08-05 02:59:56+00:00
Summary: fix mysterious h5py failure in docs build
Affected #: 1 file
diff -r c813b7c735b81d62c3a594d30d3c87944a17c37e -r 8933c88740e49345694aad6e6d6a1763121e7caa yt/units/yt_array.py
--- a/yt/units/yt_array.py
+++ b/yt/units/yt_array.py
@@ -886,7 +886,7 @@
d = g[dataset_name]
# Overwrite without deleting if we can get away with it.
if d.shape == self.shape and d.dtype == self.dtype:
- d[:] = self
+ d[...] = self
for k in d.attrs.keys():
del d.attrs[k]
else:
https://bitbucket.org/yt_analysis/yt/commits/90ac8cf152c1/
Changeset: 90ac8cf152c1
User: ngoldbaum
Date: 2017-08-05 06:46:37+00:00
Summary: Merge pull request #1525 from Xarthisius/unicode_fix
Replace unicode double quotation mark with ascii
Affected #: 6 files
diff -r 73d27659e3b280ec7f665210eb712704c6f698b9 -r 90ac8cf152c12131bdc709653db7e433c5ddd4d3 doc/source/analyzing/analysis_modules/halo_catalogs.rst
--- a/doc/source/analyzing/analysis_modules/halo_catalogs.rst
+++ b/doc/source/analyzing/analysis_modules/halo_catalogs.rst
@@ -309,7 +309,7 @@
^^^^^^^^^^
A quantity is a call back that returns a value or values. The return values
-are stored within the halo object in a dictionary called “quantities.” At
+are stored within the halo object in a dictionary called "quantities." At
the end of the analysis, all of these quantities will be written to disk as
the final form of the generated halo catalog.
diff -r 73d27659e3b280ec7f665210eb712704c6f698b9 -r 90ac8cf152c12131bdc709653db7e433c5ddd4d3 doc/source/analyzing/units/3)_Comoving_units_and_code_units.ipynb
--- a/doc/source/analyzing/units/3)_Comoving_units_and_code_units.ipynb
+++ b/doc/source/analyzing/units/3)_Comoving_units_and_code_units.ipynb
@@ -171,7 +171,7 @@
"\n",
"As an aside, Darren Croton's [research note](http://arxiv.org/abs/1308.4150) on the history, use, and interpretation of $h$ as it appears in the astronomical literature is pretty much required reading for anyone who has to deal with factors of $h$ every now and then.\n",
"\n",
- "In yt, comoving length unit symbols are named following the pattern “(length symbol)cm”, i.e. `pccm` for comoving parsec or `mcm` for a comoving meter. A comoving length unit is different from the normal length unit by a factor of $(1+z)$:"
+ "In yt, comoving length unit symbols are named following the pattern `(length symbol)cm`, i.e. `pccm` for comoving parsec or `mcm` for a comoving meter. A comoving length unit is different from the normal length unit by a factor of $(1+z)$:"
]
},
{
diff -r 73d27659e3b280ec7f665210eb712704c6f698b9 -r 90ac8cf152c12131bdc709653db7e433c5ddd4d3 doc/source/reference/changelog.rst
--- a/doc/source/reference/changelog.rst
+++ b/doc/source/reference/changelog.rst
@@ -941,7 +941,7 @@
* An order of magnitude speed improvement in the RAMSES support
* Quad-tree projections, speeding up the process of projecting by up to an
order of magnitude and providing better load balancing
- * “mapserver” for in-browser, Google Maps-style slice and projection
+ * "mapserver" for in-browser, Google Maps-style slice and projection
visualization (see :ref:`mapserver`)
* Many bug fixes and performance improvements
* Halo loader
diff -r 73d27659e3b280ec7f665210eb712704c6f698b9 -r 90ac8cf152c12131bdc709653db7e433c5ddd4d3 doc/source/visualizing/plots.rst
--- a/doc/source/visualizing/plots.rst
+++ b/doc/source/visualizing/plots.rst
@@ -1146,7 +1146,8 @@
ds = yt.load("SecondOrderTris/RZ_p_no_parts_do_nothing_bcs_cone_out.e", step=-1)
plot = yt.LinePlot(ds, [('all', 'v'), ('all', 'u')], [0, 0, 0], [0, 1, 0],
- 100, labels={('all', 'u') : r"v$_x$", ('all', 'v') : r"v$_y$"})
+ 100, field_labels={('all', 'u') : r"v$_x$",
+ ('all', 'v') : r"v$_y$"})
plot.annotate_legend(('all', 'u'))
plot.save()
diff -r 73d27659e3b280ec7f665210eb712704c6f698b9 -r 90ac8cf152c12131bdc709653db7e433c5ddd4d3 yt/units/yt_array.py
--- a/yt/units/yt_array.py
+++ b/yt/units/yt_array.py
@@ -886,7 +886,7 @@
d = g[dataset_name]
# Overwrite without deleting if we can get away with it.
if d.shape == self.shape and d.dtype == self.dtype:
- d[:] = self
+ d[...] = self
for k in d.attrs.keys():
del d.attrs[k]
else:
diff -r 73d27659e3b280ec7f665210eb712704c6f698b9 -r 90ac8cf152c12131bdc709653db7e433c5ddd4d3 yt/utilities/grid_data_format/docs/gdf_specification.txt
--- a/yt/utilities/grid_data_format/docs/gdf_specification.txt
+++ b/yt/utilities/grid_data_format/docs/gdf_specification.txt
@@ -13,7 +13,7 @@
#. We avoid having many attributes on many nodes, as access can be quite slow
#. Cartesian data only for now
#. All grids must have the same number of ghost zones.
-#. If “/grid_parent” does not exist, parentage relationships will be
+#. If "/grid_parent" does not exist, parentage relationships will be
reconstructed and assumed to allow multiple grids
#. No parentage can skip levels
#. All grids are at the same time
@@ -173,7 +173,7 @@
``domain_dimensions``
dimensions in the top grid
``current_time``
- current time in simulation, in seconds, from “start” of simulation
+ current time in simulation, in seconds, from "start" of simulation
``domain_left_edge``
the left edge of the domain, in cm
``domain_right_edge``
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