Score and validation problems
Message boards : Neurona@home: Forum for users in English : Score and validation problems
| Author | Message |
|---|---|
|
I have made some observations regarding the validation and score of workunits. | |
| ID: 50 | Rating: 0 | rate:
| |
|
I have some marked Invalid against other Windows Box's, in fact some are against my own Box's. One Box with give an Invalid then another Box of mine will pickup the same Wu & it will be marked as valid ... Weird | |
| ID: 51 | Rating: 0 | rate:
| |
|
The moral of the story is that everyone should run Gentoo Linux. I was wondering about the invalids. All hosts I'm using are getting them, also. I was hoping it wasn't because of Linux. | |
| ID: 53 | Rating: 0 | rate:
| |
|
I got some comments about this yesterday. At the beginning looked like it happened when the two machines where virtualised, but now I realise that the credits are unfairly high just when two Linux machines match, up to 20 times more per a single WU than the Windows host. | |
| ID: 54 | Rating: 0 | rate:
| |
|
I have checked the data base. There are circa 78200 WU processed, and 6% of them have an average canonical credit of 22.4, while the 94% have an average canonical credit of 0.72. This produces a big unbalance in the results, because this 6% produces more than twice credits than the other 94%. | |
| ID: 55 | Rating: 0 | rate:
| |
Also, now I'm not sure what could I do to fix this in the user's credit and results tables. Users with only Linux machines have chances of having more credits that they should have compared with users only with windows machines. A little mess. Perhaps the best solution is just let the project run with this fix and let the credits adjust as more WU are calculated. As long as the problem is fixed I wouldn't do anything about the excess credit some/all of the Linux Box's were getting. Nobody's gained that much from it & unless you could run a script to correct the Credits it would be to much work on your part to manually go thru all the Linux Box's to correct it so I'd just let it stand ... | |
| ID: 56 | Rating: 0 | rate:
| |
|
Yeah. I also vote that it'd be too much work for you to safely clear up those mis-credited WU's. 8-) | |
| ID: 58 | Rating: 0 | rate:
| |
|
Yeah, I figure my opinion would be obviously biased, so I didn't bother to offer one. I'm just hoping to not drop down below 25k. If I don't lose any credit, I'll continue crawling my way to 50k. I'm just kind of waiting to see what happens before I continue. | |
| ID: 60 | Rating: 0 | rate:
| |
|
Here's a curious wu. | |
| ID: 66 | Rating: 0 | rate:
| |
|
Have to check the result returned for this WU. For some reason the Windows host requested 2.99 credits. The credit system is pretty weird. | |
| ID: 68 | Rating: 0 | rate:
| |
|
are the wu's gonna be longer ? langer=more points? :) | |
| ID: 69 | Rating: 0 | rate:
| |
are the wu's gonna be longer ? langer=more points? :) If a WU is a match with the searched solution, it should require about 100 minutes of calculations, but so far all WU have been found "bad", and are calculated in a few minutes. | |
| ID: 70 | Rating: 0 | rate:
| |
If a WU is a match with the searched solution, it should require about 100 minutes of calculations, but so far all WU have been found "bad", and are calculated in a few minutes. Do you know if such a solution can be found by the current application or do you use this run to find it out? | |
| ID: 71 | Rating: 0 | rate:
| |
If a WU is a match with the searched solution, it should require about 100 minutes of calculations, but so far all WU have been found "bad", and are calculated in a few minutes. The current application is able to recognise "good" solutions, but I don't know where is it placed in the solution space. For this reason we are sweeping different combinations. | |
| ID: 72 | Rating: 0 | rate:
| |
|
Well, I think the problems are almost solved, but not entirely. | |
| ID: 75 | Rating: 0 | rate:
| |
|
I thought there was going to be a Limit of 2 Credits ? | |
| ID: 76 | Rating: 0 | rate:
| |
I thought there was going to be a Limit of 2 Credits ? It is, I have set up this in the validator, but as in many other BOINC aspects, seems that it is not working <sigh> as it should. | |
| ID: 77 | Rating: 0 | rate:
| |
|
No, false alarm, its OK. The value in the column is the claimed credit, but the filter I set yesterday (finally at 3 credits) works: | |
| ID: 79 | Rating: 0 | rate:
| |
Message boards :
Neurona@home: Forum for users in English :
Score and validation problems