Validation inconclusive

still unclear how they determine inconclusives if it's not being compared to anything lol

I assume that's the small number of yours which are still being randomly tested? And that number drops as you get more trustworthy.

Oh, I thought you had a few of those. What are those ones you have watercooled about 4 in one PC you showed a picture of in Einstein?

i don't run that system anymore, but it was 7x RTX 2080. that system has since been dismantled, parted out, and converted to something else. I don't have any multi-GPU setups that are water cooled like that anymore. my other multi-GPU systems are air cooled at the moment.

Odd, I see it as 7.5Tflops DP, pretty much the same as all my old Tahitis together, and I get 1 maybe 1.5 million credits a day.

theoretical specs vs real world outcome. just look at the leaderboard here and you'll see MANY TitanVs in the 2-2.5M range per GPU. and with tuning you can push it more. mine should come close to 3M if i run it long enough.

---

I believe they fit each result returned into a "not unreasonable result" filter. I believe that is defined by the:
<stream_only_likelihood2>
<search_likelihood2>
values returned for each result in the stderr.txt output. If the values are reasonable, then they don't need an extra validation task, if unreasonable the result goes into inconclusive status and warrants a wingman task.

---

theoretical specs vs real world outcome. just look at the leaderboard here and you'll see MANY TitanVs in the 2-2.5M range per GPU. and with tuning you can push it more. mine should come close to 3M if i run it long enough.

I guess those specs (I get from techpowerup) are raw specs, like looking at GHz of a CPU. Your Titan presumably has a better instruction set MW can take advantage of.

I take it you're considerably richer than me :-/ https://youtu.be/qRKbX_ilsVI?t=4

I believe they fit each result returned into a "not unreasonable result" filter. I believe that is defined by the:
<stream_only_likelihood2>
<search_likelihood2>
values returned for each result in the stderr.txt output. If the values are reasonable, then they don't need an extra validation task, if unreasonable the result goes into inconclusive status and warrants a wingman task.

Sounds good, so when I stick a dodgy GPU into my good host, it'll get spotted for the charlatan it is pretty quickly.

I believe they fit each result returned into a "not unreasonable result" filter. I believe that is defined by the:
<stream_only_likelihood2>
<search_likelihood2>
values returned for each result in the stderr.txt output. If the values are reasonable, then they don't need an extra validation task, if unreasonable the result goes into inconclusive status and warrants a wingman task.

Sounds good, so when I stick a dodgy GPU into my good host, it'll get spotted for the charlatan it is pretty quickly.

Yes it should and the whole host will will then be put on 'watch' again requiring wingmen until you get 10 valid tasks in a row

Yes it should and the whole host will will then be put on 'watch' again requiring wingmen until you get 10 valid tasks in a row

I buy broken cards and resurrect. You can get a busted one for a third of the price. Sometimes just a fan is broken, or the fan controller which you can bypass, or some heatsink gunk and pads (I use the super stuff, carbon nanotubes or something) make it work again.

my boinc playlist gpu calculations all videos https://www.youtube.com/watch?v=pYVW9oA9yWk&list=PL_r97NUMjf7x4TgZT3bwQYL8KV_Vbo2J8

---