I don't think the ram problems have anything to do with AP....
I did finally manage to complete a WU running on one stick of ram......

Don't know what all the do-dah in the stderr output is about.....

About 20.74 hours for 798.96 credits........ouch.......doing MB work, that cpu time would be worth about 2,200 credits........
Of course, that would be with the new AK V8 opti app.......and no debugging going on in the background......

Will crunch the rest of the WUs for your perusal.......

EDIT....
Pappa....I have not kept up with it, and I assume many others have not either....
Could you condense in a nutshell what the advantage/difference in AP vs MB processing is in terms of the project's goals (and ours)?

---

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

Mark et al

For the moment AP credits do not matter, as it will be adjusted before release (and it being worked on in Seti Beta). The goal has been to get it working thus the "do-dah" in the stderr output...

For the Goals, that is a bit tougher as Seti's Goal is to Find ET.
Both Enhanced MultiBeam and Astropulse are "complimentary" towards Seti's Goal.
Some Users have goals beyond just "Find ET."

If we start with Enhanced MultiBeam we have a large pool of enhanced/non enhanced data to search/match using a "narrow beam" search. NTPCKR should be starting to retrieve/sort more information from that. So if we look at information gleaned from Seti Classic, there is much more known about a large portion of the sky. MultiBeam will continue to refine that (Version 6.x is in Seti Beta waiting for AP to complete there). If I look quickly back to MultiBeam version 6.x one of the goals is to separate the "graphics function" from the application. That in itself will make the standard version even faster with some improvements for the search, as each new version contains something that was learned from previous versions...

Astropulse, the methods employed will actually give the true Pulse Frequency and true Power of the Pulse. The amount of data each User is given is longer 13.42 seconds of data. It will take a bit longer but is worth it in the long run. So whether it is ET or a Black Hole, a Pulsar or some new "thing" that has to be determined during analysis. Astropulse makes it easier to sort and say this is space noise, this is earth noise, this is a Pulsar, this is a Black Hole and "this one" we do not know what it is.
It will take a while to collect enough data to compare just Astropulse... It can be used to "validate" existing MultiBeam data. It has the possibility of getting someones attention to say "Go back and look at that area of the sky." Then sit and listen.
The data would then be fed through both Astropulse and MultiBeam... That once again Improves the Chances that ET can be proven sooner.

Or like the Old American Picture of the Motorcycle Cop sitting in the shade of the highway sign in the desert. I know someone (ET) will come speeding along.

So if we now look at the User side of things, Credit - AK V8 is It. I can make the pool of data "larger faster," I can chat in the Forums and We all wait for NTPCKR... There are some Teams that have a Goal of being in the #1 spot (pick a project or all projects) that is the goal for doing distributed computing. They really do not care about the "merits" of "any project" only the chase of credit and the #1 spot. I really am not sure where/what caused that to occur but it exists and it is not necessarily bad.

So over the last two years the contribution of "Each Seti Users" CPU Time, Hardware, Money (not to forget sharing information in the Forums) has changed the "outlook" of Seti. Each of those is Important to the Goal of Find ET! Each of those is Important to the Continued Success of Seti.

"You" are all part of this!

Thank You

Al

I don't think the ram problems have anything to do with AP....
I did finally manage to complete a WU running on one stick of ram......

Don't know what all the do-dah in the stderr output is about.....

About 20.74 hours for 798.96 credits........ouch.......doing MB work, that cpu time would be worth about 2,200 credits........
Of course, that would be with the new AK V8 opti app.......and no debugging going on in the background......

Will crunch the rest of the WUs for your perusal.......

EDIT....
Pappa....I have not kept up with it, and I assume many others have not either....
Could you condense in a nutshell what the advantage/difference in AP vs MB processing is in terms of the project's goals (and ours)?

---

Please consider a Donation to the Seti Project.

Thanks for the update Pappa, and for my daily update, things are picking up a bit I think...36 hours to completion of my first Workunit...

---

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

Thank you for the additional information Pappa....

I have now completed 4 AP WUs...all took about 20-1/2 hours to complete on the Frozen Penny.....
LOL....hope the do-dah info helps.....

---

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

Busy morning...Well down to a little over 5 hours to go on my first unit. It downloaded a new one to start on finally. This is on my Intel(R) Pentium(R) 4 CPU 2.80GHz.

---

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

My T2400 HP Lappie managed its first one in 80 hours for just over 800 creds. Second one is at 13.4% after 10 1/2 hours so seems to be running about the same. That's just crunching on one core as allowing both seems to get it a bit warm - over 65C and I prefer to keep it reading at or below 60C (current readings on the cores are 51 & 52 but the ambient is cooler than it was earlier in the week).

F.

---

Now have 5 completed........6 more to go..........
Astrokitty work takes a lonnnnnnnnnnnnnnnnnng time...........even on the Frozen Penny............

