<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">One possibility would be to define a bounding box that yt uses to upload ramses data only when contained in this bounding box.<div>This can be done efficiently using the Hilbert key.</div><div><br></div><div>Romain</div><div><br><div><div>On 06 Dec 2013, at 15:49, Matthew Turk <<a href="mailto:matthewturk@gmail.com">matthewturk@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div style="font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;">Hi Junhwan,<br><br>There's some more background on this issue here:<br><br><a href="http://lists.spacepope.org/pipermail/yt-users-spacepope.org/2013-November/004265.html">http://lists.spacepope.org/pipermail/yt-users-spacepope.org/2013-November/004265.html</a><br><br>Basically, what it amounts to is:<br><br>* Right now RAMSES uses too much memory and duplicates the full mesh<br>on every processor<br>* This is not how it will always be<br>* Unfortunately changing this can't be prioritized in the next couple weeks<br><br>Your mesh is *particularly* large for what we've dealt with before.<br>As it stands, I would be surprised if it will work. The fix for this<br>would be to change the Octrees to only parse on demand rather than at<br>instantiation of the RAMSESHierarchy. Sam Geen and I have talked a<br>bit about this, and he may be interested in working on it. It's a<br>change that also will happen for N-body datasets (differently) and<br>it's definitely planned to come, but it isn't being prioritized at<br>this very moment because of other pressing concerns.<br><br>On Thu, Dec 5, 2013 at 10:47 PM, Junhwan Choi (최준환)<br><<a href="mailto:choi.junhwan@gmail.com">choi.junhwan@gmail.com</a>> wrote:<br><blockquote type="cite">Hi all,<br><br>I try to make some visualizations (density/temperature project) for<br>large simulation with yt.<br>The simulation is 4096^3 unigrid Ramses simulation.<br><br>I try to implement the basics density and temperature projection plot<br>with following script and I got memory problem and yt run is crashed.<br>=====<br>from yt.mods import *<br><br>ds = load("../output_00048/info_00048.txt", fields =<br>["Density","x-velocity",<br>"y-velocity","z-velocity","Pressure","Metallicity","Rad"])<br>center = [0., 0., 0.]<br><br>pw = ProjectionPlot(ds, "x", ("gas", "Density"),<br>weight_field="Density", center=center)<br>pw.zoom(1.01)<br>pw.save("allviewGas")<br>pw = ProjectionPlot(ds, "y", ("gas", "Density"),<br>weight_field="Density", center=center)<br>pw.zoom(1.01)<br>pw.save("allviewGas")<br>pw = ProjectionPlot(ds, "z", ("gas", "Density") ,<br>weight_field="Density", center=center)<br>pw.zoom(1.01)<br>pw.save("allviewGas")<br><br>pw = ProjectionPlot(ds, "x", "Temperature", weight_field="Density",<br>center=center)<br>pw.zoom(1.01)<br>pw.save("allviewGas")<br>pw = ProjectionPlot(ds, "y", "Temperature", weight_field="Density",<br>center=center)<br>pw.zoom(1.01)<br>pw.save("allviewGas")<br>pw = ProjectionPlot(ds, "z", "Temperature" , weight_field="Density",<br>center=center)<br>pw.zoom(1.01)<br>pw.save("allviewGas")<br>====<br><br>Is there any way to reduce the memory usage when I make visualization?<br>If I use slice instead of projection, can I save the memory?<br>I saw there is parallelization for yt. Does parallelization distribute<br>the data at the beginning of the read?<br>(But, I prefer to do so w/o parallelization at this moment.)<br></blockquote><br>In principle, yes, slices will considerably reduce the memory, modulo<br>the overhead from having all your octrees in memory at once -- which<br>will be considerable.<br><br>I will spend some time thinking if there's a hotfix we can apply to<br>make this work for you right now, as is, but I suspect it may be a<br>little time until it can be properly implemented.<br><br>-Matt<br><br><blockquote type="cite"><br>Thank you in advance,<br>Junhwan<br>_______________________________________________<br>yt-users mailing list<br><a href="mailto:yt-users@lists.spacepope.org">yt-users@lists.spacepope.org</a><br><a href="http://lists.spacepope.org/listinfo.cgi/yt-users-spacepope.org">http://lists.spacepope.org/listinfo.cgi/yt-users-spacepope.org</a><br></blockquote>_______________________________________________<br>yt-users mailing list<br><a href="mailto:yt-users@lists.spacepope.org">yt-users@lists.spacepope.org</a><br><a href="http://lists.spacepope.org/listinfo.cgi/yt-users-spacepope.org">http://lists.spacepope.org/listinfo.cgi/yt-users-spacepope.org</a></div></blockquote></div><br></div></body></html>