Slab (hadsm3) in Linux had problems with estimates of completion under certain BOINC versions. Pre 4.4x, I think it did a good job of figuring out how far along one was in the whole model run. With 4.4x (and above?), it would give you the progress through a phase, so in your case you are 84% of the way through phase 2. This can also give silly estimated times to completion.

As I never ran slab under BOINC 5.x, I don\'t know if this was solved there, but I do know 4.43 behaved as described above.

Slab (hadsm3) in Linux had problems with estimates of completion under certain BOINC versions. Pre 4.4x, I think it did a good job of figuring out how far along one was in the whole model run. With 4.4x (and above?), it would give you the progress through a phase, so in your case you are 84% of the way through phase 2. This can also give silly estimated times to completion.

As I never ran slab under BOINC 5.x, I don\'t know if this was solved there, but I do know 4.43 behaved as described above.

Good call: The percentage figures exactly match progress within the phase.

Historically this also makes sense as in the Classic UI the progress was reported separately for each phase - no doubt that got overlooked in the conversion to BOINC; and equally beyond doubt is that there is no point correcting this bug for these WU any more...

The app is hadsm3 v 4.13, the client is 5.2.7 for Linux

With the bug you describe it makes sense that the error goes with the app (slab) version rather than the client version, as percent complete is reported by the app to the client. Further conversions to estimated time to complete will be different in different client versions, but will all be wrong of course - garbage in, garbage out...

Thanks for your reply, as with many bugs it all makes perfect sense once you know what is happening...