Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
![]() |
World Community Grid Forums
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
No member browsing this thread |
Thread Status: Active Total posts in this thread: 92
|
![]() |
Author |
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
2 things you can check:
1. On the Result Status page click the Work unit name to see the quorum detail. If the wingman has already reported in, you can see the jobs in that task by clicking on the Pending Validation link. You'll be able to see how long it took. 2. Click on the properties button in BOINC manager, after selecting this running task. That will tell you how much real CPU time versus elapsed time was used by the task. If the difference is very big, you might want to restart the task [restart BOINC or suspend task with LAIM off so it unloads from memory]. If point 1 above tells the task is difficult, just let it run. It will stop at 12:00 CPU hours anyhow. --//-- |
||
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Dear nittany85,
if the calculation hasn't produced a single checkpoint in 11h, it indicates that the calculation is not converging, i.e., no result can be reached. This happens sometimes in numerical computations, but in this project it should be a rare exception. We are very sorry about the inconvenience - but that's science. Best wishes Your Harvard CEP team |
||
|
|
![]() |