View Issue Details [ Jump to Notes ] [ Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0004432ParaView(No Category)public2007-02-08 15:232007-04-02 16:35
ReporterEric Stanton 
Assigned ToEric Stanton 
PrioritynormalSeveritymajorReproducibilityunable to reproduce
StatusclosedResolutionunable to reproduce 
PlatformOSOS Version
Product Version 
Target VersionFixed in Version 
Summary0004432: Load State: Threshold filter parameters not being restored
DescriptionWhen a state is loaded that includes a threshold filter, the variable being thresholded does not show up in the list of possible ones and the range of values is incorrect.
TagsNo tags attached.
Project
Topic Name
Type
Attached Files

 Relationships

  Notes
(0006679)
Eric Stanton (reporter)
2007-03-07 23:39

 I've added a dependency to bug 0004472 where a reader's properties are not getting restored correctly. Thresholding in a state script does work correctly when thresholding by a variable that does not have to be turned on explicitly in the reader (i.e. global node id).
(0006773)
Berk Geveci (administrator)
2007-03-13 15:28

 Is this fixed now that Exodus state loading bug is fixed?
(0006777)
Eric Stanton (reporter)
2007-03-13 15:39

 Not exactly. When you load state/lookmark with a threshold filter in it, the view initially is correct. But when you click on the threshold filter in the pipeline browser, it seems to revert to some default values for the selected variable array and threshold range. I'll look into it.
(0007024)
Eric Stanton (reporter)
2007-03-30 16:39

 Looks like the bug fairies fixed this for me!

 Issue History
Date Modified Username Field Change
2011-06-16 13:10 Zack Galbreath Category => (No Category)

Copyright © 2000 - 2018 MantisBT Team