Most of the time I can see a significant difference between results for a task when validation is inconclusive. But here is a case where the difference is not apparent to me. Can someone help to understand what the difference is?
http://setiathome.berkeley.edu/workunit.php?wuid=2204607102
Thanks!

---

GitHub: Ricks-Lab
Instagram: ricks_labs

Although the peak count is the same the peaks are either at different frequencies, or have different powers.
All you see in the stderr is a very short summary of the results.

---

Bob Smith
Member of Seti PIPPS (Pluto is a Planet Protest Society)
Somewhere in the (un)known Universe?

Although the peak count is the same the peaks are either at different frequencies, or have different powers.
All you see in the stderr is a very short summary of the results.

So is there another file that gets uploaded in addition to the stderr file?

---

GitHub: Ricks-Lab
Instagram: ricks_labs

Although the peak count is the same the peaks are either at different frequencies, or have different powers.
All you see in the stderr is a very short summary of the results.

So is there another file that gets uploaded in addition to the stderr file?

Yes, it's result file that contains processed data.
OpenCL and AKv8 based CPU builds provide human-readable signals representation just for debugging convenience.

---

SETI apps news
We're not gonna fight them. We're gonna transcend them.

Thanks for the clarification. Still so much to learn here.

---

GitHub: Ricks-Lab
Instagram: ricks_labs

Although the peak count is the same the peaks are either at different frequencies, or have different powers.
All you see in the stderr is a very short summary of the results.

So is there another file that gets uploaded in addition to the stderr file?

Yes, it's result file that contains processed data.
OpenCL and AKv8 based CPU builds provide human-readable signals representation just for debugging convenience.

Thank You Raistmer,

I copied a piece of a code so that Cuda special edition obeys the same convention. For debugging convenience.

Petri R.

---

To overcome Heisenbergs:
"You can't always get what you want / but if you try sometimes you just might find / you get what you need." -- Rolling Stones

I copied a piece of a code so that Cuda special edition obeys the same convention. For debugging convenience.

Petri R.

Oh, very good! At last we will be able to investigate validation issues directly, w/o re-running offline first.
Also, look into -v 2 functionality. It prints best signals as they develops. I found it quite useful too while in validation-check more.

---

SETI apps news
We're not gonna fight them. We're gonna transcend them.

I copied a piece of a code so that Cuda special edition obeys the same convention. For debugging convenience.

Petri R.

Oh, very good! At last we will be able to investigate validation issues directly, w/o re-running offline first.
Also, look into -v 2 functionality. It prints best signals as they develops. I found it quite useful too while in validation-check more.

I'll do that next as soon as I have time.

---

To overcome Heisenbergs:
"You can't always get what you want / but if you try sometimes you just might find / you get what you need." -- Rolling Stones