They are "current stock" applications so don't really qualify for inclusion in the Lunatics installer.

Not sure I understand that answer, or perhaps I mis-framed the question.
The current Beta 6 installer installs SoG 8.20. Was wondering when, or if, the installer would be updated to install the SoG 8.22 instead?
Or am I still all wet? (we could use any moisture right now :)

---

I think what was meant was that the Lunatics apps were supposed to be the "cutting edge" development apps or the next evolution for the stock "Main" apps. Since the stock main apps are actually more advanced than what is in the last Lunatics installer, then there really isn't anything new to add. If you want to run the most advanced apps, then just run stock and forget about the Lunatics installer apps. At least for the MB gpu apps. Still something to say about the Lunatics MB cpu apps though.

And of course, if you really want to run the latest and greatest apps, then you need to get on board with the Linux apps developed by TBar and Petri.

---

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

A proud member of the OFA (Old Farts Association)

And of course, if you really want to run the latest and greatest apps, then you need to get on board with the Linux apps developed by TBar and Petri.

At this stage of the game, not sure I have enough brain cells remaining to sign up for the Linux experience. SCO Unix/Xenix schools were a long, long time ago ... :)

---

But based on comments alluded by Stephen and what I remember, our Windows app developer Raistmer said it would be almost impossible to use the exiting CUDA9 Linux app code source for any Windows app simply because the mechanisms the Linux app uses isn't available in the Windows environment.

Ups, hardly I said so :)
What I could say it's no Windows build until sync bug would be resolved (is it?).
CUDA is quite OS-independent AFAIK though I dealt only with older versions.

---

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

I think Raistmer only really knows the OpenCL environment. Anything possible in CUDA for Linux should be possible in CUDA for Windows.

There were attempts to backport OpenCL apps to CUDA from my side (reader could find them scattered in current sources as #ifdef USE_CUDA pragmas) but work wasn't finished.
Currently there is no sense to continue that branch, better to concentrate on Petri's code and maybe port smth to OpenCL instead (there are ATi GPUs still and last Intel's ones become more and more powerful).

---

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

But I don't think Raistmer wants to tackle Petri's code for whatever reason.

Stephen

:)

Ony time. Perti did great job and it worth to be studied of course, no other reasons but lack of time.

---

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

But based on comments alluded by Stephen and what I remember, our Windows app developer Raistmer said it would be almost impossible to use the exiting CUDA9 Linux app code source for any Windows app simply because the mechanisms the Linux app uses isn't available in the Windows environment.

Ups, hardly I said so :)
What I could say it's no Windows build until sync bug would be resolved (is it?).
CUDA is quite OS-independent AFAIK though I dealt only with older versions.

Hi Raistmer,
sync-bug as you call it is still there but with less impact. I scan the pulses with all SM units running. If anything is found that part is done sequentially on one SM to ensure correctness.

I wish I had more time too. If I did I'd implement signal collecting/reordering on GPU.

Petri

---

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

If anything is found that part is done sequentially on one SM to ensure correctness.

Petri

Hi, Petri

Same I use in OpenCL. If this allow to pass test cases collected so far I would say bugfix applied. Of course sequential scan slows things down but it's not a bug as long as valid results are provided.

Regarding signal collecting on GPU - pulses are hard die at least for me :) If I recall right, pulses and triplets are the ones that not "on GPU" in Signals on GPU (SoG) build.
So I wish you have more time too! Would be glad to port CUDA solution to OpenCL if any ;)
Perhaps the key is reordering on GPU too as you say. In SoG I just gather signals and final reordering is done on CPU. And that's not quite appropriate for Pulses. Maybe smth else too but at time I actively worked on SoG Pulses resisted %).

---

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

If anything is found that part is done sequentially on one SM to ensure correctness.

Petri

Hi, Petri

Same I use in OpenCL. If this allow to pass test cases collected so far I would say bugfix applied. Of course sequential scan slows things down but it's not a bug as long as valid results are provided.

Regarding signal collecting on GPU - pulses are hard die at least for me :) If I recall right, pulses and triplets are the ones that not "on GPU" in Signals on GPU (SoG) build.
So I wish you have more time too! Would be glad to port CUDA solution to OpenCL if any ;)
Perhaps the key is reordering on GPU too as you say. In SoG I just gather signals and final reordering is done on CPU. And that's not quite appropriate for Pulses. Maybe smth else too but at time I actively worked on SoG Pulses resisted %).

I still measure time in years. Today is my 50th birthday.
I have a long time to develop and enhance any code and project I find interesting.
Today it is Seti CUDA and the next day it will be ... well the future is Open.

Petri

