Workunit 452113339
name 	de_modfit_84_bundle5_3s_south_pt2_2_1651669798_11233861
application 	Milkyway@home Separation
created 	15 May 2022, 9:34:34 UTC
minimum quorum 	1
initial replication 	1
max # of error/total/success tasks 	2, 9, 6
validation 	Pending
Task
click for details	Computer	Sent	Time reported
or deadline
explain	Status	Run time
(sec)	CPU time
(sec)	Credit	Application
271031951 	928280 	15 May 2022, 9:43:24 UTC 	15 May 2022, 23:26:13 UTC 	Completed, waiting for validation 	2,773.68 	2,758.37 	pending 	Milkyway@home Separation v1.46
x86_64-pc-linux-gnu

What validation do rhey want when
minimum quorum 1
initial replication 1
max # of error/total/success tasks 2, 9, 6
validation Pending

---

What validation do rhey want when
minimum quorum 1
initial replication 1
max # of error/total/success tasks 2, 9, 6
validation Pending

An answer to that has several parts :-)

Validation Pending simply means that your result hasn't yet been examined by the validator. Normally, that's a fairly swift process, but at the moment the Separation validator seems to get a bit behind (probably because of the extra load on the server caused by wrangling queries on a database with too many live work units!)

At 15 May 2022, 23:42:26 UTC the Server Status page reported 122114 work units waiting for validation. So there would be lots of work units in the Validation Pending category for a lot of users.

Now, the "Quorum 1, initial replication 1" is just the way a project using adaptive replication should launch new work units; when the initial task is returned and the validator has looked at it, if the result is not obviously invalid and if the system that returned it has a good run of consecutive validated returns there's a significant likelihood that it will validate without needing a second opinion - there's a random factor involved, and it'll allow most tasks to self-validate. If the system doesn't have a run of validated results, or if the random factor decrees that a second opinion is needed, the validator will request a second task (and the quorum and/or replication counts will increment.)

The Separation project is definitely using adaptive replication; N-Body jobs set up as if for adaptive replication but don't seem to follow through (which is part of the reason that clearing the N-Body backlog is taking so long - every initial successful result is marked for a second opinion!...)

Hope this helps...

Cheers - Al.

What validation do rhey want when
minimum quorum 1
initial replication 1
max # of error/total/success tasks 2, 9, 6
validation Pending

Okay alanb1951 covered the first part so i will try and tackle the last part the "max # of error/total/success tasks 2, 9, 6" That simply means that each task is sent out 2 times, but alanb1951 already covered the current situation with that. The total is the max number of times it can be sent out before the Server crunches the task to see what's wrong with it and why it wasn't validated by other pc's, it's possible the task itself is just junk. The "success tasks" listing is unknown to me.

Each task we get for our pc's is a very small part of the whole, think of it as a part of a VERY long formula written on a chalkboard, okay I'm old and that's the way we did it, and you and I get just one part of that formula to crunch and return. Then the project puts them all back together and voila they have a picture of the Milky Way in the case of this Project.

Now, the "Quorum 1, initial replication 1" is just the way a project using adaptive replication should launch new work units; when the initial task is returned and the validator has looked at it, if the result is not obviously invalid and if the system that returned it has a good run of consecutive validated returns there's a significant likelihood that it will validate without needing a second opinion - there's a random factor involved, and it'll allow most tasks to self-validate. If the system doesn't have a run of validated results, or if the random factor decrees that a second opinion is needed, the validator will request a second task (and the quorum and/or replication counts will increment.)
...
Hope this helps...

That is probably the reason then. I am a new user of Milkyway and while all my results seem to me to be correct, perhaps a day or two of results are not enough to go through self-validation even though they say a quorum of one is the requirement.

I notice I now have no work units in this category.

---

Now, the "Quorum 1, initial replication 1" is just the way a project using adaptive replication should launch new work units; when the initial task is returned and the validator has looked at it, if the result is not obviously invalid and if the system that returned it has a good run of consecutive validated returns there's a significant likelihood that it will validate without needing a second opinion - there's a random factor involved, and it'll allow most tasks to self-validate. If the system doesn't have a run of validated results, or if the random factor decrees that a second opinion is needed, the validator will request a second task (and the quorum and/or replication counts will increment.)
...
Hope this helps...

That is probably the reason then. I am a new user of Milkyway and while all my results seem to me to be correct, perhaps a day or two of results are not enough to go through self-validation even though they say a quorum of one is the requirement.

I notice I now have no work units in this category.

You are very lucky some people have thousands and I for instance have Validation inconclusive (809) which is 1 less than yesterday