---

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

Well completed my first unit it took 155.25 hours. The next unit is ticking away slowly. I claimed 1334.05 but received 1261.42 Oh well see what the next one will do.

---

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

Well completed my first unit it took 155.25 hours. The next unit is ticking away slowly. I claimed 1334.05 but received 1261.42 Oh well see what the next one will do.

Ouch................so I suppose the 20 hour range is not too bad?

---

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

Maybe this has not been decided yet..........

When AstroPulse begins here on Seti, will everyone automatically start getting this work or do we join AstroPulse just like any another project?

---

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

The getting started page at astropulse leads to a 404. how do you attach,can't find an address?

The getting started page at astropulse leads to a 404. how do you attach,can't find an address?

The page is http://setiweb.ssl.berkeley.edu/beta/

The getting started page at astropulse leads to a 404. how do you attach,can't find an address?

Maybe it takes 20 hours or so to attach..........LOL...

---

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

Mark

If you could take a moment to pop into the Astropulse Forum and report times on the Results a Few are courious.

Regards

Al

Now have 5 completed........6 more to go..........
Astrokitty work takes a lonnnnnnnnnnnnnnnnnng time...........even on the Frozen Penny............

---

Please consider a Donation to the Seti Project.

Got there ok. have one wu says 165hrs.After I run my catche out of seti and rosetta, will see how it does.

Geek@Play

Users will get it automatically. Seti Beta Currently is the testing arm of Seti. As I said when Astropulse gets here we go back to testing the 6.x version of Enhanced MultiBeam.

Maybe this has not been decided yet..........

When AstroPulse begins here on Seti, will everyone automatically start getting this work or do we join AstroPulse just like any another project?

---

Please consider a Donation to the Seti Project.

Got there ok. have one wu says 165hrs.After I run my catche out of seti and rosetta, will see how it does.

My first WUs were estimated at 105 hours, but are only taking ~32 hours to complete on Q6600 @ 3200Mhz. 2 more to crunch after current one finishes.

Odd message in my log telling me that I attached to the "wrong" URL though...

6/13/2008 11:23:46 PM|SETI@home Beta Test|You used the wrong URL for this project
6/13/2008 11:23:46 PM|SETI@home Beta Test|The correct URL is http://setiweb.ssl.berkeley.edu/beta/
6/13/2008 11:23:46 PM|SETI@home Beta Test|Using the wrong URL can cause problems in some cases.
6/13/2008 11:23:46 PM|SETI@home Beta Test|When convenient, detach this project, then reattach to http://setiweb.ssl.berkeley.edu/beta/

I never knew that you could attach to a "wrong" URL ???

Voyager et al

The estimates that you see are based on the Duration Correction Factor (DCF) that your Enhanced MultiBeam is settled into.

You are more than welcome to let it run with Seti and Rosetta Running. So it will take the same amount of time it will give an idea of how well it switches back and forth.

So watching it the first few hours, then writing the time and the percent done you can get a better idea of how long it will take.

Got there ok. have one wu says 165hrs.After I run my catche out of seti and rosetta, will see how it does.

---

Please consider a Donation to the Seti Project.

My first WUs were estimated at 105 hours, but are only taking ~32 hours to complete on Q6600 @ 3200Mhz. 2 more to crunch after current one finishes.

Odd message in my log telling me that I attached to the "wrong" URL though...

6/13/2008 11:23:46 PM|SETI@home Beta Test|You used the wrong URL for this project
6/13/2008 11:23:46 PM|SETI@home Beta Test|The correct URL is http://setiweb.ssl.berkeley.edu/beta/
6/13/2008 11:23:46 PM|SETI@home Beta Test|Using the wrong URL can cause problems in some cases.
6/13/2008 11:23:46 PM|SETI@home Beta Test|When convenient, detach this project, then reattach to http://setiweb.ssl.berkeley.edu/beta/

I never knew that you could attach to a "wrong" URL ???

I'm not quite clear on WU uploads & downloads, but a website can have more than one registered URL that points to that IP address.
And from what I vaguely remember from something that happened months ago, the "primary" project address was http://setiweb.ssl.berkeley.edu/beta/, but the [re]Captcha license (used in updating the profiles) was registered to http://setiathome.berkeley.edu/beta/.

---

Hi,

When AstroPulse begins here on Seti, will everyone automatically start getting this work or do we join AstroPulse just like any another project?

It will be another application for the same project. When Astropulse has gone mainstream we will crunch two different types of workunits here at SETI@home (SETI enhanced multibeam and Astropulse).

And as long as you have an app_info.xml in place you won't get any application automatically. By using the app_info.xml here at SETI you are telling SETI "It's completely my own responsibility to get a new application".

Regards,
Carsten