MantisBT - ParaView
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0013831ParaView(No Category)public2013-01-29 17:492016-08-12 09:59
ReporterAlan Scott 
Assigned ToKitware Robot 
PrioritynormalSeverityminorReproducibilityhave not tried
StatusclosedResolutionmoved 
PlatformOSOS Version
Product Versiongit-master 
Target VersionFixed in Version 
ProjectSandia
Topic Name
Typeincorrect functionality
Summary0013831: Master bug - Progress Handler is a mess
DescriptionThis is a master bug that I will hang sub bugs off of. Basically, the current Progress Handler is a mess. This bug relates to file vtkPVProgressHandler.cxx, plus imbedded code in all of the filters that calls it. I am seeing the following:
* No parameter checking for bad input variables. (progress should generally be 0.0 to 1.0 within the code)
* No print statements in the Progress Handler that can be turned on that shows that progress actually increments.
* Intermixing progress of a range of 0.0 to 1.0 and 0.0 to 100.0 within the same object/functions. This is undocumented, and very confusing.
* Progress coming into the Progress Handler from filters (expected progress of 0.0-1.0) with a range up to 10's or 100's (1000% to 10000% done).
* Some conditions (such as a status of 0.0, or any number out of the 0-1 range) that is flooding MPI with messages.
* Some filters, such as the CTH reader, that runs absolutely crazy progress. For instance, with the CTH reader, status is 0.0 to 0.2, then backs up and runs 0.04 to 0.38, then 0.64 to 1.0.
* Running multiple server sometimes provides crazy results (see ranges outside of 0.0-1.0 above).

That's probably a good start. I will post additional bug reports with specifics.
Steps To Reproduce
Additional Information
TagsNo tags attached.
Relationships
parent of 0013832closed Kitware Robot ProgressHandler - Cell to Point is broken 
parent of 0013833closed Kitware Robot ProgressHandler - spyPlotReader is broken 
parent of 0013835closed Kitware Robot ProgressHandler -Exodus Reader is broken 
parent of 0013834closed Kitware Robot ProgressHandler needs fixing, error checking, consistency and COMMENTS. 
parent of 0013836closed Kitware Robot ProgressHandler - Most filters - are broken 
parent of 0013839closed Utkarsh Ayachit Progress status locks multiserver 
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2013-01-29 17:49Alan ScottNew Issue
2013-01-29 17:51Alan ScottDescription Updatedbug_revision_view_page.php?rev_id=553#r553
2013-01-29 21:48Alan ScottRelationship addedparent of 0013832
2013-01-29 21:49Alan ScottRelationship addedparent of 0013833
2013-01-29 21:49Alan ScottRelationship addedparent of 0013835
2013-01-29 21:50Alan ScottRelationship addedparent of 0013834
2013-01-29 21:50Alan ScottRelationship addedparent of 0013836
2013-01-30 16:34Alan ScottRelationship addedparent of 0013839
2013-05-01 15:58Nikhil ShettyAssigned To => Nikhil Shetty
2013-05-01 16:12Nikhil ShettyNote Added: 0030671
2013-05-01 16:12Nikhil ShettyStatusbacklog => todo
2013-06-05 16:01Nikhil ShettyAssigned ToNikhil Shetty =>
2015-01-11 08:27Utkarsh AyachitSource_changeset_attached => ParaView master e1f6e4e5
2015-01-11 08:28Utkarsh AyachitSource_changeset_attached => ParaView master 6242d9a0
2016-08-12 09:59Kitware RobotNote Added: 0038322
2016-08-12 09:59Kitware RobotStatustodo => closed
2016-08-12 09:59Kitware RobotResolutionopen => moved
2016-08-12 09:59Kitware RobotAssigned To => Kitware Robot

Notes
(0030671)
Nikhil Shetty   
2013-05-01 16:12   
One of issue may be a general issue for multiblock data sets. The CompositeDataPipeline executes one algorithm for every block. During each run the algorithm reports progress from 0.0 - 1.0 and thus we see multiple progress for a single run.

The GUI takes range from 0.0 to 100 and so there may be some things arising out of this confusion.

Fixes are on their way.
(0038322)
Kitware Robot   
2016-08-12 09:59   
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.