Well I'm not having much luck.Ran ok for about 27hrs,on one core with seti and rosetta on one core. Whent to nnt on bouth seti and rosetta, then astro began running on both cores,then boincmgr would exit,suspended astro with no change, aborted bouth wus and now boinc running ok.XP with P2d 920 and boinc 6.1.0. don't knpw what to do now. Reported this at astropulse, but no feedback yet.Wondering if I should resume astro...

Voyager

Thank You

I suspect that an upgrade to BOINC 6.2.6 should take care of the problem.
6.1.x was not ready for prime time.

Regards
Al

Well I'm not having much luck.Ran ok for about 27hrs,on one core with seti and rosetta on one core. Whent to nnt on bouth seti and rosetta, then astro began running on both cores,then boincmgr would exit,suspended astro with no change, aborted bouth wus and now boinc running ok.XP with P2d 920 and boinc 6.1.0. don't knpw what to do now. Reported this at astropulse, but no feedback yet.Wondering if I should resume astro...

---

Please consider a Donation to the Seti Project.

I suspect that an upgrade to BOINC 6.2.6 should take care of the problem.
6.1.x was not ready for prime time.

easy upgrade, we'll see how it works. Thanks..

Voyager et al

I do have note that 6.2.6 is still not quite ready for prime time. So as I also participate in BOINC Alpha it is certainly better than 6.1.x

I suspect that an upgrade to BOINC 6.2.6 should take care of the problem.
6.1.x was not ready for prime time.

easy upgrade, we'll see how it works. Thanks..

Edit Other Notes
A reminder that some of the BOINC Core Clients are outdated and should be upgraded. I posted information that lead to a fix for 5.10.45 which should at some point in time be incorporated into 5.10.46

A push is happening to fix the bulk of issues (BOINC) in 6.2.6 to make it the "stable" release. One of the key things about the 6.2.x version are to increase Machine Security along with providing for separation of the Project (Seti) Application into just crunching and looking at the pretty graphics. It would improve the performance for many projects. That is the 6.x application in Seti Beta (on hold) to account for that.

---

Please consider a Donation to the Seti Project.

Finished a 4.33 app for AP, on my P4 2.8GHz w/HT enabled, 2GB RAM, Win XP SP3, took 544,326.80 seconds to finish, claiming 767.72 credit. Just a little over 7 days, that was straight crunching with POEM@HOME running along side it.

---

Let's be honest the Beta experience is crap.
You crunch for 150 hr and the WU errors out and sometimes your system crashes.
You crunch for 100 hr and the Dev requests that you abort all your WUs so you can immediately start testing a newer version of the application.
Such is the life of a Beta tester. But, if someone doesn't do it, Seti main would be a disaster for months when a new software was released.
The only consolation comes from knowing that the trials at Beta usually produces a relatively painless experience for the mainstream Seti users.

.... and if you expected better, then you don't understand beta testing, and you should not do it.

It is crap.

The contract I use for my beta testers says "We are giving you software to run which is broken. We know it's broken, we just don't know how it's broken. You agree to run it, and tell us how it is broken -- and you agree that problems are expected."

With a good group of beta testers, the release will go very well.

---

I'm the 1.3 million second one...

Long time

And I have no problems with it. Why? I'm beta testing the Mac app port from Dotsch. I have done a v4.30, a v4.31, and am doing a v4.33 right now. The only problem is that the Mac is so slow, I will be into a WU and the new port will come out, so I am about a week behind (and a few days late on the deadline). To be honest, I am happy to help the testing of the new AP app. The old G4 isn't very good at anything else...

---

Clk2HlpSetiCty:::PayIt4ward

Let's be honest the Beta experience is crap.
You crunch for 150 hr and the WU errors out and sometimes your system crashes.
You crunch for 100 hr and the Dev requests that you abort all your WUs so you can immediately start testing a newer version of the application.
Such is the life of a Beta tester. But, if someone doesn't do it, Seti main would be a disaster for months when a new software was released.
The only consolation comes from knowing that the trials at Beta usually produces a relatively painless experience for the mainstream Seti users.

.... and if you expected better, then you don't understand beta testing, and you should not do it.

It is crap.

The contract I use for my beta testers says "We are giving you software to run which is broken. We know it's broken, we just don't know how it's broken. You agree to run it, and tell us how it is broken -- and you agree that problems are expected."

With a good group of beta testers, the release will go very well.

........I'm currently beta testing Powerpack 1 for Windows Home Server, & so far, so good. The satisfaction of seeing the public release solving issues(including on my own server) is great.

I moaned about MS software & now instead of moaning, doing something about it..........& gladly.

---

Both of these URLs seem to point to the exact same webpage.

To point out the 'obvious', a webpage would be stored on the computer at the IP address, regardless of the URL. The URL in many cases is a 'shortcut', pointing to the IP Address Computer (example: My job has several computers, and on each one D: and E: point to the same network folder. The reason? Some older programs reference D:, the rest know about E:...)

If one is "correct" for the project and the other is "wrong"... then the wrong one should point to and load the correct one to avoid confusion, IMO. But then I am only a programmer and am ignorant to details of webpage management... Maybe what I suggest makes no sense to project webmasters.

As for 'webpage management', I have no direct experience, but... I have gathered (somewhere, without being able to point out where, immediately...) that Seti Main and Seti Beta used the same main URL (setiweb.[ssl.]berkeley.edu), then one moved for some reason and the other didn't. Could be 'laziness', could be politics, could be Murphy even...

