When submitting a realflow job, with a single frame range (eg. 0-300), is it correct that the progress is only seen in the task overview but not in the jobs overview via deadline monitor?
As there is only 1 task, I had expected that the job progress would increase simultaneously with the single tasks that that job has.
Which would be preferred when running multiple realflow sims on different machines.
As now there is no overview of the progress, as it’s only visible per job.
of course it’s already great to have some realflow progress indication in this beta version
thanks for the response, didn’t realize the situation also exists for other plugins (usually don’t do single frames).
read that it would be something for the 7.0 release…
any chance it can be implemented early for only the realflow plugin for example?
As with realflow it’s applicable for 99% for the jobs (if not 100%)
even if it were a simple ‘hack’ to be able to clone the most recent tasks progress bar next to the job progress bar would already do it
(sounds simple in my head… pretty sure it’s a nightmare for you to implement… but figured to give it a shot)
and if you want to top it off for the realflow plugin it would be perfect if we can see a finished frame number.
Then if, for whatever reason, the job is interrupted it’s easier to resume without the need of opening realflow to see what % is which frame.
It’s not plugin-specific, so we can’t just implement it for realflow.
Currently, we build up the job’s progress based on completed task counts. That’s why you only see 0% or 100% for single task jobs. We currently do not store the progress of individual tasks within the job object, so we need to have a special case were if a job has a single task, when the slave updates the progress % for it, it would also update a special field in the job object with that progress %.
So because we need to modify core code for this to work, we wanted to wait for the next major release.
I has a short look at the python and did manage to get the finished frame number to display instead of the %.
But also noticed that this hack only works until frame 100… guess it’s cut off above that as it’s made to show up to 100% only
