Mailman 3 July 2013 - yt-dev

Issue #599: Structured but irregular mesh (yt_analysis/yt)
by Matthew Turk July 2, 2013

July 2, 2013

New issue 599: Structured but irregular mesh https://bitbucket.org/yt_analysis/yt/issue/599/structured-but-irregular-mesh Matthew Turk: We should be able to specify varying fwidths along an axis for a rectilinear grid. This will enable better handling of data like MOAB and weather simulations. cc: @scopatz Responsible: MatthewTurk

1 0

Announcing: yt 2.5.4
by Matthew Turk July 2, 2013

July 2, 2013

Hi all, We're proud to release yt version 2.5.4. This is a scheduled point release that includes all bug fixes identified and fixed since the release of 2.5.3 on June 3. Additions, changes and bug fixes include: * Considerably (10x+) faster kD-tree building for volume rendering * System build fix for POSIX systems * Fixing domain offsets for halo centers-of-mass * Removing some Enzo-specific terminology in the Halo Mass Function * Addition of coordinate vectors on volume render *… [View More]

1 0

Oct-diet pull request
by Matthew Turk July 1, 2013

July 1, 2013

Hi all, I've just issued a big pull request that puts octrees (particle and Eulerian) on a major diet. Comments, suggestions and test cases that fail or pass would be welcomed! https://bitbucket.org/yt_analysis/yt-3.0/pull-request/54/octree-diet/diff I've laid out how things are now done, and I'd also be grateful to hear about whether those ideas should be changed/improved/etc. -Matt

1 1

PR for 3.0 that affects particle_mass in Enzo
by Matthew Turk July 1, 2013

July 1, 2013

Hi all, Just a quick note that this PR affects how particle_mass is read in in Enzo in yt-3.0. If you object to this change, please leave a comment. https://bitbucket.org/yt_analysis/yt-3.0/pull-request/55/reduce-overall-mem… -Matt

1 0

Issue #598: Particle fields should be created inside closures (yt_analysis/yt)
by Matthew Turk July 1, 2013

July 1, 2013

New issue 598: Particle fields should be created inside closures https://bitbucket.org/yt_analysis/yt/issue/598/particle-fields-should-be-cr… Matthew Turk: Each particle field should be created inside a closure; none should exist in the primary namespace. This means that while accessing something like "ParticleMassMsun" will still be possible, it will map internally to always having "all","ParticleMassMsun". In doing so we'll ensure that at all times in the generation of the fields … [View More]

1 0