I have five 2021 Separation tasks still showing as well.

386397 2142671412 859903 25 Jan 2021, 8:00:43 UTC 27 Jan 2021, 15:04:53 UTC Completed and validated 3,411.47 3,401.00 0.00 Milkyway@home Separation v1.46
windows_x86_64
386205 2142668940 859903 25 Jan 2021, 8:00:43 UTC 26 Jan 2021, 2:11:46 UTC Completed and validated 3,707.07 3,698.09 0.00 Milkyway@home Separation v1.46
windows_x86_64
328767 2141970947 810438 24 Jan 2021, 11:51:07 UTC 26 Jan 2021, 14:23:12 UTC Completed and validated 246.31 60.86 0.00 Milkyway@home Separation v1.46 (opencl_nvidia_101)
windows_x86_64
328760 2141970676 810438 24 Jan 2021, 11:51:07 UTC 25 Jan 2021, 15:06:39 UTC Completed and validated 246.74 60.33 227.52 Milkyway@home Separation v1.46 (opencl_nvidia_101)
windows_x86_64
328759 2141970662 810438 24 Jan 2021, 11:51:07 UTC 25 Jan 2021, 15:06:39 UTC Completed and validated 253.42 59.11 227.52 Milkyway@home Separation v1.46 (opencl_nvidia_101)
windows_x86_64

---

In October of 1969 I took an oath to support and defend the Constitution of the United States against all enemies, foreign and domestic;
There was no expiration date.

Kevin,

Not really a Server Update issue, but I wasn't sure where to post this...

Could you please put something on the end of the Updated GPU Requirements thread in the Number crunching forum and then lock it?

Every so often someone will post in there about their GPU not being supported, and it might be a way of letting them know the current position re GPUs! :-)

Cheers - Al.

My account is not being updayed. help!!!

My account is not being updayed. help!!!

What is not being updated?

My MILKYway@home project. It has kep thesame unit number for sometime.

My MILKYway@home project. It has kep thesame unit number for sometime.

Do you mean the credits perhaps? This has been discussed in many threads, in this one you will also find the date we expect to get credits again.

---

Hello admins, what about the WUs that have the status "Done, confirmation not clear"? Where is the error in your system? I expect some appreciation for the participants who donate their CPU time and money!

---

Hello admins, what about the WUs that have the status "Done, confirmation not clear"? Where is the error in your system? I expect some appreciation for the participants who donate their CPU time and money!

Read this.

---

Hello Admins,
Postings 76769 through 76786, and beyond, seem to indicate that how the algorithms work is not well understood. Further, possibly how the algorithms are supposed to work isn't well understood either.
--> Is there a place, an author, a maintainer, who can clearly lay out in detail for contributors how the MW-at-Home is supposed to work?
--> It _seems_ that there is a large number of unvalidated results accumulating that suggests to the non-astrophysicist professional contributor a lack of useful progress (LoUP),... yet with an enormous computational expenditure.
In that regard, my interest is not at all about "receiving credit," but rather about getting a "sense of progress" on this project.
ThatGuyInTheServerRm

On February 5, Kevin Roux wrote (message 76876 in thread "Admin Updates"):

Working on
- giving tasks needed for validation priority so credit can be given out faster

