I purposely didn't post Beta's Url, If anyone want to join Beta, all they need is enough Gumption to Google Seti Beta. ;-)

Claggy

I purposely didn't post Beta's Url, If anyone want to join Beta, all they need is enough Gumption to Google Seti Beta. ;-)

Claggy

It work also with adding /beta to the SETI@home URL.
But IIRC, I got problems in past with this URL.

So for to be sure, I posted the correct SETI@home Beta Test (http://setiweb.ssl.berkeley.edu/beta) URL.

;-)

---

BTW.

Maybe also interesting Jeff. Since ~ 2 months.. 'unable to change project preferences'.

---

Never mind trying to connect to beta. We have a serious connectivity problem. If we don't get it fixed soon, I will put out a news item about it. This does not bode well for putting the main servers on line tomorrow.

I have it set now in my Boinc, let me know if you need me to test some GPU's for you.

---

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

Never mind trying to connect to beta. We have a serious connectivity problem. If we don't get it fixed soon, I will put out a news item about it. This does not bode well for putting the main servers on line tomorrow.

Ohhh, I don't like the sound of that!!! Pick the biggest guy in the lab and send him down the hill to kick some IT behind!!! Even if it isn't their fault it will make you feel better! :-)

---

PROUD MEMBER OF Team Starfire World BOINC

Okay, who kicked the Ethernet cable out from the router??? Or, possibly this has anything to do with the work toward the gigabit connection to campus???

Never mind trying to connect to beta. We have a serious connectivity problem. If we don't get it fixed soon, I will put out a news item about it. This does not bode well for putting the main servers on line tomorrow.

Good to hear and not so good to hear, Thankfully Seti flooded Me with way more than I ever asked for, So I couldn't download If I tried.

---

My Computer Builds and Other Projects
My Amazon Wishlist

Thank you for the change. Personally, I will be extremely happy when this goes mainstream. As it has likely been for others, it has been frustrating for me to see the VLAR WUs take approximately five times the GPU processing time for the same amount of credit.

---

As the 'WU limit in progress' was increased at Monday afternoon my time, my BOINC got .vlar endings WUs for the GPU.
On my system it don't work well here at SETI@home.

I have an app_info.xml file with 608 and cuda entries.
My BOINC have current 41 .vlar_0 and .vlar_1 WUs for GPU (So this are new ones).

At SETI@home Beta Test I have an app_info.xml file with 609 and cuda23 entries and there it worked well.

It can be that it don't work well with 608 and cuda entries in the app_info.xml file?

---

As the 'WU limit in progress' was increased at Monday afternoon my time, my BOINC got .vlar endings WUs for the GPU.
On my system it don't work well here at SETI@home.

I have an app_info.xml file with 608 and cuda entries.
My BOINC have current 41 .vlar_0 and .vlar_1 WUs for GPU (So this are new ones).

At SETI@home Beta Test I have an app_info.xml file with 609 and cuda23 entries and there it worked well.

It can be that it don't work well with 608 and cuda entries in the app_info.xml file?

The change has not been implement at SETI main yet.

---

BOINC WIKI

As the 'WU limit in progress' was increased at Monday afternoon my time, my BOINC got .vlar endings WUs for the GPU.
On my system it don't work well here at SETI@home.

I have an app_info.xml file with 608 and cuda entries.
My BOINC have current 41 .vlar_0 and .vlar_1 WUs for GPU (So this are new ones).

At SETI@home Beta Test I have an app_info.xml file with 609 and cuda23 entries and there it worked well.

It can be that it don't work well with 608 and cuda entries in the app_info.xml file?

The change has not been implement at SETI main yet.

Yes, it has. See Jeff's note here.

But due to a bad pass-down, it was disabled for a short-time by changes Dr. A had Matt make on Monday. It should be back in force now, but Matt said some WUs went out on Monday under the old system before he fixed the changes. That may be what happened to Sutaru. There will also be resends that were split under the old system, Jeff thought maybe for several months.

Just wondering if anyone has any idea of when GPUs will stop getting VLAR WUs (from the old system before the .vlar update). I am just wondering, as I keep checking and finding that several non-tagged VLAR WUs are still being sent to my GPU.

I'm patient to wait for the old WUs to go through their process, I just don't like not knowing if I can stop checking or not.

---

Soli Deo Gloria

Just wondering if anyone has any idea of when GPUs will stop getting VLAR WUs (from the old system before the .vlar update). I am just wondering, as I keep checking and finding that several non-tagged VLAR WUs are still being sent to my GPU.

I'm patient to wait for the old WUs to go through their process, I just don't like not knowing if I can stop checking or not.

That can take many many months, due to all resends that happens for various reasons.

---

Too much hormone treated meat.
Too much Monsanto veggies.
Too old and outdated constitution.
A crazy problem, as you Yanks use to say......
There is no God, and God never existed.

Just wondering if anyone has any idea of when GPUs will stop getting VLAR WUs (from the old system before the .vlar update). I am just wondering, as I keep checking and finding that several non-tagged VLAR WUs are still being sent to my GPU.

I'm patient to wait for the old WUs to go through their process, I just don't like not knowing if I can stop checking or not.

You would need to use Fred's BOINC Rescheduler tool for to protect your GPU for old re-sent VLAR WUs.

---

I never got third-party stuff to work properly, so I wrote my own program.

Okay, so we can't really know for sure. That's all I needed to know, thanks.

---

Soli Deo Gloria

I never got third-party stuff to work properly, so I wrote my own program.

Okay, so we can't really know for sure. That's all I needed to know, thanks.

There actually is a for sure cutoff based on the delay_bound which sets the deadline, and the limit on number of replications. The longest delay_bound in that range is 54.32 days, the max total replications are 10. The last unmarked VLAR work was produced accidentally Monday July 26 2010, so I make the date for absolute safety about January 21 2012.

Almost all VLARs have a delay_bound of 46.5 days and it's highly unlikely for more than 2 hosts to fail to complete and report the tasks, so by the end of the third deadline cycle on December 6 2010 I'd expect reissues of those unmarked VLARS to be negligibly few.

                                                                 Joe