New issue 954: Poor quality text when saving as eps; bounding box issues when saving as ps
Running the attached script gives two output files--one is eps, and the other ps. The eps version has very poor-quality text. The ps version has better text, but the bounding box appears to be incorrect in its horizontal dimensions, as it cuts off axis and colorbar labels.
New issue 953: Unassigned variable being referenced when trying to save slice plot as eps using eps.single_plot
Running the attached script will throw an error stating that _p1 hasn't been assigned. Looking at the code, _p1 is only conditionally assigned; in this case, self.canvas=None, so the assignment isn't happening.
When this is fixed, I believe there will still be an error in axis_box_yt() in the file eps_writer.py. The trouble comes from the line
_xrange = (0, width * plot.ds[units])
This throws a key error.
New issue 952: loading hierarchy before parallel_objects causes barrier mismatch
Loading hierarchy before entering parallel_objects causes barrier mismatch and the process hangs indefinitely. Everything goes well when all cpus are running the operation, but this happens when some of the cpus are idle.
Here's the minimal example that produces the problem in yt 2.6 when run with -np 2.
Out of three objects, the process hangs when the third projection is finished and a barrier is opened.
from yt.config import ytcfg
ytcfg['yt', 'loglevel'] = '1'
from yt.mods import *
import numpy as np
cs = np.random.rand(3, 3)
def do(c, pf):
cube = pf.h.region(c, c-0.1, c+0.1)
proj = pf.h.proj(2, 'Density', source=cube)
for c in parallel_objects(cs):
if __name__ == '__main__':
pf = load('../../enzo_tiny_cosmology/DD0046/DD0046')
Looking at the log, it seems that the number of barriers opened is very different depending on whether pf.h is called before parallel_objects or not.
If it is called, a barrier is opened many times, and always opened after one projection is finished.
If not, it is only called once on each cpu when all objects allocated to it is processed (which seems natural)
yt-dev mailing list
I set it up for my own use (having a fresh install to test my Julia wrapper against), but in case anyone is interested, I’ve set up nighty builds for Linux x86_64 and Windows x86_64 on Binstar:
It takes the current source code from Bitbucket (from yt_analysis) and builds a binary that can be installed using Anaconda.
Fellow yt users:
We at the yt development team want to make yt better for you, the user. We
have prepared a short survey to gain your valuable feedback to help us
understand what is working in yt and what is not. Could you please spare 2
minutes to fill out our survey below?
We plan to collect responses and make available a selection of results
10, so please let us know what you think at the following URL:
On behalf of the yt development team,
University of Arizona
I'd like to nominate Suoqing Ji to be a yt project member. Suoqing has
been making tons of great contributions recently, and I think giving him
commit rights on the bitbucket repository is more than justified.