There have been a number of cool new features in the pull request queue
recently. Some of these have added new features and I think it might be
worthwhile to indicate that by bumping the minor version number on the next
I think it would be a good idea to try to integrate the open PRs as well as
any that come in over the next couple of weeks that can be reviewed, call
it yt 3.1 and release on or around Dec. 1. This will mean generating a
proofread docs build and perhaps a few days of low-hanging issue triaging.
I'd nominate John ZuHone to send out the release email to recognize the
hard work he's been putting in recently.
Just an idea, but I've tried to include specifics as a basis for further
discussion. What do you all think?
New issue 931: Make `annotate_title` the standard method for setting the title in PhasePlot objects
Right now, `PhasePlot` and `PlotWindow` classes have separate methods for setting the figure title, `set_title()` and `annotate_title()` respectively. To reduce confusion, it might make sense to combine these to be just one of the two options.
New issue 930: np.concatenate fails for YTArrays
YTArrays cannot be compared using numpy functions like intersect1d because np.concatenate either fails (for dimensional arrays) or for dimensionless arrays it produces a YTArray object where the units attribute is `None` (which then fails in `__eq__`, `__lt__`, etc).
This may already be known and may be unfixable (due to the way numpy implements concatenate)...
import numpy as np
A = yt.YTArray(range(10))
B = yt.YTArray(range(10))
AttributeError Traceback (most recent call last)
<ipython-input-10-90c76c488fa7> in <module>()
----> 1 np.intersect1d(A,B)
/usr/local/lib/python2.7/site-packages/numpy/lib/arraysetops.pyc in intersect1d(ar1, ar2, assume_unique)
248 aux = np.concatenate((ar1, ar2))
--> 250 return aux[:-1][aux[1:] == aux[:-1]]
252 def setxor1d(ar1, ar2, assume_unique=False):
/Users/drudd/Programs/yt/yt/units/yt_array.pyc in __eq__(self, other)
854 return False
855 if isinstance(other, YTArray):
--> 856 if not self.units.same_dimensions_as(other.units):
857 raise YTUnitOperationError("equal", self.units, other.units)
AttributeError: 'NoneType' object has no attribute 'same_dimensions_as'
I know we nixed the previous notebook progress bar because it was really bogging things down—but it would be handy to have one, and there are some ASCII-only implementations that probably won’t use as much memory.
Any thoughts? I’d be happy to look into it myself.
(Moving over to yt-dev)
What do you think the major reasons to hold off on merging are?
On Mon, Oct 20, 2014 at 10:18 PM, Sam Skillman <samskillman(a)gmail.com> wrote:
> Hi Kiki,
> Thanks for the compliments on the volume rendering in yt. As of right now
> there isn't a simple way to add streamlines in the same figure. However, we
> are really close! There is a current work-in-progress [WIP] pull request
> where we are adding such a capability. What I'd suggest is to keep your
> ears open for new requests for testing the new framework and check back
> soon. I hope that by the end of the week we'll have some examples up on the
> pull request that would give you enough of a head start to try it out. I
> will try to remember to cc you when i send out requests for beta-testers.
> On Mon, Oct 20, 2014 at 6:02 PM, Dionysopoulou K.
> <K.Dionysopoulou(a)soton.ac.uk> wrote:
>> Dear Sir or Madam,
>> I recently came across the yt libraries for python and was impressed by
>> its capabilities and the speed of the volume renderer in particular. The
>> library creates superior quality figures and I would like to use it for my
>> papers. The problem I have for now is that I would like to have volume
>> rendering plus streamlines of a vector field in the same figure and I
>> haven’t figured out how one could do that. Is there a way to achieve this in
>> Thanking you in advance.
>> All the best,
>> Kyriaki Dionysopoulou
>> Mathematical Sciences
>> University of Southampton
>> Southampton, SO17 1BJ, UK
>> yt-users mailing list
> yt-users mailing list
FYI -- this may explain some issues last week.
---------- Forwarded message ----------
From: Mads Kiilerich <mads(a)kiilerich.com>
Date: Mon, Oct 20, 2014 at 2:22 PM
Subject: Mercurial & SSL & POODLE, Mercurial 2.7 and 2.7.1 and SSL
error: sslv3 alert handshake failure
To: "mercurial(a)selenic.com" <mercurial(a)selenic.com>
The recent POODLE story has raised the awareness of the problems with
old SSL versions. It might make sense to take the opportunity to
disable SSLv3 on web servers hosting Mercurial repositories.
Note however that there was a client side bug in Mercurial 2.7 and
2.7.1 that made it use SSLv3 without considering more recent versions.
Trying to connect to servers without SSLv3 with these Mercurial
versions will fail with something like:
abort: error: _ssl.c:507: error:14094410:SSL
routines:SSL3_READ_BYTES:sslv3 alert handshake failure
or if using TortoiseHg:
SSL error: sslv3 alert handshake failure
The solution is to upgrade Mercurial (or TortoiseHg) to a more recent version.
See also http://blogs.atlassian.com/2014/10/ssl-poodle/ .
Mercurial mailing list
yt-dev mailing list