Hi all,
There has been some lag with the bitbucket API lately. Unfortunately
when Fido tries to pull changes via the API it shows no changes even if
there are new changes via the web interface.
Long story short, if fido says your tests fail, take a look at the console
log. If it says near the bottom that there was nothing to merge in, you've
hit the bitbucket API issue.
Nathan
Hey everyone,
I just discovered by accident that one can now generate a TimeSeries
DatasetSeries object with the load() command in yt-3.0.
import yt
time_series = yt.load('DD????/DD????')
for ds in time_series:
print ds.current_time
I don't know when this functionality was created or by whom, but it's great
and simplifies the timeseries analysis steps. Does it work for all
frontends?
I'm happy to update the timeseries documentation with this information, but
I wanted to make sure it worked with all frontends, and see if there were
any other new tricks that were added when this functionality was added .so
we don't have to iterate too much on the docs update. Since I didn't write
this functionality, I don't know what else was done and it doesn't look
like it was written down in the docs.
Cameron
--
Cameron Hummels
Postdoctoral Researcher
Steward Observatory
University of Arizona
http://chummels.org
Hi, I'd like to add some BoxLib datasets to the suite of public datasets
available for testing and experiementation. Can someone point me to the
procedure of how to do that? and any guidelines regarding size. Also, are
both 2- and 3-d (and 1-d?) datasets acceptable there?
Thanks,
Mike
--
Michael Zingale
Associate Professor
Dept. of Physics & Astronomy • Stony Brook University • Stony Brook, NY
11794-3800
*phone*: 631-632-8225
*e-mail*: Michael.Zingale(a)stonybrook.edu
*web*: http://www.astro.sunysb.edu/mzingale
Hi all,
A group of us are here in Austin for the scipy conference. Today we're
going to be sprinting on yt, focusing mostly on closing tickets for the
yt-3.0 release. If you're in Austin, please feel free to come on down to
the AT&T center to meet with us. My cell phone number is 720-201-2231 -
give me a call if you need help finding us.
We'd love to have remote participants. I will be watching the IRC channel
- we could probably also set up a google hangout if there is interest.
Hope you all are having a great Friday :)
-Nathan
Hi all,
Can we get some eyes on the SDF pull request? Since the that uses it
went out yesterday, I was hoping to get it in, as long as we can
identify any blockers that can and will be addressed before 3.0 goes
out.
https://bitbucket.org/yt_analysis/yt/pull-request/955/wip-sdf-frontend-an...
I think it now depends on thingking when actually being used for http
SDF, but that's pure python and easy to install.
-Matt
Hi Folks!
So, I'm trying to build yt with python3. My python/c is still noobish,
but so far I've converted everything with 2to3, however I'm getting some
errors in regards to the kdtree libraries. I was wondering if anybody has
tried a python3 build and/or if anybody has an idea on how to properly
install new kdtree libraries for python3?
Thanks for any insights!
-Jill
Hi all,
Has anyone tried to build YT using a recent version of Forthon? I've been building using 0.8.10 on an older Python installation but when I use any of 3 installations using Forthon 0.8.13 (pip installed, 0.8.15 is current) it fails due to misunderstanding how to construct the module fortran file from the module name:
Traceback (most recent call last):
File "/software/python-2.7-2014q2-el6-x86_64/bin/Forthon", line 2, in <module>
import Forthon.Forthon_builder
File "/software/python-2.7-2014q2-el6-x86_64/lib/python2.7/site-packages/Forthon/Forthon_builder.py", line 87, in <module>
raise Exception('Main fortran file can not be found, please specify using the fortranfile option')
Exception: Main fortran file can not be found, please specify using the fortranfile option
....
subprocess.CalledProcessError: Command '['/software/python-2.7-2014q2-el6-x86_64/bin/Forthon', '-F', 'gfortran', '--compile_first', 'fKD_source', '--no2underscores', '--fopt', "'-O3'", 'fKD', 'fKD_source.f90']' returned non-zero exit status 1
Looking through the differences in Forthon_builder.py between those two versions looks like fortranfile is set to a default in the older version:
0.8.10:34 fortranfile = options.fortranfile or (pkg + '.' + options.fixed_suffix)
0.8.13:34 fortranfile = options.fortranfile
Adding a --fortranfile option for fKD.f90 seems to work, but I'm not certain this is the correct solution. I'll submit a PR for the following change unless anyone else has a better idea (or reason it's a bad idea):
setup.py:63
cmd = [Forthon_exe, "-F", "gfortran", "--compile_first",
"fKD_source", "--no2underscores", "--fopt", "'-O3'", "fKD",
"fKD_source.f90"]
->
cmd = [Forthon_exe, "-F", "gfortran", "--compile_first",
"fKD_source", "--no2underscores", "--fopt", "'-O3'", "-f", "fKD.f90",
"fKD", "fKD_source.f90"]
Douglas Rudd
Scientific Computing Consultant
Research Computing Center
drudd(a)uchicago.edu
New issue 854: Different dimensions for coordinates and fields in `smoothed_covering_grid`
https://bitbucket.org/yt_analysis/yt/issue/854/different-dimensions-for-c...
John ZuHone:
This script:
```
#!python
import yt
import numpy as np
pf = yt.load("GasSloshing/sloshing_nomag2_hdf5_plt_cnt_0150")
L = 617. # width in kpc
dx = 2.*pf.index.get_smallest_dx().in_units("kpc").v
nx = int(L/dx)
le = pf.arr([-0.5*nx*dx]*3, "kpc").in_units("code_length").v
dims = np.array([nx]*3)
cube = pf.smoothed_covering_grid(pf.index.max_level-1, le, dims)
print cube["x"].shape
print cube["density"].shape
```
Gives this output:
```
#!python
(131, 131, 131)
(132, 132, 132)
```
So the shapes of the coordinates and the fields have gotten out of sync somehow. This only happens for certain values of `L` and `nx`, setting `L = 600.` results in both dimensions being the same.
