Sorry, I'm not thinking about this correctly. My apologies. 

On Sep 26, 2014, at 3:18 PM, John ZuHone <> wrote:

So we're actually *not* getting a 1D dataset then, in the sense that we will be duplicating zones. 

On Sep 26, 2014, at 3:16 PM, Matthew Turk <> wrote:

Hi John,

On Fri, Sep 26, 2014 at 2:14 PM, John ZuHone <> wrote:
Hi Matt,

I'm coming back to this thread...

From the docstring:

   connectivity : array_like
       This should be of size (N,8) where N is the number of zones.
   coordinates : array_like
       This should be of size (M,3) where M is the number of vertices
       indicated in the connectivity matrix.

How would this work for 1D data? Or would it?

My suggestion would be to fake it by setting the right edges to be 2pi
and pi, and feeding in a faux-3D dataset.




On Aug 29, 2014, at 6:40 AM, Matthew Turk <> wrote:

Hi Dan,

The load_hexahedral_mesh option will handle arbitrarily spaced
coordinate systems.  It accepts the cell boundaries and the cell
values (so there must be N+1 boundaries) and the argument
geometry='spherical' will then have it interpret them as spherical
coordinates.  That should work to get log spaced radius zones.


On Fri, Aug 29, 2014 at 12:25 AM, Daniel Whalen <> wrote:

I am trying to use yt to visualize 3D spherical coordinate data sets created
with the ZEUS-MP
code.  I know yt can directly read in such data, but are there any issues
when the grid is ratioed
in the radial coordinate (ie, logarithmically spaced zones in radius).


Dan Whalen

yt-users mailing list

yt-users mailing list

yt-users mailing list
yt-users mailing list