| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Active Research
Forum: Mapping Cancer Markers Forum
Thread: All of my MCM Work Units revert to 0% completion once they reach anywhere from .09xx% completion to 1.3xx% completion... |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 11
|
|
| Author |
|
|
SKEPTICINFORMED
Cruncher Joined: Jul 12, 2015 Post Count: 31 Status: Offline Project Badges: 
|
Hello!
All of my MCM Work Units revert to 0% completion once they reach anywhere from .09xx% completion to 1.3xx% completion. Is anyone else having this problem, and is WCG/MCM implementing a fix? I've never had this happen before, and I keep having to abort MCM Work Units. |
||
|
|
TPCBF
Master Cruncher USA Joined: Jan 2, 2011 Post Count: 1950 Status: Offline Project Badges: 
|
Hello! Someone mentioned this before, on macOS IIRC, but it doesn't seem that this effects a lot of people.All of my MCM Work Units revert to 0% completion once they reach anywhere from .09xx% completion to 1.3xx% completion. Is anyone else having this problem, and is WCG/MCM implementing a fix? I've never had this happen before, and I keep having to abort MCM Work Units. I just have myself occasionally batches that run to anywhere in the 90s to 100% and then just sit and never finish. This happened since way back when the whole system was still run under IBM and I was told that it wouldn't be worth to look into it, because it apparently effects on a very small number of people. I would suspect that your problem is being handle similar... Ralf  |
||
|
|
SKEPTICINFORMED
Cruncher Joined: Jul 12, 2015 Post Count: 31 Status: Offline Project Badges:
|
Thanks, Ralf! I hope they fix it, because I've been supporting MCM for years and even if it's only affecting a small number of people, it means that MCM is missing out on completing Work Units faster.
|
||
|
|
Ian C
Cruncher Joined: Jul 28, 2022 Post Count: 27 Status: Offline |
I too see this (posted on Boinc agent support) on my Mac.
SCC threw some curve balls that were fixed by making sure Boinc had Full Disk Access, but it made no difference to MCC. Constant looping, and therefore blocking of WUs from other project. So had to turn it off. |
||
|
|
Ian C
Cruncher Joined: Jul 28, 2022 Post Count: 27 Status: Offline |
I tried re-adding MCM a couple o days ago, and the same thing kept happening, so aborted them all again.
But nobody seems to give much of a stuff. |
||
|
|
JunT
Cruncher Joined: Apr 29, 2009 Post Count: 1 Status: Offline Project Badges: 
|
I've been experiencing the same problem on my Mac. I don't remember when the problem started but I have to abort all the MCM tasks in order to accept the tasks from Smash Childhood Cancers prject.
|
||
|
|
Ian C
Cruncher Joined: Jul 28, 2022 Post Count: 27 Status: Offline |
Hi,
Follow a suggestion by alanb1951 (https://www.worldcommunitygrid.org/forums/wcg...ad,45418_offset,10#687817) I did some fiddling, initial putting the CPU usage and time up to 99% and this solved the issue and got the WUs working. Turn it down to 60% and (and even turning up again didn't help the stuck units so I had to abort them) the problem remerged (and even turning up again didn't help the stuck units so I had to abort them). Originally set at 50% for both. Now set at 75% and chugging along happily, although I could probably keep my coffee warm on top of the Mac.. Intel 2018 /8GB RAM Mac mini running Ventura (fully updated - but also dedicated to Boinc, by weather station and Plex serving - not a work machine). Hope this might help those with neverending-loop MCM WUs. |
||
|
|
toulouse1712
Cruncher Joined: Sep 3, 2022 Post Count: 3 Status: Offline Project Badges: 
|
I've been having the same problem on my Mac-mini. Each task gets to around 2 or 3 minutes elapsed time and then goes back to 0. Is anyone looking into this problem, please. Or should I just avoid all 'Mapping Cancer Markers' work units ?
|
||
|
|
Ian C
Cruncher Joined: Jul 28, 2022 Post Count: 27 Status: Offline |
My reply immediately above your post may help.
|
||
|
|
ezrgrid
Cruncher Joined: Sep 21, 2005 Post Count: 4 Status: Offline Project Badges: 
|
The workaround also appears to work for me. And instead of reducing CPU time I have reduced the number of CPUs available to BOINC to 6 (of the 8 cores in my MacBook). That way it does not act as a heating device :-)
|
||
|
|
|