Just a word of caution [although I do not have detailed knowledge of BOINC server features and how you plan to use them]:
In a few(?) projects, the BOINC server is configured such that "resends" (additional replica after aborts, invalids etc.) are assigned to hosts which recently returned valid results within a certain turnaround time. I have once witnessed this feature creating a deadlock of work distribution at QuChemPedIA: First there was a wave of troublesome workunits which gave a lot of invalid results. (Their input parameters didn't lead to physically sensible model configs.) That way, eventually all of the active hosts dropped out of the aforementioned category of prioritized hosts. The server got to a point at which it didn't assign any new work any more at all. This deadlock was resolved when the admin figured out the cause and where in the server configuration to remove or relax the host discrimination for replica task assignments.

In other words, now that there are practically no hosts with recent valid results any more, watch out that the server nevertheless will assign _1 tasks to such seemingly untrustworthy hosts. (Though I guess we are still perhaps two weeks or so away from the point when we are through with the current stash of _0 tasks.)

On February 5, Kevin Roux wrote (message 76876 in thread "Admin Updates"):

Working on
- giving tasks needed for validation priority so credit can be given out faster

Just a word of caution [although I do not have detailed knowledge of BOINC server features and how you plan to use them]:
In a few(?) projects, the BOINC server is configured such that "resends" (additional replica after aborts, invalids etc.) are assigned to hosts which recently returned valid results within a certain turnaround time. I have once witnessed this feature creating a deadlock of work distribution at QuChemPedIA: First there was a wave of troublesome workunits which gave a lot of invalid results. (Their input parameters didn't lead to physically sensible model configs.) That way, eventually all of the active hosts dropped out of the aforementioned category of prioritized hosts. The server got to a point at which it didn't assign any new work any more at all. This deadlock was resolved when the admin figured out the cause and where in the server configuration to remove or relax the host discrimination for replica task assignments.

In other words, now that there are practically no hosts with recent valid results any more, watch out that the server nevertheless will assign _1 tasks to such seemingly untrustworthy hosts. (Though I guess we are still perhaps two weeks or so away from the point when we are through with the current stash of _0 tasks.)

That was initially designed at Seti so units that were waiting for a 3rd of 4th valid result would get it back more quickly than waiting thru the queue, IOW it got the tasks off the Server and into storage quicker because they would no longer be waiting for a valid result match. In the end they too turned it off because the ;faster; hosts, they initially tried to pick hosts that were returning tasks within 24 hours, were just pc's and like all pc's they too had the occasional problem and tasks weren't really coming back any sooner.

Kevin, your post https://milkyway.cs.rpi.edu/milkyway/forum_thread.php?id=5069&postid=76876

mentions some users old Separation tasks were cleared.

What was the criteria?

Why haven't all Separation tasks been cleared from the database?

I've still got 2800 Separation tasks hanging on in Valid, Invalid and Error categories.

---

Are completed N-Body tasks ever going to be validated? I now have over 100 completed tasks in my que, validation inconclusive. Should I quit crunching for this project?

---

Are completed N-Body tasks ever going to be validated? I now have over 100 completed tasks in my que, validation inconclusive. Should I quit crunching for this project?

Yes they will be validated and no you shouldn't quit because that means they will take even longer to validate. The problem is the Server made a whole bunch of extra main tasks and when it makes a wingman task it goes at the end of the queue, so we are plowing thru all the main tasks before we start on all the wingman tasks.

BTW I have 702 tasks waiting for a wingman.

Kevin, your post https://milkyway.cs.rpi.edu/milkyway/forum_thread.php?id=5069&postid=76876

mentions some users old Separation tasks were cleared.

What was the criteria?

Why haven't all Separation tasks been cleared from the database?

I've still got 2800 Separation tasks hanging on in Valid, Invalid and Error categories.

Keith,

Those Separation tasks that haven't been cleared have been "orphaned" (i.e. their workunit records no longer exist); there was some discussion about this earlier in this thread, including a possible solution

Cheers - Al.

Yes, I saw your post and the solution is perfect for the task. From the header text for that file.

// delete results without a corresponding workunit.
// (in principle these shouldn't exist)

That matches exactly the issue the database is suffering from.

Why hasn't this been done during one of the backup or maintenance evolutions the project has done since Separation ended?

---

Because no one is leading the project. There is no IT department that deals with the project's server. It is not clear which hardware is used in the project's server. The computers you currently support for the project have much more advanced and high-tech hardware than the servers of this project. And now this project has started to lose its seriousness. Look, they haven't been able to solve a database problem for 2 weeks. Personally, if this problem is not solved within 1 week, I will withdraw my support from the project and turn to the universe@home project.

Because no one is leading the project. There is no IT department that deals with the project's server. It is not clear which hardware is used in the project's server. The computers you currently support for the project have much more advanced and high-tech hardware than the servers of this project. And now this project has started to lose its seriousness. Look, they haven't been able to solve a database problem for 2 weeks. Personally, if this problem is not solved within 1 week, I will withdraw my support from the project and turn to the universe@home project.

Universe's main Scientist died recently and while they have a new one they are taking a break from sending out tasks for up to 3 months while they do things the way the new guy wants them done. But there's always Cosmology, as long as you are already have an account there, and Asteroids.

Because no one is leading the project. There is no IT department that deals with the project's server. It is not clear which hardware is used in the project's server. The computers you currently support for the project have much more advanced and high-tech hardware than the servers of this project. And now this project has started to lose its seriousness. Look, they haven't been able to solve a database problem for 2 weeks. Personally, if this problem is not solved within 1 week, I will withdraw my support from the project and turn to the universe@home project.

I woud also like to point out that having an "IT department" costs money, which most likely the scientists don't have access to.

More than likely the university has said you can the rack space, power and bandwidth to run the project but nothing else, so IT solutions and maintenance have to be sourced from elsewhere including students. If you google "Kevin Roux" you'll find he is studying a master of science at the university and "Tom Donlon" is a graduate research assistant

Universe@Home won't have any work for you, their lead scientist has passed away and there is a work generation pause while the behind the scenes stuff gets sorted out.

Look, they haven't been able to solve a database problem for 2 weeks.

Which problem with database? The inconclusive tasks are not a problem with database and it's not a problem at all, as it will clear out by itself. If it ain't broke, don't fix it, all results will be validated, just later than usual, no crunching wasted, that's the main thing.

---