Greetings,
With the recent addition of a fantastic volume render to yt, people have
been creating some amazing visualizations. To showcase some of the
wonderful movies that yt users are making, we've set up video gallery here:
http://yt.enzotools.org/video_gallery.html
Made something great of your own? Submitting it to the gallery is easy.
First, get a free account on vimeo.com. Free accounts will allow you to
upload 500 Mb per week. Next, join the yt group on vimeo.com:
http://vimeo.com/groups/34915
When you upload your video and add it to the yt group, it will automatically
be added to the yt video gallery. And that's it!
We look forward to seeing what everyone is up to!
Britton Smith,
on behalf of the yt hive-mind.
Hey again YT community,
I was hoping to get some heading on using the simple volume rending
script that is written up in the YT cookbook, but it seems that
direct_ray_casting isn't a part of yt extensions anymore? Is there
something to substitute this? I see that in the software sample
script, there is a referencing of VolumeRendering, can I use this?
Thanks for your time and effort!
Nicholas Earl
Dear all,
in one of my scripts I have something like this:
pc = PlotCollection(pf, center=[0.5,0.5,0.5])
p = pc.add_projection("Temperature", 0, weight_field="Density")
p.modify["contour"]("Density", ncont=5, take_log=True)
...
...
...
pc.save("%s_temp-proj" % pf,override=True)
The saved file has a resolution of 800x800. Is there a way to change this
number in YT? I had a look in the PlotCollection class, but I haven't found
what I'm searching.
Looking forward to your suggestions,
Cheers
Luigi
--
---------------------------------------------------------------
Luigi Iapichino
Zentrum fuer Astronomie der Universitaet Heidelberg
Institut fuer Theoretische Astrophysik
Albert-Ueberle-Str. 2, D-69120 Heidelberg, Germany
Tel: +49 6221 548983, Fax: +49 6221 544221
e-mail: luigi(a)ita.uni-heidelberg.de
URL: http://www.ita.uni-heidelberg.de/~luigi/
Hi,
http://drop.io/Dark_Matter_Density
In the above plot, the label is Dark_Matter_Density. But the "M" in matter and "D" in Density do not print correctly.
How can I correct "M" and "D" ?
Here is the script I am using...
from yt.mods import *
fn = "RedshiftOutput0001"
pf = load(fn)
reg = pf.h.region([0.5, 0.5, 0.5], [0.45, 0.0, 0.0], [0.55, 1.0, 1.0])
pf.h.save_object(reg, "region")
reg1 = pf.h.load_object("region")
pc = PlotCollection(pf,center=[0.5, 0.5, 0.5])
p = pc.add_projection("Dark_Matter_Density", 0, source=reg1)
p.set_zlim(1e-8, 5e-3)
pc.save("%s" % pf)
Shankar
Hey YT community,
I was wondering if anyone had any sort of starting notion for a problem that
I face. I've done slices of a wave progressing in the x-y plane (the wave
front moves in the x-direction, from x = 0), what I want to do is take the
data from one specific x-value (i.e. a strip running the bounds of y at some
position x). I wanted to be able to plot the data -- for instance, density
-- (ideally, for my situation, it should be some sort of sinusoidal plot)
with density as the y axis and y position as the x-axis.
Is there anyway I could form this using YT?
Thanks for all your time and effort!
Nicholas Earl
Hi,
The projection, slice, velocity and overplot particles routines: They read the DM particles or gas ?
Looking at the density legend, it looks like this is baryon density field.
Is there a provision to plot projection and slice for DM ?
Also, I get this error when overplotting particles...
yt INFO 2010-03-22 12:17:44,051 Created plot collection with default plot-center = [0.5, 0.5, 0.5]
yt INFO 2010-03-22 12:17:44,144 Getting the binary hierarchy
yt INFO 2010-03-22 12:17:44,153 Finished with binary hierarchy reading
yt INFO 2010-03-22 12:17:46,108 Added slice of Density at x = 0.5 with 'center' = [0.5, 0.5, 0.5]
Traceback (most recent call last):
File "slice.py", line 42, in <module>
p.modify["nparticles"](0.005)
File "/autohome/u118/agarwa23/yt-x86_64/src/yt-1.6/yt/raven/PlotTypes.py", line 52, in __getitem__
raise KeyError(item)
KeyError: 'nparticles'
Shankar
Dear Colleague,
Please pass this email along to any researchers that you feel may be
interested, and apologies if you receive multiple copies of this
message.
The Enzo development consortium is pleased to announce the first Enzo
Users Workshop, which will take place at the San Diego Supercomputer
Center on June 28-30, 2010. This workshop will be take place shortly
after the release of Enzo 1.6, which will have several new features
(including MHD and radiation transport), and will be targeted at both
new and experienced Enzo users. We will present tutorials on both
beginning and advanced Enzo subjects, including running existing
simulation types, developing new problem initialization routines, and
data analysis and visualization using the 'yt' analysis package.
Several experienced Enzo users and developers will be available to
help users with both beginning and advanced questions.
The website for the workshop is http://lca.ucsd.edu/workshops/enzo2010
, which contains a mailing list sign up, draft schedule, and
accommodation details. We will be able to partially defray
accommodation costs for attending students. We hope to see you there!
Sincerely,
Matthew Turk, Michael Norman, and Brian O'Shea
(on behalf of the Enzo development team)
Hi all,
I've backported to trunk (r1664 & r1665) a bunch of the changes to the
volume rendering that have been going on in the mercurial repository.
If you're running on yt-1.6 (the stable branch) you can safely ignore
the rest of this message. Recall that "yt instinfo" may be able to
auto-upgrade your installation!
The full set of changes, from my SVN commits, is here:
* Updates to the time series code. It's now just about usable.
* Adding package parallel_tools, where we will be adding all NEW parallel
support code and migrating old code over to.
* Ray casting now works in parallel and with non-equal width/height values for
the output image. This necessitated a change in API.
* Added AMRInclinedBox data object.
* Heaviside function added to transfer functions.
* VolumeRendering is now an object. direct_ray_cast is now gone.
* Added Sam Skillman's image_handling module.
* Added HomogenizedBrickCollection and DistributedObjectCollection. These
were designed to parallelize the brick partitioning, but I believe we need a
new mechanism for that, so currently they do things but not 3D domain decomp.
* Adding preliminary support for both Chombo and Gadget.
* Vertex-centering is a tiny bit faster.
The big things to note are that we have support for very small gadget
datasets, in a very limited fashion. If you're interested in helping
out with this, let me know. Additionally, Jeff Oishi has added basic
support for Chombo datasets.
The biggest changes here are that the volume rendering has had a shift
in API -- this was to accommodate the fact that it is now parallel.
Previously, direct_ray_cast was to be called; now, the object itself
hangs off the hierarchy, like all other first-class objects in yt.
Where previously, one would import volume_rendering and then call
direct_ray_cast, now one would do something like this:
--
import yt.extensions.volume_rendering as vr
pf = load("DataDump0155.dir/DataDump0155")
W = 100.0/pf['au']
SIZE = 1024
c = pf.h.find_max("Density")
tf = vr.ColorTransferFunction((-14.0, -10.0))
tf.add_layers(8) # sample a colormap 8 times
vp = pf.h.volume_rendering(L, W, c, (SIZE, SIZE), tf)
vp.ray_cast()
vr.plot_rgb(vp.image, "my_image")
--
This would plot a 100 AU wide image, centered at the most dense point,
that's 1024x1024. One of the side effects of this change in API is
that this exact operation will now operate in parallel. Britton and
Sam have reported good scaling for the parallelism; I'm testing it out
myself on huge datasets, so hopefully I'll have some benchmarks in the
near future.
Sorry about the breakage, but I think it's worth it. The "yt instinfo
-u" command will attempt to upgrade your current installation, if
you're interested in any of these changes. Let us know if this has
caused any breakages!
Best,
Matt
Hi there--
The covering_grid returns arrays that are in Enzo (thus Fortran)
ordering, correct? So if I do
open(filename,'wb').write( h.covering_grid(0,left,resolution)[ 'Density'] )
I should wind up with a binary file in the same order as the original enzo data?
d.
--
Sent from my Stone Tablet and carried by my Pterodactyl.
Hi Matt,
Just to cover another possible linking issue, do you happen to have libreadline installed in /usr/local on the machine you're building on?
Thanks,
Rick
namor:~ rpwagner$ python
Python 2.6.4 (r264:75706, Feb 1 2010, 13:22:43)
[GCC 4.2.1 (Apple Inc. build 5646) (dot 1)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> import readline
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
ImportError: dlopen(/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/lib-dynload/readline.so, 2): Library not loaded: /usr/local/lib/libreadline.6.0.dylib
Referenced from: /Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/lib-dynload/readline.so
Reason: image not found
>>>
