There is a misconception with the progress indicators in (probably) all KNIP nodes: e.g. when you have 5 images that each take a while to process, the percentage indicator shows the following stages:
bouncing cube -- 0% -- 20% -- 40% -- 60% -- Done.
I would expect the following states instead (and this is how the core KNIME nodes do work in my experience):
There is a misconception with the progress indicators in (probably) all KNIP nodes: e.g. when you have 5 images that each take a while to process, the percentage indicator shows the following stages:
I would expect the following states instead (and this is how the core KNIME nodes do work in my experience):
The issue is that
setProgressis called in most places after processing the current row, but before increasing the row counter variable.See: https://github.com/knime-ip/knip/search?utf8=%E2%9C%93&q=setProgress&type=