When I went to attach to "SETI Beta" via BOINC Manager, I didn't see the project listed on on the popup selection list. So I performed a google search on seti+astropulse. The first returned result seemed the only reasonable result on the first page and after viewing, seemed especially reasonable. Only after attaching to it and DL ~150 hours of AP 4.33 work I view my "messages" where I was informed that I attached to the "wrong" URL and provided with the "correct" project URL.

It's no problem... I'm just making comments about my "attaching to SETI Beta experience"... I'll detatch then reattach to the "correct" URL after my AP queue is empty.

Well now you know... ;-)

---

As for 'webpage management', I have no direct experience, but... I have gathered (somewhere, without being able to point out where, immediately...) that Seti Main and Seti Beta used the same main URL (setiweb.[ssl.]berkeley.edu), then one moved for some reason and the other didn't. Could be 'laziness', could be politics, could be Murphy even...

The only "official" address for "release"-SETI/BOINC is setiathome.berkeley.edu but at any given time one or more other addresses can also be used, example whatever machine the web-server is currently running on has been usable. But, these "other addresses" can be disabled at any given time, so should not be used. Before release, BOINC beta used maggie.* and possibly for some time setibeta or something.

After release then SETI beta was re-started, it was quickly discovered IE didn't correctly handle cookies using same url, even one was /beta and other not, and for this reason the beta was moved to using setiweb.

---

"I make so many mistakes. But then just think of all the mistakes I don't make, although I might."

Well hopefully they will speed astropulse up some before release. I will be gone to LA for a couple months so I set my astropulse machine for no tasks and will let it run seti while I am gone since I can't update the betas while away.

---

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

My Astrokitty crashed............

I don't think it was Astrokitty's fault......the Frozen Penny seems to have a mind of it's own lately..........hope the few results I did turn in helped.......

---

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

Mark

If you could report in Seti Beta, that would give everyone a chance to insure that the Scheduler/Validator portion is working and your "wingmen" know.

I would hate to think that AP melted the Ice around the Frozen Penny... LOL
Or the Kitties now have wet feet...

Al

My Astrokitty crashed............

I don't think it was Astrokitty's fault......the Frozen Penny seems to have a mind of it's own lately..........hope the few results I did turn in helped.......

---

Please consider a Donation to the Seti Project.

Mark

If you could report in Seti Beta, that would give everyone a chance to insure that the Scheduler/Validator portion is working and your "wingmen" know.

I would hate to think that AP melted the Ice around the Frozen Penny... LOL
Or the Kitties now have wet feet...

Al

My Astrokitty crashed............

I don't think it was Astrokitty's fault......the Frozen Penny seems to have a mind of it's own lately..........hope the few results I did turn in helped.......

Well.....the kitties did finish a bit o' Astrokitty work.....
But then the ice melted......

I could do some more if you feel it is warranted......
Please advise........a slower but steadier Penny seems to be the ticket right now.......
Trying to get it's RAC back up to where it really belongs.....
My new Q9450 is kicking the Penny's butt right now........that just ain't right.....
3.6gig or so VS 4.3 gig.....???
It's just a matter of time......but that is a tune I shall post in the Cafe.........

---

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

I had to suspend QMC & Astropulse a few days ago due to heat problems on quad. Problem resolved & wu's crunching again.

Question: - When Astropulse goes mainstream, will they still be as long? I'm not bothered if they are, just curious.

---

I had to suspend QMC & Astropulse a few days ago due to heat problems on quad. Problem resolved & wu's crunching again.

Question: - When Astropulse goes mainstream, will they still be as long? I'm not bothered if they are, just curious.

Probably, but next year with new computers and after the optimisers have done there wonderful deeds again, they will only take a few hours.

Ever the optimist.

Andy

So with the coming of Astropulse, everyone here will be forced then to crunch for both Seti and Astropulse? No choices at all? Just overnite you are in the Astropulse project without joining the project or attaching to the project? Seems rather undemocratic for a project being run from Berkeley, USA! Will credits earned for Astropulse be seperate from Seti?

---

Boinc....Boinc....Boinc....Boinc....

So with the coming of Astropulse, everyone here will be forced then to crunch for both Seti and Astropulse? No choices at all? Just overnite you are in the Astropulse project without joining the project or attaching to the project? Seems rather undemocratic for a project being run from Berkeley! Will credits earned for Astropulse be seperate from Seti?

There will be the ability to choose only to crunch AP or MB by using appropriate app_info.xml files.
Why should credits be separate, AP is only another way of looking for ET based on his radio transmissions.

I had to suspend QMC & Astropulse a few days ago due to heat problems on quad. Problem resolved & wu's crunching again.

Question: - When Astropulse goes mainstream, will they still be as long? I'm not bothered if they are, just curious.

Probably, but next year with new computers and after the optimisers have done there wonderful deeds again, they will only take a few hours.

Ever the optimist.

Andy

Optimization may be more difficult with AstroPulse. About a year ago, Tetsuji 'Maverick' Rai looked into building it with ICC and IPP and posted in part:

One thing I can say is these source files are precision-sensitive with ICC. With Intel compiler, with normal options, the binary will be an inaccurate cruncher, while s@h_enhanced was relatively accuracy tolerant.

Eric and Josh have kept their options open and haven't promised any specific changes to the length of work or deadlines. The AstroPulse Algorithms and Science page does have a statement indicating that (when it was written) they were considering some change in length (number of large DM chunks).

                                                                   Joe

Have noticed over the past several days that on reboot, this wu keeps resetting to 0, with the time to completion staying at 02:03, yet each time before the reboot it had already completed 4 hours or more. Is this normal? Other wu's no problem.

02/07/2008 02:39:31|SETI@home Beta Test|Restarting task 23ap08aa.14671.4980.3.11.23_1 using setiathome_enhanced version 602

---