[yt-users] reading the fields correctly (ramses-rt)

[Nathan Goldbaum]

Hi Salvatore,

I think we'll need to add support for these data formats to yt itself.

Before we moved to github there were some attempts to add support for more
ramses fields in these pull requests:

https://bitbucket.org/yt_analysis/yt/pull-requests/1464
https://bitbucket.org/yt_analysis/yt/pull-requests/2139
https://bitbucket.org/yt_analysis/yt/pull-requests/2499
https://bitbucket.org/yt_analysis/yt/pull-requests/2500

Unfortunately none of those efforts proceeded to the point where we could
merge the code in.

If you'd be interested in working on this, I think it would be a great
initial contribution to yt.

If you're not interested in adding support for this, then we could at least
open an issue to track this feature request:

https://github.com/yt-project/yt/issues/new

It would also be nice if you could include some sample datasets that
someone who is interested in working on this but does not have access to
ramses-rt could use to debug with while working on this feature.

In the end yt's support for data formats is limited by what sorts of data
the developers who have worked on any given part of the codebase have had
access to. Unfortunately given the culture of astronomical simulation
codes, that sometimes means we do not support all possible versions of a
given data format simply because we were not aware of that subset of the
data format when we initially added support.

Hope that helps,

Nathan

On Wed, May 31, 2017 at 2:01 PM, sacielo <sacielo at gmail.com> wrote:

> Hi all,
>
> I'm experiencing a little trouble in reading some RAMSES files which
> include radiative transfer.
> In this (broadly used) implementation some of the fields do not follow the
> order they have classical RAMSES files; e.g. the pressure field is later in
> the fields list. Indeed when I read the files those fields do not have the
> correct content.
>
> Can someone please suggest a possible workaround? For instance a plugin
> for this kind of files, if it exists, or suggest how I could swap the
> fields, or rename them with the correct name?
> I do not want simply to create new fields, without correcting the default
> ones, as all derived fields (and possibly other valuable yt features) would
> not work properly.
>
> Thank you very much!
>
> Best,
>
> Salvatore
>
> _______________________________________________
> yt-users mailing list
> yt-users at lists.spacepope.org
> http://lists.spacepope.org/listinfo.cgi/yt-users-spacepope.org
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.spacepope.org/pipermail/yt-users-spacepope.org/attachments/20170531/8f143504/attachment.htm>