hi
my work of my cpu's dont get confirmations. what can i do?
kind regards

The system is working through all the WUs it needs to validate, and some will need a second copy of the workunit sent out for confirmation. You are doing great. This is a system backlog and not your problem. Keep processing Workunits to help work through the long queue of them that need to be done, and eventually the ones you have done will be validated.

You haven't done anything wrong. The work you have done will be validated in time. The best thing you can do is to continue processing the workunits, since the to be sent queue is a bit too long.

You haven't done anything wrong. The work you have done will be validated in time. The best thing you can do is to continue processing the workunits, since the to be sent queue is a bit too long.

ok, thank you!

Since several weeks the WU's hanging (beeing finished) in my oppinion and also the points for a WU are much reduced compared to the last 2 years. Before i did more Milkyway points (per day) than for Einstein project. now Einstein runs better but: And now i found a project where my cpu's doing the same points for one of that projects during just one month. And this makes me confused. Also: Seems to be operation system related... makes me think stopping projects which just costs e-power when they do not support my OS the same way like other ones.

You haven't done anything wrong. The work you have done will be validated in time. The best thing you can do is to continue processing the workunits, since the to be sent queue is a bit too long.

ok, thank you!

Since several weeks the WU's hanging (beeing finished) in my oppinion and also the points for a WU are much reduced compared to the last 2 years. Before i did more Milkyway points (per day) than for Einstein project. now Einstein runs better but: And now i found a project where my cpu's doing the same points for one of that projects during just one month. And this makes me confused. Also: Seems to be operation system related... makes me think stopping projects which just costs e-power when they do not support my OS the same way like other ones.

For the most part every Project makes it's own decisions about how many credits to give out for a given task, some Projects do use a standard formula but others just come up with a number and go from there. The numbers can be based on a few dozen things like...more credits per task can mean more users coming to the site, does the data have a deadline ie the Covid research several projects did and some still do, etc etc.,

For the most part every Project makes it's own decisions about how many credits to give out for a given task, some Projects do use a standard formula but others just come up with a number and go from there. The numbers can be based on a few dozen things like...more credits per task can mean more users coming to the site, does the data have a deadline ie the Covid research several projects did and some still do, etc etc.,

Ok, thank you

But: Can you tell me the situation with n-Body WUs: There are ~11000 task in my list and ~10300 are not confirmed. These work takes a few days/weeks beeing calculated when running the cpus 24/7. i get a feeling that all cpus which are not permanent connected to the internet dont get confirmation while some other cpus which are requireing/sending direktly tasks getting confirmed immediately. (kind of feeling, not 100% verified). On the other hand: Only Seperation Tasks running all fine and are already validated (currently no new tasks available ).

To get more details read through some of the other forums on this site. But the short of it is that the project is still recovering from a disk crash a few weeks ago. At one point way too many (over 14 million) N-Body tasks were generated. One of the consequences is that validation is very slow. Before things go back to normal they need to be processed and the way things look now it'll take weeks or longer. There's nothing wrong with the tasks themselves and they will eventually get validated. I'd say just keep crunching, the more people we have doing N-Body the faster we can get through that queue.

Separation has its own issues - namely it's hard to get consistent work.

For the most part every Project makes it's own decisions about how many credits to give out for a given task, some Projects do use a standard formula but others just come up with a number and go from there. The numbers can be based on a few dozen things like...more credits per task can mean more users coming to the site, does the data have a deadline ie the Covid research several projects did and some still do, etc etc.,

Ok, thank you

But: Can you tell me the situation with n-Body WUs: There are ~11000 task in my list and ~10300 are not confirmed. These work takes a few days/weeks beeing calculated when running the cpus 24/7. i get a feeling that all cpus which are not permanent connected to the internet dont get confirmation while some other cpus which are requireing/sending direktly tasks getting confirmed immediately. (kind of feeling, not 100% verified). On the other hand: Only Seperation Tasks running all fine and are already validated (currently no new tasks available ).

Look at one of your tasks on the website and it will say how many times it needs to be sent out to be validated, if more than one than then the problem could be that someone said the 2nd task isn't being sent out until after the 1st task is returned, meaning your wingmens units are at the back end of a FIFO quque. Then of course if your 1st wingman doesn't return a valid task then it needs to be sent out again.