| Author | Message |
|
|
|
It seems to me hugly unfair and does chase away alot of crunchers , the fact that triplets although found by both the crunscher who turn in the same result gets accounted for only to the one who turns in the first result. The second gets a slab and the credits and thats it. I was wondering and counting and missing more then 100 triplets in my account until i found out that my bad luck was to be second in turning in the result. Well the way to avoid this from my side is to turn back the results in the waiting list where there is already a result turned in to make sure i turn in mine first. Is this in the intrest of the project? I doupt because this would if lot of people do so lead to a lot of time wasted and a lot of results resendt over and over until one inocent does the crunching the second time.
Can you change your politics on this and give not only the credits but aswell the triplets to both the cruchers who found them?
best regards Nikolaus |
|
|
|
|
|
Thanks, in fact we don't slap anyone :)
It is not a political game I'm playing here, this topic has come
up a few times before, the reasons are the database that is
going to hold all the data, how boinc works with canonical results,
and last but not least the way the website displaying your stats has
been built and now the people that built it are gone. |
|
|
|
|
|
Over at PrimeGrid, both crunchers get the entry in project's internal stats, but only the first cruncher to return can report it to the Top5000-Prime-List (if he/she don't do so within 14 days, the second can do). So I think it is OK that ABC triplets are counted for the first return only. And for those, who are interested in it, this might be a reason not to set a high cache. ;)
____________
Proud member of SETI.Germany
 |
|
|
|
|
Thanks, in fact we don't slap anyone :)
It is not a political game I'm playing here, this topic has come
up a few times before, the reasons are the database that is
going to hold all the data, how boinc works with canonical results,
and last but not least the way the website displaying your stats has
been built and now the people that built it are gone.
Thanks for the explanation but as both crucher get the same credit its just one command line more to make sure that both as well get the same triplets accounted . Sad to here the programmers are gone. ( hopefully you did not shoot them after finishing the programming) Are there others who cold take care to add this programm line? or is it a principle not to do it?
best regards and thanks again for the rapid response
Nikolaus |
|
|
|
|
Over at PrimeGrid, both crunchers get the entry in project's internal stats, but only the first cruncher to return can report it to the Top5000-Prime-List (if he/she don't do so within 14 days, the second can do). So I think it is OK that ABC triplets are counted for the first return only. And for those, who are interested in it, this might be a reason not to set a high cache. ;)
What they do in Prime Grid does not make the unfairness go away. We as well do not argue that shooting people in Iraq for stealing a chicken is a practice already in place in an other country therefore we can do it as well.
Sorry if my example is to drastic , no offence meant not to the Iraqi chicken thiefs or evryone else.
best regards Nikolaus |
|
|
|
|
Thanks, in fact we don't slap anyone :)
It is not a political game I'm playing here, this topic has come
up a few times before, the reasons are the database that is
going to hold all the data, how boinc works with canonical results,
and last but not least the way the website displaying your stats has
been built and now the people that built it are gone.
Thanks for the explanation but as both crucher get the same credit its just one command line more to make sure that both as well get the same triplets accounted . Sad to here the programmers are gone. ( hopefully you did not shoot them after finishing the programming) Are there others who cold take care to add this programm line? or is it a principle not to do it?
best regards and thanks again for the rapid response
Nikolaus
They were webprogrammers, unfortunately I can't state my opinion here as a representant of abc@home about webdevs and shooting.
It's not just one commandline in the code, I can
add things in the assimilator with the result vector, so that can be done,
but the database would become a problem.
Then the stats on the webpage, one day, *some day*, I would like
abc stats on abcathome.com by just logging in, not that you've to go through rekenmeemetabc, then that could be changed.
To sum it up, if someone is going to change the webstats, and the database
can 'hold' it, yes it's possible.
I understand your viewpoint and it's right,
what we have now is a compromise, but changing it involves quite some work
and extra load we don't like from the project side. |
|
|
|
|
Thanks, in fact we don't slap anyone :)
It is not a political game I'm playing here, this topic has come
up a few times before, the reasons are the database that is
going to hold all the data, how boinc works with canonical results,
and last but not least the way the website displaying your stats has
been built and now the people that built it are gone.
Thanks for the explanation but as both crucher get the same credit its just one command line more to make sure that both as well get the same triplets accounted . Sad to here the programmers are gone. ( hopefully you did not shoot them after finishing the programming) Are there others who cold take care to add this programm line? or is it a principle not to do it?
best regards and thanks again for the rapid response
Nikolaus
They were webprogrammers, unfortunately I can't state my opinion here as a representant of abc@home about webdevs and shooting.
It's not just one commandline in the code, I can
add things in the assimilator with the result vector, so that can be done,
but the database would become a problem.
Then the stats on the webpage, one day, *some day*, I would like
abc stats on abcathome.com by just logging in, not that you've to go through rekenmeemetabc, then that could be changed.
To sum it up, if someone is going to change the webstats, and the database
can 'hold' it, yes it's possible.
I understand your viewpoint and it's right,
what we have now is a compromise, but changing it involves quite some work
and extra load we don't like from the project side.
Thanks so far ,I see willingness and understanding of the issue. i dont give up the hope things will change.
Best regards Nikolaus
|
|
|