---

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

If anything is found that part is done sequentially on one SM to ensure correctness.

Petri

Hi, Petri

Same I use in OpenCL. If this allow to pass test cases collected so far I would say bugfix applied. Of course sequential scan slows things down but it's not a bug as long as valid results are provided.

Regarding signal collecting on GPU - pulses are hard die at least for me :) If I recall right, pulses and triplets are the ones that not "on GPU" in Signals on GPU (SoG) build.
So I wish you have more time too! Would be glad to port CUDA solution to OpenCL if any ;)
Perhaps the key is reordering on GPU too as you say. In SoG I just gather signals and final reordering is done on CPU. And that's not quite appropriate for Pulses. Maybe smth else too but at time I actively worked on SoG Pulses resisted %).

And I messed up my software earlier today so if my inconclusives is climbing up, I'll revert back to the old. I'll check that in the morning. Now at 4:10+ am I'm going to sleep.

---

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

Well! Happy Birthday Petri! Just wanted to say how much we crunchers appreciate our volunteer app developers. That goes for Raistmer and TBar too and all the supporting volunteers who test and suggest improvements.

---

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

A proud member of the OFA (Old Farts Association)

Well! Happy Birthday Petri! Just wanted to say how much we crunchers appreciate our volunteer app developers. That goes for Raistmer and TBar too and all the supporting volunteers who test and suggest improvements.

Thank you Keith,
and all other too who feel like congratulating. Let's keep the thread clean.

Thanks.

---

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 hope you had an enjoyable birthday.

---

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

I hate to spoil the party but.... It seems the problem isn't just with the Arecibo Shorties. I'm receiving the same type of overflows with the Non-VLAR BLC tasks with AR around 1.5. That's pretty much what I found with the Shorties, AR of around 1.2 works, 1.6 and above doesn't. Now it's BLC around AR 1.5 and up that also doesn't work,

setiathome v8 enhanced x41p_V0.96, Cuda 9.00 special
Modifications done by petri33, compiled by TBar.

Detected setiathome_enhanced_v8 task. Autocorrelations enabled, size 128k elements.
Work Unit Info:
...............
WU true angle range is :  1.810926
Sigma 0
Thread call stack limit is: 1k
Pulse: peak=inf, time=37.2, period=0.2726, d_freq=8234849452.47, score=nan, chirp=0, fft_len=8 
Pulse: peak=inf, time=37.71, period=0.3205, d_freq=8234849452.47, score=nan, chirp=0, fft_len=8 
Pulse: peak=inf, time=38.22, period=0.2936, d_freq=8234849452.47, score=nan, chirp=0, fft_len=8 
Pulse: peak=inf, time=38.73, period=0.3146, d_freq=8234849452.47, score=nan, chirp=0, fft_len=8 
Pulse: peak=inf, time=39.24, period=0.3314, d_freq=8234849452.47, score=nan, chirp=0, fft_len=8 
Pulse: peak=inf, time=39.75, period=0.3069, d_freq=8234849452.47, score=nan, chirp=0, fft_len=8 
Pulse: peak=inf, time=40.26, period=0.3055, d_freq=8234849452.47, score=nan, chirp=0, fft_len=8 
Pulse: peak=inf, time=40.77, period=0.3114, d_freq=8234849452.47, score=nan, chirp=0, fft_len=8 
Pulse: peak=inf, time=41.28, period=0.2831, d_freq=8234849452.47, score=nan, chirp=0, fft_len=8 
Pulse: peak=inf, time=41.79, period=0.3254, d_freq=8234849452.47, score=nan, chirp=0, fft_len=8 
Pulse: peak=inf, time=42.3, period=0.2929, d_freq=8234849452.47, score=nan, chirp=0, fft_len=8 
Pulse: peak=inf, time=42.81, period=0.2635, d_freq=8234849452.47, score=nan, chirp=0, fft_len=8 
Pulse: peak=inf, time=43.32, period=0.3334, d_freq=8234849452.47, score=nan, chirp=0, fft_len=8 
Pulse: peak=inf, time=43.83, period=0.273, d_freq=8234849452.47, score=nan, chirp=0, fft_len=8 
Pulse: peak=inf, time=44.34, period=0.3258, d_freq=8234849452.47, score=nan, chirp=0, fft_len=8 
Pulse: peak=inf, time=44.85, period=0.2946, d_freq=8234849452.47, score=nan, chirp=0, fft_len=8 
Pulse: peak=inf, time=45.36, period=0.3163, d_freq=8234849452.47, score=nan, chirp=0, fft_len=8 
Pulse: peak=inf, time=45.87, period=0.2267, d_freq=8234849452.47, score=nan, chirp=0, fft_len=8 
Pulse: peak=inf, time=46.37, period=0.3394, d_freq=8234849452.47, score=nan, chirp=0, fft_len=8 
Pulse: peak=inf, time=46.88, period=0.2176, d_freq=8234849452.47, score=nan, chirp=0, fft_len=8 
Pulse: peak=inf, time=47.39, period=0.3111, d_freq=8234849452.47, score=nan, chirp=0, fft_len=8 
Pulse: peak=inf, time=47.9, period=0.2884, d_freq=8234849452.47, score=nan, chirp=0, fft_len=8 
Pulse: peak=inf, time=48.41, period=0.3366, d_freq=8234849452.47, score=nan, chirp=0, fft_len=8 
Pulse: peak=inf, time=48.92, period=0.2786, d_freq=8234849452.47, score=nan, chirp=0, fft_len=8 
Pulse: peak=inf, time=49.43, period=0.2621, d_freq=8234849452.47, score=nan, chirp=0, fft_len=8 
Pulse: peak=inf, time=49.94, period=0.2894, d_freq=8234849452.47, score=nan, chirp=0, fft_len=8 
Pulse: peak=inf, time=50.45, period=0.2849, d_freq=8234849452.47, score=nan, chirp=0, fft_len=8 
Pulse: peak=inf, time=50.96, period=0.2936, d_freq=8234849452.47, score=nan, chirp=0, fft_len=8 
Pulse: peak=inf, time=51.47, period=0.295, d_freq=8234849452.47, score=nan, chirp=0, fft_len=8 
Pulse: peak=inf, time=51.98, period=0.3174, d_freq=8234849452.47, score=nan, chirp=0, fft_len=8 
SETI@Home Informational message -9 result_overflow
NOTE: The number of results detected equals the storage space allocated.

