radmc3d <http://www.ita.uni-heidelberg.de/~dullemond/software/radmc-3d/> is
a Monte Carlo radiative transfer code that can produce spectra and images
for dust continuum and line radiation. I've written some code to save out a
yt dataset into the format it uses for its AMR input files. It needs some
cleaning up and documentation, but if this is something other people are
interested in, I'd be happy to try to add it to yt code base. In principle,
this would let any code with a yt frontend interface with radmc3d without
too much hassle.
A number of people have written to me off list requesting a change, so
this will instead be on Tuesday the 23rd at 1PM Eastern.
I've created an event on Google Plus on the yt page. I've set it to
public, because we don't have everyone in circles yet on there.
Here's the event page:
On Sat, Apr 13, 2013 at 10:08 AM, Matthew Turk <matthewturk(a)gmail.com> wrote:
> Hi all,
> I'd like to call a brief, approximately one hour, strategy meeting on
> Monday, April 22nd at 3PM Eastern. This will cover where yt is at,
> where we can go, and how things are progressing. Some of this will be
> dedicated to progress updates (from me and others) as well as
> soliciting feedback on a number of things. Many other projects --
> notably Cactus -- do these on a fixed schedule, so based on the
> success/failure of this one we can consider having them
> The agenda I would like to cover will include:
> * yt 3.0 status, including near/long term plans for development and
> support for non-grid codes
> * Rundown of all YTEPs accepted and outstanding
> * yt's "presence" on the web
> * 3.0 paper
> I will also be soliciting feedback in roundtable style on:
> * How are we doing?
> * How is the procedure for code contributions working?
> * How is the yt "infrastructure" meeting people's needs? (Mailing
> lists, Bitbucket, etc)
> * Where are energies being spent that could be better spent elsewhere?
> If you have either agenda items or discussion items, please reply to
> this email and suggest them.
> I think having a large presence at this meeting would be very useful,
> so if you are able to make it, please try to do so. It'll be held as
> a google hangout, and I'll send details here when it starts up. If
> there's a pressing need to reschedule, please write in reply to this
> Thanks, and looking forward to seeing you there,
Today in IRC, Chris and I went back and forth on the particle
deposition stuff in advance of the meeting next week. My task right
now is to come up with spatial field chunking for Octs in a consistent
way; of course I'll write this up into the extant YTEP, which will
allow for feedback particularly from ARTIO, ART and RAMSES folks, but
as a quick first pass I was wondering what everyone thought of:
1) Unifying DomainSubsets into a single object with subclasses
2) Making that new base class a subclass, itself, of YTSelectionContainer
This would mean that this new base class would be very similar to the
GridPatch object -- which it already is -- and would implement, most
crucially, the __getitem__ accessor pattern. This would return a
[+-]? Specifically, Doug, Chris, and SamL?
Sidenote: I discovered that we will not have to rewrite spatial fields
that currently work for grids; my understanding of the numpy
broadcasting system was not complete, and I didn't realize that this
script does *exactly what I want it to.
This means that our Oct spatial fields will be (2+NGZ*2, 2+NGZ*2,
2+NGZ*2, NOCT) shaped.
New issue 552: cut_region doesn't work in 3.0
It seems that subselecting on data objects using field cuts hasn't been implemented in 3.0.
from yt.mods import *
pf = load('DD0000/DD0000')
dd = pf.h.all_data()
lt = dd.cut_region("grid['Temperature'] < 1e5")
Traceback (most recent call last):
File "test2.py", line 8, in <module>
File "/home/goldbaum/yt-3.0/yt/data_objects/data_containers.py", line 200, in __getitem__
File "/home/goldbaum/yt-3.0/yt/data_objects/data_containers.py", line 470, in get_data
File "/home/goldbaum/yt-3.0/yt/geometry/grid_geometry_handler.py", line 237, in _identify_base_chunk
gi = dobj.selector.select_grids(self.grid_left_edge,
File "/home/goldbaum/yt-3.0/yt/data_objects/data_containers.py", line 441, in selector
yt.utilities.exceptions.YTDataSelectorNotImplemented: Data selector 'cut_region' not implemented.
I've issued a PR for YTEP-0013, which tries to promote deposited particle
fields to being a first-class field type. This extends the (field_type,
field_name) syntax, adds a new concept of the 'deposit' field_type.
If you're at all interested in how particles are treated in yt, I'd
encourage you to look at the PR and comment!