My system is crunching wah2_eas25_a4e1_202012_24_1004_012253799_1. It said, yesterday evening, that it had 2d 01:02:16 left to run, that time was reducing normally. I expected to see it with 1d ... etc. remaining. This morning, it is showing 2d 07:18:12, ie. longer than yesterday evening. Is that normal expected behaviour. Deadline is over a month away, so not an urgent issue.

---

Wave upon wave of demented avengers march cheerfully out of obscurity into the dream.

I don't know about the specific set (eas25 1004) but the average run time for wah2 models according to server status page is 2.11 weeks.

---

The batch was closed on the 5th February due to problems with the ancillary files so you can just abort it. Credit for trickles sent has been granted. If you look at the task page it says, "didn't need." You can safely abort any tasks from 1004 and use your machine for something useful or if you don't run other projects, save electricity.

I've aborted the unit. Most annoying, it had accumulated 16 days plus change, that is a lot of time other projects could have used. I remember some while ago I was similarly annoyed by the project, useless credit is not compensation for wasted CPU time that some of the other projects could have used. I am dropping the project again, it is not "running" right.

---

Wave upon wave of demented avengers march cheerfully out of obscurity into the dream.

I think in future the plan is to send the abort signal from the project to abort tasks in that situation though not 100% sure. I am pretty sure there was a post about it in the number crunching section but a lot of people don't check the forums regularly to spot these things. (I only go to the forums of other projects when there is a problem and I would guess a lot of people are like that with CPDN.