Sorry to chime in so late. ART in yt-2.x still works -- and in fact, it's
the only way you can do offaxis projections, volume renders, and Sunrise
exports for ART. I'm guessing the first two will be a long time before they
work in yt-3.0, and the latter will require somewhat less effort. Anyway,
while I don't want to maintain ART in 2.x any more, we should could leave
it in a functional state. Maybe post a warning, but keep the code?
On Thu, Jul 18, 2013 at 11:36 AM, Aaron Smith <asmith(a)astro.as.utexas.edu>wrote:
This would be good because if new people use yt 2.x with RAMSES data
they should know the 3.0 implementation is much better.
On 7/18/13 1:27 PM, Matthew Turk wrote:
> Hi all,
> I'd like to propose we actually remove the RAMSES and ART (NMSU)
> frontends from yt 2.x, since they probably don't work, and certainly
> not to the level of support they have in 3.0. In fact, I'd go so far
> as to say that NMSU ART and RAMSES are production quality in 3.0,
> unlike in 2.x where they don't quite work properly.
> I think we need confirmation from Chris Moody before this can be done,
> but does anyone have an objection to this? I will simply replace them
> with stubs that say, please use yt 3.0.
> yt-dev mailing list
yt-dev mailing list