im still not sure why he got credit for it then. i've seen plenty of WUs invalidate for less.

You're only able to look at the raw signal count from out here. The actual validation is done against the 20KB - 30KB result file which is uploaded at the end of processing - just one of those signals can look like:

<gaussian>
  <peak_power>5.7957577705383</peak_power>
  <mean_power>0.57813739776611</mean_power>
  <time>2458905.5078695</time>
  <ra>6.5102765875108</ra>
  <decl>8.7759971597974</decl>
  <q_pix>0</q_pix>
  <freq>1418912409.544</freq>
  <detection_freq>1418914503.6237</detection_freq>
  <barycentric_freq>0</barycentric_freq>
  <fft_len>16384</fft_len>
  <chirp_rate>42.310804859724</chirp_rate>
  <rfi_checked>0</rfi_checked>
  <rfi_found>0</rfi_found>
  <reserved>0</reserved>
  <sigma>1.5730149745941</sigma>
  <chisqr>1.3424669504166</chisqr>
  <null_chisqr>2.281421661377</null_chisqr>
  <score>0</score>
  <max_power>11.661991119385</max_power>
  <pot length=181 encoding="x-csv">
    16,3,7,4,2,8,21,20,3,8,30,10,6,0,18,6,13,5,2,4,17,38,4,1,54,11,55,7,33,
    255,198,28,76,41,1,25,12,16,13,13,3,2,5,9,20,45,5,17,22,31,22,1,4,23,3,
    4,21,1,26,4,1,10,5,28
  </pot>
</gaussian>

yes, but even looking at the raw signal counts, if one result has wildly different counts than the other, can they really be similar?

i found 3 apples
i found 5 apples

hmm, but 2 of them look kind of the same, good enough!

---

Seti@Home classic workunits: 29,492 CPU time: 134,419 hours

"weakly similar" is really very, very, weak.

my point is less about a canonical result. and that's good that it's not being used.

but it's giving this user the false impression that their system is all good because it's getting "mostly valid" results, but they aren't really. if they invalidated, the user would be faced with the realization that something needs to be rectified.

---

Seti@Home classic workunits: 29,492 CPU time: 134,419 hours

I think this dates back to the very early days of SETI@Home, when the whole concept of 'distributed computing' was weird and nobody knew whether it would take off. The idea was to give users a warm, fuzzy feeling for a 'good try'.

Unfortunately, in this case, it seems to have succeeded only too well...

So there are two issues.
One, why are invalid results being marked as valid?
Two, why is it returning invalid results?
The installed GPU drivers are the most current available and have been on since early February.
I will disable the GPU from receiving work but that doesn't fix the issue which I would think is more wide spread than just my system.

---

Find this 5700 with lot of invalids

8896142

---

I found another 5700 with lots of invalids https://setiathome.berkeley.edu/results.php?hostid=8854997

It's just a shame that BOINC can't work out and display those AMD driver versions used, but I'd say that they're just using the drivers that were supplied at the time of intro and don't have those with the proper OpenCL support.

Cheers.

What is the status on Linux drivers for the RX 5700 XT? Still broken?

I think I understand that the Windows 10 drivers have been fixed?

Tom M

---

A proud member of the OFA (Old Farts Association).

What is the status on Linux drivers for the RX 5700 XT? Still broken?

I think I understand that the Windows 10 drivers have been fixed?

Tom M

If you read further back in this thread, the latest AMD drivers have fixed the issue with the 5700* cards.

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

Yes, for Windows. But a driver change in a windows package doesn’t necessarily get reflected in the Linux package.

I don’t know if there is/was any real confirmation of RX5700+Linux being fixed.

---

Seti@Home classic workunits: 29,492 CPU time: 134,419 hours

I don't know, I don't have the 5700 and I don't run amdgpu-pro. But, I can report that amdgpu drivers v20.10 were just released. It's hard to follow the versioning; release version is different than internal version. I'm assuming the new Linux drivers include the patches that were in the last Windows driver update. In any case, there are new drivers, so it is reasonable to re-evaluate the situation.

---

TY Paul.

---

A proud member of the OFA (Old Farts Association).