SETI@home Beta Test : forum : 'VLAR WUs not to GPU'

;-)

---

If you would like to test also, this is the URL of SETI@home Beta Test for your BOINC: http://setiweb.ssl.berkeley.edu/beta

---

It's look like it work well on my system.

How it's on your system?

Write there:
SETI@home Beta Test : forum : 'VLAR WUs not to GPU'

;-)

---

Looks like it worked on mine so far...They take 20 hours on my CPU. If seti could do that much work on units it would really cut down server traffic. 10 day cache would be many.

---

Official Abuser of Boinc Buttons...
And no good credit hound!

I made a quick look to your PC at SETI@home Beta Test..

You let run stock apps there..
You have 4 AP WUs DLed there.
And the first reported AP result needed ~ 19 hours.

We wanted to test the new '(MB) VLAR WUs not to GPU'.. ;-)

If you would like to test, you should disable AP in the project preferences.

You could take opt. apps at SETI@home Beta Test, if the app (version) is already published here at SETI@home.

I let run opt. AK_v8b for CPU and stock 6.09_cuda23 for GPU there.

---

I made a quick look to your PC at SETI@home Beta Test..

You let run stock apps there..
You have 4 AP WUs DLed there.
And the first reported AP result needed ~ 19 hours.

We wanted to test the new '(MB) VLAR WUs not to GPU'.. ;-)

If you would like to test, you should disable AP in the project preferences.

You could take opt. apps at SETI@home Beta Test (if the app (version) is already published here at SETI@home).

I let run opt. AK_v8b for CPU and stock 6.09_cuda23 for GPU there.

I changed the settings in seti beta to:
SETI@home Enhanced: yes
Astropulse: no
Astropulse v5: no
Is this correct?

---

Official Abuser of Boinc Buttons...
And no good credit hound!

I looked to the preferences here, it should look similar at BETA:

Run only the selected applications SETI@home Enhanced: yes
Astropulse: no
Astropulse v5: no
If no work for selected applications is available, accept work from other applications? no


BTW. But current both project server are down, or?

---

I looked to the preferences here, it should look similar at BETA:

Run only the selected applications SETI@home Enhanced: yes
Astropulse: no
Astropulse v5: no
If no work for selected applications is available, accept work from other applications? no


BTW. But current both project server are down, or?

OK thats what I have, will give it a shot when severs are up. So far it only asked for CPU work when I let it ask.

---

Official Abuser of Boinc Buttons...
And no good credit hound!

I guess you have too much GPU WUs from SETI@home DLed.. ;-)

---

It's look like it work well on my system.

How it's on your system?

Write there:
SETI@home Beta Test : forum : 'VLAR WUs not to GPU'

;-)

And your experiences then there.. ;-)

---

Now enabled at SETI@home: 'VLAR WUs not to GPU'

'server run, July 23-26 2010'

A big 'Thanks a lot!' to the admins! *thumb up*


EDIT of the title of this thread from 'Test with us - ..' to 'Now enabled @ SETI@home ..'.

---

As for seeing the change - I just got a bunch marked vlar to the CPU.
I'd have assumed the oldest files get sent out first? Have we run through all pre-change already?

---

Carola
-------
I'm multilingual - I can misunderstand people in several languages!

As for seeing the change - I just got a bunch marked vlar to the CPU.
I'd have assumed the oldest files get sent out first? Have we run through all pre-change already?

That's how Jeff said it would work.

I still received 3 VLARs that were sent to My gpus, I'll be running rescheduler 1.9 until I see no need to run It anymore.

Jeff's post said it would not affect work that has already been split, but not sent out. Only the new work split will have this done to them.

---

The splitters right now are cooking about 40 WU's a second and down to ~180000

So we should see by in the morning.

Regards

---

Please consider a Donation to the Seti Project.

I still received 3 VLARs that were sent to My gpus, I'll be running rescheduler 1.9 until I see no need to run It anymore.

In addition to those which were probably split during the latest outage, VLARs have a 46.5 day deadline and reissues obviously can't change the WU name to have a .vlar added. There will be a possibility of getting such a reissue for at least several months, though they should be very rare within about 2 months.

                                                               Joe

I don't think it's because of the usage of the ReSchedule V1.9 tool..
My BOINC DL .vlar WUs for GPU.

So I guess the '.vlar WUs not to GPU' work not well here at SETI@home.


How it's with your BOINC?

---

I don't think it's because of the usage of the ReSchedule V1.9 tool..
My BOINC DL .vlar WUs for GPU.

So I guess the '.vlar WUs not to GPU' work not well here at SETI@home.

How it's with your BOINC?

It'll download them, if they are present in the feeder queue.

The server modifications only prevent new VLAR tasks being added to that queue - old ones being resent will still be downloaded, as before. Are your VLARs all replication _2, _3 and above? They should be.

The WUs have endings of .vlar_0 and .vlar_1 and are DLed for '608 cuda' (app_info.xml).

---

The WUs have endings of .vlar_0 and .vlar_1 and are DLed for '608 cuda' (app_info.xml).

You're right, this .VLAR Wu has been sent to the GPU, maybe because it's a resend? (Edit: i now see you have others sent to the GPU, that aren't resends)

http://setiathome.berkeley.edu/workunit.php?wuid=636108071

Claggy