Dear All,

I noticed that I every 3 to 4 days the rosetta queue doubles in size.
This is probebly due to people that send in there results to late.

I get tasks that have allready been finished by someone else.

example

https://boinc.bakerlab.org/rosetta/workunit.php?wuid=1042741034

Send 24 Apr 2020, 3:50:59 UTC should be returned 27 Apr 2020 3:50:59. Yet it is not and I got the task at 27 Apr 2020, 3:52:32 UTC.
At 27 Apr 2020, 11:11:46 UTC the result is returned and I am still crunching the numbers.

Would it be posible to put the 'not returned in time' tasks at the back on the queue. This way everyone processes new tasks and eventualy we will get to the tasks that have expired and give other people more time to send in there results.

This way we do not do double work.

Other example
https://boinc.bakerlab.org/rosetta/workunit.php?wuid=1043012150

Dear All,

I noticed that I every 3 to 4 days the rosetta queue doubles in size.
This is probebly due to people that send in there results to late.

I get tasks that have allready been finished by someone else.

example

https://boinc.bakerlab.org/rosetta/workunit.php?wuid=1042741034

Send 24 Apr 2020, 3:50:59 UTC should be returned 27 Apr 2020 3:50:59. Yet it is not and I got the task at 27 Apr 2020, 3:52:32 UTC.
At 27 Apr 2020, 11:11:46 UTC the result is returned and I am still crunching the numbers.

Would it be posible to put the 'not returned in time' tasks at the back on the queue. This way everyone processes new tasks and eventualy we will get to the tasks that have expired and give other people more time to send in there results.

This way we do not do double work.

Other example
https://boinc.bakerlab.org/rosetta/workunit.php?wuid=1043012150

Hmmm, problem with that is research. If the results were required by the 27th and on the 27th you put the WU to the back of the queue then you might as well scrap it as any results eventually returned will be far too late to be of use.