We have a lot of Progress Bars that on most jobs run for less than a second.
These really do not make sense any more.
as the user can not follow the progress at that speed.
Also with the removal of the PacmanExecutor the order of algorithms is fixed.
So if there is a hang it is easy enough to look at previous algorithm "took" time line to see what happened before
and then look at asb to see what happens next.
To make matter worse (for the ProgressBar fans anyway) the big talk to the machine algorithms are run in Java so the python Progress bar is not very useful anyway.
Step 1 lets look at a Giant run to see which Algorithm took long enough to make a ProgressBar interesting.
Step 2 See if any of those are python based so ProgressBar makes sense.
Options are then.
Keep Some Porgressbars
Remove all ProgressBars but add a Start log message to Java Tasks
We have a lot of Progress Bars that on most jobs run for less than a second.
These really do not make sense any more. as the user can not follow the progress at that speed.
Also with the removal of the PacmanExecutor the order of algorithms is fixed. So if there is a hang it is easy enough to look at previous algorithm "took" time line to see what happened before and then look at asb to see what happens next.
To make matter worse (for the ProgressBar fans anyway) the big talk to the machine algorithms are run in Java so the python Progress bar is not very useful anyway.
Step 1 lets look at a Giant run to see which Algorithm took long enough to make a ProgressBar interesting. Step 2 See if any of those are python based so ProgressBar makes sense.
Options are then.