typo fix:<br><br>When you ask for a time value that does not exactly match one of the
ones a reader can produce, it is up to the reader to (decide what) time to produce
geometry at, but it has to specify what it chose in its outputs time
meta information key. That said, all the ones I have looked at all
round down.<br><br clear="all">David E DeMarle<br>Kitware, Inc.<br>R&D Engineer<br>28 Corporate Drive<br>Clifton Park, NY 12065-8662<br>Phone: 518-371-3971 x109<br>
<br><br><div class="gmail_quote">On Tue, Aug 25, 2009 at 5:13 PM, David E DeMarle <span dir="ltr"><<a href="mailto:dave.demarle@kitware.com">dave.demarle@kitware.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im">of DS1 are also in DS2 and visit them only once.) When at a time value that is not in DS1, such as 0.25, ParaView will load the "closest" time value available. (I don't remember whether ParaView will round down to 0.0 or up to 0.5. Try it and find out.)<br>
<br></div>When you ask for a time value that does not exactly match one of the ones a reader can produce, it is up to the reader to time to produce geometry at, but it has to specify what it chose in its outputs time meta information key. That said, all the ones I have looked at all round down.<br>
</blockquote></div><br>