| 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: 8
|
|
| Author |
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
First installed BOINC 7.4.53 on the phone last week and sideloaded 7.16.3 few days ago. So far ran 8 OPN1, 7 validated and this one, the second under 7.16.3 to be in Pending Validation. Notably towards the end is the listing of dockings 0 to 5 AFTER dockings 10 through 24 (11 through 25 really).
Result Log Timestamps suggests things ran out of sequence or parts were rerun. Dockings 0-4 happened while in my pocket and out, crunching just on 1 of 2 cores. ![]() |
||
|
|
yoerik
Senior Cruncher Canada Joined: Mar 24, 2020 Post Count: 413 Status: Offline Project Badges:
|
that is bizarre. What's more confusing for me was why it kept restarting for over 6 hours, before resuming work on a dock.
----------------------------------------![]() |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
The event log says many times the battery is at 0 percent when set to not compute below 50%, when the charge is close to 100%.
When setting Ctrl+Find to Docking Number and Ctrl+G through, it's suggested that 0 through 5 were processed twice. That's something amazing, maybe some QA and redo when not the all the t's are not crossed correctly. Maybe a tech could elucidate on these app skills. |
||
|
|
yoerik
Senior Cruncher Canada Joined: Mar 24, 2020 Post Count: 413 Status: Offline Project Badges:
|
this is absolutely not the norm. I've got dozens of different android WUs in, and none of the result logs look anything like this.
----------------------------------------![]() |
||
|
|
BobCat13
Senior Cruncher Joined: Oct 29, 2005 Post Count: 295 Status: Offline Project Badges:
|
Two different jobs in that task.
Start AutoDock for ZINC000890361472_1-ACR3.37_RX1--4mm3_001_tyr264-HO--CYS112_wcgsplit2.dpf(Job #0) Start AutoDock for ZINC000833440239-ACR3.46_RX1--4mm3_001_tyr264-HO--CYS112.dpf(Job #1) |
||
|
|
yoerik
Senior Cruncher Canada Joined: Mar 24, 2020 Post Count: 413 Status: Offline Project Badges:
|
what's odd is that it took so long to move between the two jobs
----------------------------------------![]() |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Two different jobs in that task. Start AutoDock for ZINC000890361472_1-ACR3.37_RX1--4mm3_001_tyr264-HO--CYS112_wcgsplit2.dpf(Job #0) Start AutoDock for ZINC000833440239-ACR3.46_RX1--4mm3_001_tyr264-HO--CYS112.dpf(Job #1) Great catch, so nothing ran out of order, but makes the question even bigger, is this proper? Still in Pending Validation. |
||
|
|
BobCat13
Senior Cruncher Joined: Oct 29, 2005 Post Count: 295 Status: Offline Project Badges:
|
Great catch, so nothing ran out of order, but makes the question even bigger, is this proper? Must be. Here is one task that ran on my Linux machine. Start AutoDock for ZINC000934274455_1-ACR3.28_RX1--4mm3_001_tyr264-HO--CYS112_wcgsplit2.dpf(Job #0) Start AutoDock for ZINC001087464509_1-ACR3.42_RX1--4mm3_001_tyr264-HO--CYS112.dpf(Job #1) Start AutoDock for ZINC000600643497_1-ACR3.39_RX1--4mm3_001_tyr264-HO--CYS112.dpf(Job #2) |
||
|
|
|