Eric,
I had a temporal problem and made a small change to
vtkCompositeDataPipeline which fixed my trouble. It occurred to me (and
I confess that due to other deadlines, I have not followed this thread
carefully, but I will fix the problem after Christmas) - that perhaps
your problem was
Eric
OK I was waiting for some files to copy, so I had a quick edit of
vtkTemporalSnapToTimeStep and vtkTemporalShiftScale. Both these classes
derived from vtkTemporalDataSetAlgorithm, but this was wrong, when we
reimplemented the Temporal stuff, it was possible for these classes to
derive
Hey John,
Unfortunately, this didn't do it either.
When you get around to looking at it more closely, load up the simple
data set I sent at the beginning of the thread (or that Ken posted to
the bug report), put two temporal shift scales branching off of it,
one with zero post-shift and
I added this information to the bug report.
-Ken
On 11/25/08 11:33 AM, Eric E. Monson [EMAIL PROTECTED] wrote:
Hey Ken,
Thanks a lot for looking into this -- I'm sure it was a pleasure to see it pop
up again! :)
Your workaround using the temporal cache filter seems to work as long as I do
Nuts. I guess it wasn't fixed after all. I submitted a new bug report with
your new description.
http://www.paraview.org/Bug/view.php?id=8156
Note that I think I found a workaround using the temporal cache filter.
(Details in the bug report.)
-Ken
On 11/21/08 8:15 AM, Eric E. Monson
Hey,
Sorry for the long email, but I find this problem difficult to
describe succinctly...
In February I was trying to use multiple Temporal Shift Scale filters
as input to a Python Programmable Filter to do on-the-fly point
velocity calculations (for diffusing particles in my simulation
