That's why additional checks to conform with original logic required.
And any changes in that logic require discussion with Eric.
You have our mails - please send your proposals there.

---

News about SETI opt app releases: https://twitter.com/Raistmer

I would like to report inconsistency in original pulse find code that could lead to additional rounding noise between builds:

In snr and threshold calculations (that define signal's score later) used sqrtf() in some places and sqrt((float)) in others.
In my understansing that leads to different rounding of square root results. So can influence borderline cases. Better to chose one function.

For MSVC sqrtf() defined as:

inline float sqrtf(_In_ float _X)
        {return ((float)sqrt((double)_X)); }

So it's essentially double precision one (instead of GPU case where sqrtf takes float and returns float).

---

News about SETI opt app releases: https://twitter.com/Raistmer

I would like to report inconsistency in original pulse find code that could lead to additional rounding noise between builds:

In snr and threshold calculations (that define signal's score later) used sqrtf() in some places and sqrt((float)) in others.
In my understansing that leads to different rounding of square root results. So can influence borderline cases. Better to chose one function.

For MSVC sqrtf() defined as:

inline float sqrtf(_In_ float _X)
        {return ((float)sqrt((double)_X)); }

So it's essentially double precision one (instead of GPU case where sqrtf takes float and returns float).

... and in some places of the code the sqrt/sqrtf can be omitted because the next value is "sqrt(previous*2.0f)" and that can be replaced by a multiplication by a constant sqrt(2) that translates to "previous*1.4142...(float or double)". And yes, I know, that imposes another kind of rounding error but it is significantly faster if it is in an often used code path.

But thanks, I'll look at the code for sqrt/sqrtf.

That's why additional checks to conform with original logic required.
And any changes in that logic require discussion with Eric.
You have our mails - please send your proposals there.

Finding a pulse is a rare event. I can use atomic_max() to GPU main memory from different threads to ensure that a real maximum is found. Another option is to gather all found pulses to a buffer and run a second kernel or a set of last threads to select the 'reportable' and 'best' pulses.

That's why additional checks to conform with original logic required.
And any changes in that logic require discussion with Eric.
You have our mails - please send your proposals there.

Finding a pulse is a rare event. I can use atomic_max() to GPU main memory from different threads to ensure that a real maximum is found. Another option is to gather all found pulses to a buffer and run a second kernel or a set of last threads to select the 'reportable' and 'best' pulses.

yes.
In this particular case atomic reduce would be better option IMHO cause there is no reasonable upper limit for number of signals for reduce (instead of reportable ones where we have hardwired upper limit of 30 pulses for now).

EDIT but check CUDA specification carefully if atomic global memory operations still atomic between different blocks. If I recall correctly it's not the case for OpenCL workgroups (that is, different workgroup execution order unrestricted )

---

News about SETI opt app releases: https://twitter.com/Raistmer

I think we finished with massive testing of 8.19.
Hope Eric will have some time for release after returning from conference.
Next version not ready for beta for now, I'll make announcement when it will be ready.

Great news.
8.19 will go on Seti?

I think we finished with massive testing of 8.19.
Hope Eric will have some time for release after returning from conference.
Next version not ready for beta for now, I'll make announcement when it will be ready.

Great news.
8.19 will go on Seti?

It's only news once Eric okays it ;-)

Last I heard he was out of state (giving a talk at a scientific conference in Mexico)

I think we finished with massive testing of 8.19.
Hope Eric will have some time for release after returning from conference.
Next version not ready for beta for now, I'll make announcement when it will be ready.

Great news.
8.19 will go on Seti?

It's only news once Eric okays it ;-)

Last I heard he was out of state (giving a talk at a scientific conference in Mexico)

Hopefully near a beach with lots of frozen drinks ;)

For any Mac users testing the Mac nVidia Apps, nVidia released a new CUDA Driver yesterday. Everyone with a Fermi and above GPU running Darwin 15.x and above, Especially those running Darwin 16.x, should update to the New Driver,
http://www.nvidia.com/object/macosx-cuda-8.0.46-driver.html
New Release 8.0.46
CUDA driver update to support macOS 10.12 and NVIDIA display driver 367.15.10.05f01
Recommended CUDA version(s): CUDA 8.0
Supported MAC OS X:
10.12.x
10.11.x

Apparently everyone with Darwin 14 and below are excluded from this update. For those with Darwin 13 & 14 running Fermi and above, you should be using this driver, http://www.nvidia.com/object/macosx-cuda-7.5.30-driver.html

I'd like to point out a WU on Main, just in case of something 'interesting':
2283484899
Currently 'Inconclusive' after being sent to a x86-android-linux-gnu (Android/Intel Atom x64), opencl_intel_gpu_sah (Mac x64)and opencl_nvidia_SoG (Windows).

---

I'd like to point out a WU on Main, just in case of something 'interesting':
2283484899
Currently 'Inconclusive' after being sent to a x86-android-linux-gnu (Android/Intel Atom x64), opencl_intel_gpu_sah (Mac x64)and opencl_nvidia_SoG (Windows).

overflow

---

News about SETI opt app releases: https://twitter.com/Raistmer

I'm guessing there is a problem with the server showing recent work units?

The last one show is from yesterday evening. Only ask as I'm trying to see how the new OS, OpenCl and Cuda are reacting to the work units.

I'll check in the morning and hopefully it will update to a more recent report so I can tell if they are validating or not.

I'm guessing there is a problem with the server showing recent work units?

The last one show is from yesterday evening. Only ask as I'm trying to see how the new OS, OpenCl and Cuda are reacting to the work units.

I'll check in the morning and hopefully it will update to a more recent report so I can tell if they are validating or not.

Replica DB server has been offline most of the day, according to the SSP. Never really recovered from the maintenance window Tuesday.

---

If I can help out by testing something, please let me know.
Available hardware and software is listed in my profile here.

Yeah I was wondering if it was something like that..Well guess nothing to do but keep crunching until they are able to repair it.

Thanks

Zalster

Yeah I was wondering if it was something like that..Well guess nothing to do but keep crunching until they are able to repair it.

Yeah, as long as we can u/l and d/l work, it's all good :)

---

If I can help out by testing something, please let me know.
Available hardware and software is listed in my profile here.

Here https://cloud.mail.ru/public/2aUP/dborYAw9G is the iGPU build with maximal possible precision options for kernel code.
Please try if it will improve iGPU precision.

---

News about SETI opt app releases: https://twitter.com/Raistmer

Hi Raistmer

I have just set this host going using your new iGPU app http://setiweb.ssl.berkeley.edu/beta/show_host_detail.php?hostid=78787

I'll leave it running over the weekend - hopefully that should give you some idea as to whether your changes have worked or not. Edit: Well it might if they manage to fix the results pages :)

Fingers crossed :-)

Hi Raistmer

I have just set this host going using your new iGPU app http://setiweb.ssl.berkeley.edu/beta/show_host_detail.php?hostid=78787

I'll leave it running over the weekend - hopefully that should give you some idea as to whether your changes have worked or not. Edit: Well it might if they manage to fix the results pages :)

Fingers crossed :-)

Thanks, I'll look for your host results.

---

News about SETI opt app releases: https://twitter.com/Raistmer

Hi Raistmer

I have just set this host going using your new iGPU app http://setiweb.ssl.berkeley.edu/beta/show_host_detail.php?hostid=78787

I'll leave it running over the weekend - hopefully that should give you some idea as to whether your changes have worked or not. Edit: Well it might if they manage to fix the results pages :)

Fingers crossed :-)

Thanks, I'll look for your host results.

I was going to swap this host back to stock today but, as the results pages are still not updating, I'll leave it running your test app until after this week's outage. Hopefully the results pages will be working again after that and you can confirm whether you have enough information before I swap back :-)

Seems new build is too imprecise on Skylake (INTEL Intel(R) HD Graphics 530 (4859MB) OpenCL: 2.0) too.

---

News about SETI opt app releases: https://twitter.com/Raistmer