Meow for the Lunatics!

+1

---

Meow for the Lunatics!

+1

Amen to that, brother....

And another meow-out for them.
A sometimes underapreciated bunch of dedicated souls.

---

"Freedom is just Chaos, with better lighting." Alan Dean Foster

Interesting question is, will there be GPU GB work, as most GB stuff seems to be VLAR? Since VLAR work is currently turned off for GPUs on production (I have seen a good bit of GPU VLAR on SETI Beta) will that follow suit on GB? If so, will there be enough capacity to crunch the new volume of CPU-only work?

Rather than speculating, keep an eye on what Eric says in the News area.

http://setiathome.berkeley.edu/forum_thread.php?id=79411&postid=1778449#1778449

Interesting question is, will there be GPU GB work, as most GB stuff seems to be VLAR? Since VLAR work is currently turned off for GPUs on production (I have seen a good bit of GPU VLAR on SETI Beta) will that follow suit on GB? If so, will there be enough capacity to crunch the new volume of CPU-only work?

Rather than speculating, keep an eye on what Eric says in the News area.

http://setiathome.berkeley.edu/forum_thread.php?id=79411&postid=1778449#1778449

Too many threads about the same subjects. Thanks :)

---

My first completed guppi - task 4854464991 - was deep in VLAR territory at AR=0.008804, but completed in roughly 75% (by time and flopcounter) of what an Arecibo VLAR needs.

I have run 9 though, I'm seeing about 1:17 compared to 2:20 for MB VLAR

55 minutes for the CPU so far..

Question about GB-VLARs: is it possible (has any testing been done?) that these new VLARs will behave differently when crunched on NVIDIA cards?

Is it possible they won't take so long as the Arecibo ones do?


Given that the data is said to be all VLAR (I think), it would be nice to know, so that the servers could be made to send them to GPUs...

---

Question about GB-VLARs: is it possible (has any testing been done?) that these new VLARs will behave differently when crunched on NVIDIA cards?

Is it possible they won't take so long as the Arecibo ones do?


Given that the data is said to be all VLAR (I think), it would be nice to know, so that the servers could be made to send them to GPUs...

If processed with OpenCL app yes.
But no mechanism to distinguish OpenCL app from cuda so far.

---

With each crime and every kindness we birth our future.

Question about GB-VLARs: is it possible (has any testing been done?) that these new VLARs will behave differently when crunched on NVIDIA cards?

Is it possible they won't take so long as the Arecibo ones do?

Given that the data is said to be all VLAR (I think), it would be nice to know, so that the servers could be made to send them to GPUs...

If processed with OpenCL app yes.
But no mechanism to distinguish OpenCL app from cuda so far.

Talking of NVidia OpenCL apps, has anybody had any problems with the latest drivers, perhaps especially 364.72 for Windows 10?

I've had an email from Jacob Klein, drawing my attention to this POEM project message board thread: Do not use Nvidia driver 364.47. I'm about to try and reproduce his NVidia SDK sample failures, but with the Windows 7 version of the drivers - if I have time, I'll run a SoG bench as well.

Talking of NVidia OpenCL apps, has anybody had any problems with the latest drivers, perhaps especially 364.72 for Windows 10?

I've had an email from Jacob Klein, drawing my attention to this POEM project message board thread: Do not use Nvidia driver 364.47. I'm about to try and reproduce his NVidia SDK sample failures, but with the Windows 7 version of the drivers - if I have time, I'll run a SoG bench as well.

I am running 364.72 on one of my computers. I have noticed nothing out of the ordinary so far. (I installed that driver last night as that computer updated (fast track) and I had to reinstall NVIDIA drivers, so I did the latest ones). Hoping all continues to work well.

---

SETI@home classic workunits 4,019
SETI@home classic CPU time 34,348 hours

Now we just need an update to the user task list page that shows the GBT work.
Meow?

Agreed

Would be nice, but if I get it right, the GB stuff is just more V8, and there's no attempt other than filename to differentiate once it's split?

Meows, Jim ...

Might be right about that.
Just would be nice to keep tabs on it separately.
Maybe not possible.

Meows.

It would also be nice to be nice to filter the view of tasks by the processor type. Such as CPU, ATI, iGPU, NVIDIA, & maybe ARM. When you are trying to find tack down an issue for a specific processor type and there are two or three in the host it can become time consuming unfiltered.

---

SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[

What about AstroPulse task from GBT? Will they be available in future, or are AP's only from Arecibo?

Got anyone some GBT tasks for AMD GPU already ?
I only got 9 for CPU so far.

---

With each crime and every kindness we birth our future.

Ran the SoG testcase bench under the 364.72 driver Jacob was worried about - no problem found (though my test was Windows 7, his Windows 10).

SSP shows 5 splitters active, but SSP only shows one tape getting split, and only 1 channel in progress on tape(dark green block) Should that not be 5 blocks, for consistency with Aricebo stuff?

Now that more tapes are being split, it looks as though the above is incorrect, and that in fact a single channel is a very, very skinny green, barely visible.
Makes sense, I guess, given the scale a larger number of channels per tape means each channel is a tinier piece of the bar chart. Tired eyes here?

---

Because AFAIK most of the GB data is VLAR and the paucity of APs I can foresee many of the big Nvidea GPUs will run out of data.

---

So do we yet have good estimates on these new work units?

I'm seeing a wide fluctuation on times

4854604170
angle 0.008804
Time to complete 53 min 4 sec
0 spike
1 autocorrect
4 pulse count
1 triplet

4854604378
angle 0.008804
Time to complete 2 min 11 sec

4854604345
angle 0.008804
Time to complete 11 min 2 sec
14 spike count
0 auto
16 pulse count

4854604470
angle 0.008804
Time to complete 51 min 27 sec
1 spike
5 pulse count


So I'm not seeing any patterns yet. Anyone else?

Because AFAIK most of the GB data is VLAR and the paucity of APs I can foresee many of the big Nvidea GPUs will run out of data.

When both Green Bank and Arecibo WUs are being generated, I wonder if it would better to distribute the work load between GPU and CPU differently, i.e., limit CPUs to only VLAR work and GPUs to only non VLAR work. Right now CPUs can run both and GPUs, at least Nvidia GPUS, can only run non VLAR which heavily favors the CPUs. I would think it would be more productive to ensure there is work for both CPU and GPU by making sure that CPUs are doing work that only the CPU can do so that there is work for the GPU.

Because AFAIK most of the GB data is VLAR and the paucity of APs I can foresee many of the big Nvidea GPUs will run out of data.

Yeah, worried about that myself ...

---