Thanks for the suggestion DCL, I'll definitely try to do that from now on.

Just curious. Is there a reason this is considered a Notice that should repeat itself 10s after the initial posting? It's partially on me but when I see a Notice, I get my hopes up just to find I already read it the first three or four times it popped up last week and ten days ago subsequently.

Not really a complaint. Plus I do get to post to the forum which isn't a place I feel too particularly welcomed.

Oops, I didn't realize that was happening. I think I had the export as notice setting configured wrong. Hopefully it won't do that now!

Not really a complaint. Plus I do get to post to the forum which isn't a place I feel too particularly welcomed.

post-away and ignore the people saying untoward things!! Asking questions is the way to get answers to questions we don't know.

Just joined.
old duffer from Wahpeton, ND
across the Red River from Minnesota.
- Chuck
no reply needed

Greetings!
I think it is wonderful to participate in BOINC projects!
Love space science and happy I can contribute.
Got a question;
I have 13 units with status "ready to start", Application "Milkyway@home Separation 1.46", Name "de_modfit_8x_bundle_4s_bgset_7_xxxxxxxxxxxxx".
they all have a deadline of "2021-02-17 17:36:11".
I'm curious about why none of them are running?
Am I missing something?
Cheers,
Edward

---

Greetings!
I think it is wonderful to participate in BOINC projects!
Love space science and happy I can contribute.
Got a question;
I have 13 units with status "ready to start", Application "Milkyway@home Separation 1.46", Name "de_modfit_8x_bundle_4s_bgset_7_xxxxxxxxxxxxx".
they all have a deadline of "2021-02-17 17:36:11".
I'm curious about why none of them are running?
Am I missing something?
Cheers,
Edward

Here at MillkyWay the cpu tasks use all of your cpu cores not just one or two of them so if you are also running another boinc project then the MilkyWay ones will wait until they get in desperation mode and will then block your other projects from running. To limit the number of cores they use you will need an app_config.xml file and that's something you should discuss in the Number Crunching thread.

Thanks for the intel!

Fortunately, this problem was solved before I joined the project,lol

---

Fortunately, this problem was solved before I joined the project,lol

WELCOME!!!

Fortunately, this problem was solved before I joined the project,lol

Welcome, glad to have ye aboard :)

According to my User Total MW@H stats in the BOINC Manager I got a big jump in credits on 10 Feb to 11 Feb. I looked at my work units report and there were no work units reported to my account between 30 January and 1 March. Was there an outage in reporting work unit completion to user accounts?

Not that I am aware of Bill, but I wouldn't be surprised if something like that happened when we flushed out WUs from the system. A lot of them were very old WUs that were stuck, so if you crunched a lot years ago its possible that the credit would have only come through now.

I haven't seen any MW@Home jobs in more than a week. When will the jobs go back out to BOINC?

I haven't seen any MW@Home jobs in more than a week. When will the jobs go back out to BOINC?

Check your settings then as I did gpu tasks less than a week ago and see this when I check the Server Status:

Milkyway@home N-Body Simulation 1000 273796 0.19 (0.01 - 20.58) 3622
Milkyway@home Separation 10092 949449 0.25 (0 - 92.92) 7503

the first number after the name is tasks available, the 2nd number is the number of tasks in progress

Ok, time to turn in my "guy card" and give y'all a laugh at my expense. Like many of you, I participate in more than one project. For me it's this one, Prime Grid, and Einstein. My Nvidia GPUs are running PG and my AMD cards are here. I hit up Einstein when this project went through that rough spot the last couple days. Now this all relates to the thread I promise. I noticed that Einstein seemed to be slow to give me work as well, but there is chatter over there about WUs that allowed me to believe it could be me. Now this project is back to normal and as I said I was getting few WUs while others have said they getting work no prob. So i got to thinking "gee Hold, what would cause all your projects to get limited work?" I strolled over to PG to see if I found any primes being Tour de Prime and all and it hit me. You idiot, you set your WU que to 0 days. So ever hopeful, I set up an alternate venue that allowed several days que and ploped my primary MW cruncher in that venue. Told MW to get work and POW...900 WUs. Sorry if I cause you any worry Tom, looks like all is actually well with the servers, I'm just a scrub. Ok, y'all can stop laughing now lol.

Resource Zero is a great feature. I tried it before where I had more than one RZ project accepting new work but either they both sit there saying after you, no after you... Or one dominates and the other never seems to send any work. It seems to work best to just have a single RZ project.

---

Ok, time to turn in my "guy card" and give y'all a laugh at my expense. Like many of you, I participate in more than one project. For me it's this one, Prime Grid, and Einstein. My Nvidia GPUs are running PG and my AMD cards are here. I hit up Einstein when this project went through that rough spot the last couple days. Now this all relates to the thread I promise. I noticed that Einstein seemed to be slow to give me work as well, but there is chatter over there about WUs that allowed me to believe it could be me. Now this project is back to normal and as I said I was getting few WUs while others have said they getting work no prob. So i got to thinking "gee Hold, what would cause all your projects to get limited work?" I strolled over to PG to see if I found any primes being Tour de Prime and all and it hit me. You idiot, you set your WU que to 0 days. So ever hopeful, I set up an alternate venue that allowed several days que and ploped my primary MW cruncher in that venue. Told MW to get work and POW...900 WUs. Sorry if I cause you any worry Tom, looks like all is actually well with the servers, I'm just a scrub. Ok, y'all can stop laughing now lol.

Resource Zero is a great feature. I tried it before where I had more than one RZ project accepting new work but either they both sit there saying after you, no after you... Or one dominates and the other never seems to send any work. It seems to work best to just have a single RZ project.

Yes that's true because of the new way Boinc pre-fetches work based on the task that's currently running, it doesn't look around at other RZ Projects because it keeps getting work from the one it's crunching. Personally I also dislike it but I understand how it would add complexity to the programming to make it look at all the RZ Projects and ask each for work on a rotating basis when it's close to completing the current task.

First post from a newbie to this project but a pre-BOINC SETI guy.

If I'm in the wrong place, please let me know where I should post..

In recent days I've seen a few tasks that seem to be runaways. Most tasks complete in under an hour and a half. The runaways increase their time to completion. I have aborted three showing three days left to run.

Are these legitimate tasks that will in fact complete or are they just Born To Run - forever? Are there any any remedies out there? I am not inclined to keep checking on them and chucking away days of time on useless work.

The one I am looking at right now is "M-Body Simulation 1.76 (mt) suspended and showing over three days remaining.
I am running Windows 10 (ugh) on Intel Xeon 12 CPU's (6 cores) @ 3.5Ghz with an Nvidia Quadro M4000 GPU

Thanks
Liam

Welcome to the project and forums. Search on n-body tasks stalling and you will find countless posts going back years on the problem. Mostly occurs on Windows and one of the things you can try is to stop and restart BOINC.

The other thing is to write up an app_config.xml file to restrict the n-body tasks to only use 2-4 cpus instead of their default of using all cpus concurrently.

Also if running any virus scanners, don't scan the BOINC folder or sub-folders as they can restrict writing necessary files and checkpoints for BOINC.

---