<div dir="ltr"><div><div>Good morning,<br><br></div>Well the caching was not the issue. The animation I started creating last evening has thus far only written two 3 frames, so I will uncheck the offscreen rendering next and try again. We have been playing with the offscreen rendering before, but I beleive that had to do with stability issues in one of the previous versions.<br>
<br></div>Tom<br><div><div><br></div></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">2013/1/14 Utkarsh Ayachit <span dir="ltr"><<a href="mailto:utkarsh.ayachit@kitware.com" target="_blank">utkarsh.ayachit@kitware.com</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Interesting. I am not sure what it could be. Another option is to try<br>
disabling the use of offscreen rendering for screenshots (by<br>
unchecking "Use Offscreen Rendering for Screenshots" in the "Settings"<br>
dialog on the "Render View" page (at the bottom of that page).<br>
<span class="HOEnZb"><font color="#888888"><br>
Utkarsh<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
On Mon, Jan 14, 2013 at 11:06 AM, Tom Fahner <<a href="mailto:tom.fahner@gmail.com">tom.fahner@gmail.com</a>> wrote:<br>
> Hello Utkarsh,<br>
><br>
> Well in fact I have used both. I had used a python script before, which gave<br>
> a similar behavior, but in that case the unusual large intervals were about<br>
> 15 minutes instead of 8 hours. I also noticed that there was something wrong<br>
> in my setup using the python script, so when I redid the animation I simply<br>
> used the GUI to check the setup more rigorously and decided not to use the<br>
> python script.<br>
><br>
> A bit more info on the python script:<br>
><br>
> With the python script I also assumed it may have been related to the actual<br>
> screen being rendered at the moment that the large intervals showed up. This<br>
> because I used VNC to log into the machine for rendering and the screen was<br>
> locked with ParaView running for most of the time. I just unlocked the<br>
> screen occasionally to have a look at the progress from time to time and I<br>
> could imagine this may have influenced the rendering. Later I also saw a 15<br>
> min. interval between two pngs which were created in the middle of the<br>
> night, meaning the screen was probably still locked, so I assumed that me<br>
> unlocking the screen could not have been the reason. Fifteen minutes between<br>
> two frames can be accepted if this happens once in 100 frames or so, but 8<br>
> hours is just too much.<br>
><br>
> At the moment I started the animation from the GUI again, but with the<br>
> "Cache Geometry" unchecked as you suggested. I will check the results of<br>
> that setting tonight.<br>
><br>
> Regards,<br>
> Tom<br>
><br>
><br>
> 2013/1/14 Utkarsh Ayachit <<a href="mailto:utkarsh.ayachit@kitware.com">utkarsh.ayachit@kitware.com</a>><br>
>><br>
>> Tom,<br>
>><br>
>> I wonder if caching is causing these issues. Are you using the<br>
>> ParaView GUI or a Python script? If the GUI, can you disable caching<br>
>> (uncheck "Cache Geometry" from the "Animation" page in the "Settings"<br>
>> dialog.<br>
>><br>
>> Utkarsh<br>
>><br>
>> On Mon, Jan 14, 2013 at 5:50 AM, Tom Fahner <<a href="mailto:tom.fahner@gmail.com">tom.fahner@gmail.com</a>> wrote:<br>
>> > Dear all,<br>
>> ><br>
>> > For some reason I noticed that ParaView has some large intervals between<br>
>> > writing a PNG for consecutive frames of an animation. Normally there is<br>
>> > about one minute between the timestamp of two PNGs, but sometimes there<br>
>> > is<br>
>> > suddendly a gap of 8 hours:<br>
>> ><br>
>> > 141K Jan 13 15:56 New_Volume_.0118.png<br>
>> > 141K Jan 13 15:58 New_Volume_.0119.png<br>
>> > 139K Jan 13 15:59 New_Volume_.0120.png<br>
>> > 139K Jan 13 16:00 New_Volume_.0121.png<br>
>> > 138K Jan 14 00:34 New_Volume_.0122.png<br>
>> > 139K Jan 14 00:35 New_Volume_.0123.png<br>
>> > 139K Jan 14 00:36 New_Volume_.0124.png<br>
>> ><br>
>> > There are multiple occasions where these large intervals happen but this<br>
>> > does not happen at a regular interval of the animation. There does seem<br>
>> > to<br>
>> > be a relation with the amount of memory that is used, since there is a<br>
>> > sudden decrease in memory used right after "Jan 14 00:34". Below I will<br>
>> > describe my animation and setup. I hope anyone can give an explanation<br>
>> > for<br>
>> > the behavior.<br>
>> ><br>
>> > During the weekend I have created an animation of a mixing tank using<br>
>> > volume<br>
>> > rendering of the concentration of some chemicals in the tank. It is a<br>
>> > reasonably large CFD simulation performed with OpenFOAM. There are about<br>
>> > 15<br>
>> > million cells (tetrahedrals and prismatic layer), but not extremely<br>
>> > large. I<br>
>> > saved the concentration every 0.25 seconds for a 120s simulation. We<br>
>> > have<br>
>> > ParaView 3.98.0 installed on this machine and it was the only program<br>
>> > running at the time. I have made the animation with ffmpeg after<br>
>> > ParaView<br>
>> > made the frames as consecutive pngs. Besides the volume rendering of the<br>
>> > concentration, the walls of the tank where shown with a fixed opacity of<br>
>> > 0.3<br>
>> > and the internal structure (some rotors and baffles) where present as<br>
>> > well.<br>
>> > Although the simulation use the MRF concept, I did mimick the rotation<br>
>> > of<br>
>> > the rotors using the transform filter. Using the "cool to warm" preset<br>
>> > for<br>
>> > visualization I could nicely set the opacity to 0 when the concentration<br>
>> > was<br>
>> > in the allowed range and it showed red in case of too high<br>
>> > concentration, of<br>
>> > blue when too low. The resulting animation is satisfactory, I just<br>
>> > wonder<br>
>> > what can be done to make sure these large intervals between writing<br>
>> > images<br>
>> > do not happen.<br>
>> ><br>
>> > Hope someone can help, if you need more information, please let me know.<br>
>> ><br>
>> > Regards,<br>
>> > Tom<br>
>> ><br>
>> > --<br>
>> > T.C. Fahner<br>
>> > e: <a href="mailto:tom.fahner@gmail.com">tom.fahner@gmail.com</a><br>
>> ><br>
>> ><br>
>> > _______________________________________________<br>
>> > Powered by <a href="http://www.kitware.com" target="_blank">www.kitware.com</a><br>
>> ><br>
>> > Visit other Kitware open-source projects at<br>
>> > <a href="http://www.kitware.com/opensource/opensource.html" target="_blank">http://www.kitware.com/opensource/opensource.html</a><br>
>> ><br>
>> > Please keep messages on-topic and check the ParaView Wiki at:<br>
>> > <a href="http://paraview.org/Wiki/ParaView" target="_blank">http://paraview.org/Wiki/ParaView</a><br>
>> ><br>
>> > Follow this link to subscribe/unsubscribe:<br>
>> > <a href="http://www.paraview.org/mailman/listinfo/paraview" target="_blank">http://www.paraview.org/mailman/listinfo/paraview</a><br>
>> ><br>
><br>
><br>
><br>
><br>
> --<br>
> T.C. Fahner<br>
> e: <a href="mailto:tom.fahner@gmail.com">tom.fahner@gmail.com</a><br>
> t: <a href="tel:%2B31-6-52642814" value="+31652642814">+31-6-52642814</a><br>
> a: van Lodensteynstraat 24<br>
> 2612 SE Delft<br>
> Netherlands<br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>T.C. Fahner<br>e: <a href="mailto:tom.fahner@gmail.com">tom.fahner@gmail.com</a><br>t: +31-6-52642814<br>a: van Lodensteynstraat 24<br> 2612 SE Delft<br> Netherlands
</div>