Best spike: peak=7.054444, time=23.57, d_freq=8234849452.47, chirp=0, fft_len=8 
Best autocorr: peak=0, time=-2.124e+11, delay=0, d_freq=0, chirp=0, fft_len=0 
Best gaussian: peak=0, mean=0, ChiSq=0, time=-2.124e+11, d_freq=0,
	score=-12, null_hyp=0, chirp=0, fft_len=0 
Best pulse: peak=0, time=-2.124e+11, period=0, d_freq=0, score=0, chirp=0, fft_len=0 
Best triplet: peak=0, time=-2.124e+11, period=0, d_freq=0, chirp=0, fft_len=0 

Spike count:    0
Autocorr count: 0
Pulse count:    30
Triplet count:  0
Gaussian count: 0

02:33:26 (26016): called boinc_finish(0)

http://setiathome.berkeley.edu/result.php?resultid=6876942983
There are a few others...

I kept getting random False overflows with all the builds, Except this last CUDA 9 App. It was the most stable, until it hit the BLC Shorties.

The current status of the installer is "There is nothing new to install" - and with nothing new on offer, there is no need for a new installer.

Wondering where, if anywhere, the 8.22 vs. 8.20 MB fit into that equation?

. . Having gone through the pain of changing the app from 8.20 to 8.22 on an i5 rig with a GTX950 I feel totally confident there is nothing to be gained from going to 8.22. I am sure it has it's points but for most hardware 8.20 is as good as it gets ...

Stephen

:)

I still measure time in years. Today is my 50th birthday.
I have a long time to develop and enhance any code and project I find interesting.
Today it is Seti CUDA and the next day it will be ... well the future is Open.

Petri

. . Well Happy Birthday you young whippersnapper. In 11 days 65 ... :)

. . Keep up the good work ...

Stephen

:)

I've found something that will both keep Petri clean, and aid him in his thought processes:

---

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

I still measure time in years. Today is my 50th birthday.
I have a long time to develop and enhance any code and project I find interesting.
Today it is Seti CUDA and the next day it will be ... well the future is Open.

Petri

Happy B-day Petri! Welcome to the 2nd half of (hopefully) your century on the planet. So far I find it's been great, other than there seems to be some weird space/time irregularity occurring, because for some reason each year seems to be going by faster and faster, and I can't seem to figure out why, or how to slow it down! Oh well, just try and enjoy every day.

---

Thanks every one.

To the shortening of years I an explanation found have: you compare a year to your lived life. Each year is less and less of the total lived. My year is now 1/50. Next year is a bit less. It is 1/51 etc.

---

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 was always under the impression it was caused by the slowing down of our internal biological clock as we age which affects our perception of time duration. We perceive events and years to pass faster.

---

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

A proud member of the OFA (Old Farts Association)