| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Active Research
Forum: Africa Rainfall Project
Thread: Work Available |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 3319
|
|
| Author |
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
entity No-one else has reported a reversion to 36 second time step. Please advise the units concerned. As regards the 7-day deadline. That is what it says on BOINC Manager, but it is actually 8 days for normal units or 4.5 days for priority units. Mike You are right, that is what BOINC Manager says. That is also the date that the client uses to terminate the WU if it hasn't started with a message in the log indicating that the WU was cancelled because the deadline has passed and the work unit hasn't started. This is what I'm seeing when looking at the WU on the website after it has been reported back by the client. I'm not sure where the 8 days and 4.5 days come into play. They may be there somewhere but I haven't witnessed any. After doing a little more research, it looks like if there isn't any communication by the client to the server concerning the work unit (the WU could be still "running") in 8 days. The server marks the WU as a "No Reply". However if the client cancels the WU due to the passed deadline and reports that back to the server, the server sees that as an "Error" and marks the WU as such. Example: ARP1_0014726_118_0 Linux Fedora Fedora 34 (Server Edition) [5.13.5-200.fc34.x86_64|libc 2.33 (GNU libc)] Error 2022-01-07 22:30:37 UTC 2022-01-14 22:37:09 UTC If you look at the stdout for the error, it only shows the version of the core client. [Edit 1 times, last edit by Former Member at Jan 15, 2022 12:24:28 AM] |
||
|
|
Mike.Gibson
Ace Cruncher England Joined: Aug 23, 2007 Post Count: 12436 Status: Offline Project Badges: 
|
Thank you. I missed that.
Kevin still has to backtrack the other stuck units and run them through a few generations before we are clear of 24 second time steps. Until the next time any stick. Mike |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
You're welcome Mike. I missed it too and happened to stumble across it when backtracking through the thread.
|
||
|
|
Mike.Gibson
Ace Cruncher England Joined: Aug 23, 2007 Post Count: 12436 Status: Offline Project Badges:
|
Thank you, Kevin.
60 stuck units have now been freed up so only 70 remain. 7 days have passed since the last full report. In that time, the last of the ultra laggards has moved on 3 generations to generation 073 and their leader has moved on 4 generations to 083. 4 of them have now overtaken the oldest stuck unit. I now have 68 candidates for the 70 units still stuck. Maybe Kevin's figures were rounded. They are generation 079 x 1, 086 x 1, 090 x 11, 091 x 16, 092 x 7, 093 x 8, 094 x 5, 095 x 4, 098 x 1, 099 x 10, 102 x 2 & 105 x 1. The list has stabilised, but may get confused when Kevin releases the rest wheb he has time. There are 62 units listed as extreme. 6 are the ultras, so there are 56 others, which are unstuck units. 3 unstuck units have escaped the extreme category. The last of the accelerated (Priority) generations is 114 and their leader is 118. The current leading generation is 128. Each of those leaders has moved on 1 generation so the definition for extreme laggard is still -15 generations with accelerated remaining at -10 generations. However, the leading unstuck unit is yet to achieve that definition. 56,696 units have been validated in the last 7 days (down to 8,099.4per day). There are now 2,225,616 units to be crunched to finish the project assuming that a full generation 182 is the last. My target for completion is now calculated as 17 October 2022. That is 8 days later than my last summary, assumes everyone works as now until the last day and reflects the decrease in work returned. It is likely that we will see the project finish before the end of 2022 due to the efforts to close up the laggards. My guess would be October 2022 assuming those university computers come back on line after their holiday. However, the step change on the unstuck units will be having an effect as those units are taking longer. Although the first half are now due to revert, we expect the remainder to have the same treatment. Mike |
||
|
|
Mike.Gibson
Ace Cruncher England Joined: Aug 23, 2007 Post Count: 12436 Status: Offline Project Badges:
|
30 hours ago I received one of a pair of resends when there was a No Reply. This made it an active triplet when it was in the 'normal' band of generations.
I would have expected it to have a short deadline but not the extra replication. Mike |
||
|
|
Mike.Gibson
Ace Cruncher England Joined: Aug 23, 2007 Post Count: 12436 Status: Offline Project Badges:
|
119 became an accelerated (priority) generation by 1500 GMT (UTC).
Mike |
||
|
|
Mike.Gibson
Ace Cruncher England Joined: Aug 23, 2007 Post Count: 12436 Status: Offline Project Badges:
|
All groups have moved on 1 generation since Sunday.
Mike |
||
|
|
MJH333
Senior Cruncher England Joined: Apr 3, 2021 Post Count: 268 Status: Offline Project Badges: 
|
Mike,
ARP1_0033480 is now on generation 109. Cheers, Mark |
||
|
|
Mike.Gibson
Ace Cruncher England Joined: Aug 23, 2007 Post Count: 12436 Status: Offline Project Badges:
|
Thank you, Mark.
It was an unstuck unit and has moved on 6 generations in 8 days. Is it on a time step of 24 seconds or 36 seconds? Mike |
||
|
|
MJH333
Senior Cruncher England Joined: Apr 3, 2021 Post Count: 268 Status: Offline Project Badges:
|
Is it on a time step of 24 seconds or 36 seconds? 36 seconds. Cheers, Mark |
||
|
|
|