New issue 585: plot collection add_projection not working?
When I try to run a very basic projection plot with yt 3.0 I get the following error:
pc.add_projection("Density", 'x', "Density")
/Users/kstewart/code/yt-3.0/yt-x86_64/src/yt-3.0-hg/yt/visualization/plot_collection.py in add_projection(self, field, axis, weight_field, data_source, center, use_colorbar, figure, axes, fig_size, periodic, obj, field_parameters)
781 obj = self.pf.hierarchy.proj(field, axis, weight_field,
782 source = data_source, center=center,
--> 783 **field_parameters)
784 p = self._add_plot(PCProjectionPlot(obj, field,
785 use_colorbar=use_colorbar, axes=axes, figure=figure,
TypeError: __init__() got an unexpected keyword argument 'source'
Not sure what's going on here. Looks like some kind of bug since this same code works perfectly in 2.5
We're proud to release yt version 2.5.3. This is a scheduled point
release that includes all bug fixes identified and fixed since the
release of 2.5.2 on May 1.
Additions, changes and bug fixes include:
* yt can now export to RADMC3D
* Athena frontend now supports Static Mesh Refinement and units (
* PlotWindows now have a set_font function and a new default font setting
* Colorbars less likely to extend off the edge of a PlotWindow
* Clumps overplotted on PlotWindows are now correctly contoured
* Allsky projections and HEALpix camera now correctly use four channels (RGBA)
* Many fixes to light ray and profiles for integrated cosmological analysis
* Improvements to OpenMP compilation
* Typo in value for km_per_pc (not used elsewhere in the code base)
has been fixed
* Enable parallel IPython notebook sessions (
* Change (~1e-6) to particle_density deposition, enabling it to be
used by FLASH and other frontends
* Addition of is_root function for convenience in parallel analysis sessions
* Additions to Orion particle reader
* Fix long-standing bug for plotting arrays with range of zero
* Fixing TotalMass for case when particles not present
* Fixing the density threshold or HOP and pHOP to match the merger tree
* Reason can now plot with latest plot window
* Adding option to have interpolation based on non-uniform bins in
* Issues with VelocityMagnitude and aliases with velo have been
corrected in the FLASH frontend
* Halo radii are calculated correctly for domains that do not start at 0,0,0.
* Halo mass function now works for non-Enzo frontends.
* Bug fixes for directory creation, typos in docstrings
If you are using the stable branch of yt from an installation script,
you can upgrade using "yt update" or "yt update --all" to upgrade your
full dependency stack. If you are using the development branch, you
may already have these fixes. A tarball of this release has been
uploaded to the Python Package Index (PyPI).
This release includes a total of over 150 changesets, contributed over
the course of nearly 40 pull requests by over a dozen individuals.
The next scheduled release will be on July 1, and will be version 2.6.
We are hoping to include a unification of the Boxlib frontends,
compatibility with Python 3 (and embedding inside Blender) and other
usual improvements to the yt codebase.
Documentation for this release can be found at:
Thanks very much,
Matt, on behalf of the yt development team
We're proud to announce the second ALPHA release of yt 3.0. yt has
recently transitioned to a time-based release plan (
https://ytep.readthedocs.org/en/latest/YTEPs/YTEP-0008.html ) and this
is the second scheduled alpha of 3.0. No date for a "final" release
has yet been set.
The yt 2.5 codebase, and further updates in the 2.x series, will be
supported for a considerable amount of time and you do not need to
= yt 3.0?! =
yt 3.0 represents a new direction forward for yt: getting rid of all
the underlying assumptions that data needs to be sectioned off into
nice little grid patches. This includes supporting Octree codes
natively (NMSU-ART and RAMSES), eventual support for SPH codes, and
even opaque data structures where the data is extremely large (ARTIO).
We're even planning support for natively handling cylindrical and
However, this *is* an alpha release. Not all of the existing codes
have been ported to 3.0.
Additionally, this release benefits from the technical and
non-technical contributions from many new people. yt is developed in
the context of a community of contributors, and with the push toward a
new architecture, we aim to expand that community considerably. In
particular, this release has considerably benefited from contributions
from many new individuals.
= Getting It! =
To try out yt 3.0, you can now pull from the main yt repository,
update to the yt-3.0 branch, and rebuild your extensions. Or, if you
would like to create a new, safely sectioned off environment, simply
re-run the normal "development" install script after changing the
variable BRANCH to "yt-3.0".
If you would like to try out yt 3.0 and are having trouble, please
write to the yt-users mailing list for assistance.
The yt 3.0 install script may also work, which can be obtained by
executing these commands:
= Examples =
New functionality can be seen in IPython notebooks available on the yt
data Hub. In particular, these notebooks demonstrate many of the
functionality that has been added for PKDgrav, Gasoline, Gadget, Enzo,
* Enzo: https://hub.yt-project.org/nb/tzeizy
* Gadget: https://hub.yt-project.org/nb/abu5nb
* RAMSES: https://hub.yt-project.org/nb/5zw7qn
* PKDgrav: https://hub.yt-project.org/nb/mp46a6
* Gasoline: https://hub.yt-project.org/nb/dfncvy
(Apologies for the SSL warning on the Hub site.)
= Reporting Problems =
If you test out yt 3.0 we want to hear if it DID or DID NOT work!
Feedback is crucial at this time. yt-users and yt-dev are both good
forums for discussion, asking questions, and reporting problems. Lots
of things have changed on the backend, but we have attempted to
minimize the user-facing changes.
To report a bug please go here:
Note that you will not receive updates if you are not logged in when
you create the bug.
= What's Next? =
The next alpha release (3.0a3) is scheduled to be released on July 15,
2013, but development can be monitored either at
http://bitbucket.org/yt_analysis/yt-3.0 or in the main yt repository
under the named branch "yt-3.0". We hope to have ready for inclusion
additional improvements to Octree codes, a units implementation for
arrays, a field naming scheme overhaul, and further robustness for
particle codes. We also are hoping to include the first attempts to
apply SPH smoothing kernels to SPH particles.
We anticipate that the next alpha release will involve more invasive
changes to the array handling and units handling code, and may include
a large number of field renaming operations. Aliases to old fields
will be provided at that time.
Many bug fixes from the mainline of 2.X development have not been
merged into the yt-3.0 repository. Bringing these bugfixes in will
occur sometime in the next few weeks.
If you'd like to participate in yt development, please stop by #yt on
irc.freenode.net ( http://yt-project.org/irc.html ) or yt-dev (
http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org ), or
submit a pull request on BitBucket.
Thanks very much,
Matt, on behalf of the yt development team