MantisBT - ParaView
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0012391ParaView(No Category)public2011-07-22 05:152016-08-12 09:58
ReporterOldrich 
Assigned ToKitware Robot 
PrioritynormalSeverityminorReproducibilityhave not tried
StatusclosedResolutionmoved 
PlatformOSOS Version
Product Version3.8.1 
Target VersionFixed in Version 
ProjectTBD
Topic Name
Typeincorrect functionality
Summary0012391: vti files do not enlarge their domain in the time series (file_1.vti, file_2.vti...)
DescriptionI produce a time series of vti files (lbm_0.vti, lbm_30.vti ...) which
change their domain size in time. For example, lbm_0.vti has <Piece
Extent="0 60 0 60 0 61"> and lbm_1020.vti has <Piece Extent="0 86 0
86 0 61">. When I load the series into the Paraview, the domain does
not enlarge and stays at its initial size. When I load lbm_1020.vti
separately, it has the correct domain size. I enclose the two sample
files where you can observe the problem.

Comment by Biddiscombe, John A:
Oldrich

I've seen another report of a similar bug.

What must be happening is that when the UPDATE_TIME is changed inside the pipeline, for whatever reason, RequestInformation is not changing the WholeExtent of the output data and so you are not seeing the imagedata change size.

You should file a bug report and attach your observations and my comment.

If you have a dataset that can be shared which I can have a copy of, please contact me off list and I'll try to look at it.

JB
Steps To Reproduce
Additional Information
TagsNo tags attached.
Relationships
Attached Fileszip vtk.zip (829) 2011-07-22 05:15
https://www.vtk.org/Bug/file/8985/vtk.zip
Issue History
Date ModifiedUsernameFieldChange
2011-07-22 05:15OldrichNew Issue
2011-07-22 05:15OldrichFile Added: vtk.zip
2016-08-12 09:58Kitware RobotNote Added: 0038012
2016-08-12 09:58Kitware RobotStatusbacklog => closed
2016-08-12 09:58Kitware RobotResolutionopen => moved
2016-08-12 09:58Kitware RobotAssigned To => Kitware Robot

Notes
(0038012)
Kitware Robot   
2016-08-12 09:58   
Resolving issue as `moved`.

This issue tracker is no longer used. Further discussion of this issue may take place in the current ParaView Issues page linked in the banner at the top of this page.