<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">A couple more things I just noticed:
<br>
<br>
8) Some of the units (pressure & temperature) seem not to be
implemented, or don't show up in the plot axes.
<br>
9) Projection plotting does some strange things if the values are
uniform to near floating-point precision (example:
<a class="moz-txt-link-freetext" href="http://i.imgur.com/kWHQ7dl.png">http://i.imgur.com/kWHQ7dl.png</a>)<br>
<br>
On 27/11/13 18:28, Nathan Goldbaum wrote:<br>
</div>
<blockquote
cite="mid:CAJXewOnKJJpbP_zLpegAKq+=iV=jToTZjQS0=V+6cnSE6O-CJw@mail.gmail.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
Glad you're excited to customize the Ramses frontend! All of the
things you suggest sound like excellent improvements.<span></span>
<div><br>
On Wednesday, November 27, 2013, Sam Geen wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi,<br>
<br>
I intend to try to fiddle with the RAMSES frontend when I have
time/need, and thought it would be good to collate a list of
tasks that need to be completed so we have a consensus on what
needs to be fixed. Feel free to suggest things or tell me that
they're already implemented if I missed them:<br>
<br>
1) Add support for RT and ATON files, which are now part of
the default RAMSES (I assume from the code that the cooling
and grav files are already read)<br>
2) Via 1), it might be nice to refactor the RAMSESDomainFile
class a bit to provide a more generic Ramses file reading
routine/class, since the formats of the files are fairly
similar and in doing 1) we might get some copy-paste bloat.<br>
3) Allow for RAMSES runs that only contain AMR & particles
(i.e. pure N-body runs with no hydro)<br>
4) Refactor the inputs to fit YT default field names (for MHD,
RT and ATON).<br>
5) Allow YT to interpret non-cosmological simulations in
RAMSES, or if it already does, remove the warning that says
this.<br>
6) Romain Teyssier suggested allowing users to specify their
own default field names for user-modified versions of RAMSES.
I don't know if YT caches data that would allow this, but I
thought I'd punt the suggestion along. Another option could be
to allow users to expose the RAMSES namelist files to YT (i.e.
the parameter files for starting up a run) - these contain a
lot more information on the physics included, etc. I'd put
this on a low priority unless someone thinks of something
clever that solves this cleanly.<br>
7) It could be worthwhile to implement read-on-demand if it's
not already - sometimes the users won't query the
ATON/RT/hydro/particle file or certain fluid fields in each
file and so we wouldn't need to read those files in that case.
This could be folded into 2).<br>
<br>
Cheers,<br>
<br>
Sam<br>
_______________________________________________<br>
yt-dev mailing list<br>
<a moz-do-not-send="true">yt-dev@lists.spacepope.org</a><br>
<a moz-do-not-send="true"
href="http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org"
target="_blank">http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org</a><br>
</blockquote>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
yt-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:yt-dev@lists.spacepope.org">yt-dev@lists.spacepope.org</a>
<a class="moz-txt-link-freetext" href="http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org">http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org</a>
</pre>
</blockquote>
<br>
</body>
</html>