ProgressBar: Simple update method where stderr is pipe #2935
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Likely resolves #1980.
Discovered that
mrinfo-ing to a file produced the simplified progress bar, whereas using2>&1 | teeused the dynamic progress bar, producing a whole lot of junk at the head of the file if opened in a text editor.This change means that MRtrix3 C++ commands invoked by a MRtrix3 Python command, where the latter is invoked with
-infoor-debug(and therefore shows dynamic information about executed processes), will now show the simplified progress bar; this is perfectly fine by me. Similarly if the stdout / stderr contents of a failed command are written to text file in the scratch directory, they will also have the simplified appearance, as they ideally should.Not 100% happy with the appearance of the simplified progress bar (see eg. #1744), but not the top priority right now.