<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif; ">
<div>
<div>
<div>I should probably let someone who knows the implementation better answer this, but I'm going to go ahead and take a crack at it anyway.</div>
<div><br>
</div>
<div>The reason why it works for the writer but not the animation is because they are grabbing the values from different places. The writer (I think) implements the time step iteration within the pipeline module. It grabs the available time steps from the
pipeline information (which your pipeline filter is properly injecting).</div>
<div><br>
</div>
<div>The GUI maintains its own collection of time steps that it has grabbed from the pipeline after certain modules marked as time step producers. The GUI could potentially read the time steps from your python programmable source, but it does not because that
module is not marked as a time step producer.</div>
<div><br>
</div>
<div>ParaView does not automatically read time steps from every module because it is not always possible to identify whether that module is creating time steps you care about. In the past we had problems with assuming that every time a module had time step
information it should be read. It caused the animation settings to change every time a module was added that passed time step information.</div>
<div><br>
</div>
<div>-Ken</div>
<div>
<div><br>
</div>
</div>
</div>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div style="font-family:Calibri; font-size:11pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style="font-weight:bold">From: </span>Aurélien Marsan <<a href="mailto:aur.marsan@gmail.com">aur.marsan@gmail.com</a>><br>
<span style="font-weight:bold">Date: </span>Tue, 13 Dec 2011 11:24:36 +0100<br>
<span style="font-weight:bold">To: </span>Paraview <<a href="mailto:paraview@paraview.org">paraview@paraview.org</a>><br>
<span style="font-weight:bold">Subject: </span>[EXTERNAL] [Paraview] Snap to timesteps with python source<br>
</div>
<div><br>
</div>
<blockquote id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style="BORDER-LEFT: #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0 0 0 5;">
<div>Good morning, </div>
<div> </div>
<div>Something I find weird : </div>
<div> </div>
<div>I generate Data using a python programmable source, and setting the available timesteps for output through the TIME_STEPS pipeline variable.
</div>
<div>I have read in the Paraview wiki that for now, that variable is not correctly handled, and that the SnaptoTimeSteps option should then not beeing working properly. That is right.
</div>
<div>Then I didn't care about what values I put in the TIME_STEPS variable, and set the time values for animating manually.
</div>
<div> </div>
<div><strong><u>But</u></strong> when saving the data in a VTK data format, the pipeline become suddenly aware of the values in TIME_STEPS variables, and only save the time steps defined by this variable....
</div>
<div> </div>
<div>... Then, is there a way to make Paraview Animation aware of the TIME_STEPS generated by the python programmable source, like the vtk writer is ?
</div>
<div> </div>
<div> </div>
<div>Thanks, </div>
<div> </div>
<div>A.Marsan</div>
_______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at
<a href="http://www.kitware.com/opensource/opensource.html">http://www.kitware.com/opensource/opensource.html</a> Please keep messages on-topic and check the ParaView Wiki at:
<a href="http://paraview.org/Wiki/ParaView">http://paraview.org/Wiki/ParaView</a> Follow this link to subscribe/unsubscribe:
<a href="http://www.paraview.org/mailman/listinfo/paraview">http://www.paraview.org/mailman/listinfo/paraview</a>
</blockquote>
</span>
</body>
</html>