Eric,

Is there any chance you could give us an update on Multi-Beam and AP, and give us some idea of your plans for the near future.
I assume from what has been said on the Main Site, that Multi-Beam will have to be introduced there soon.

So can we expect a new pre-release version here?

If so do how long do you plan to run it, assuming that there are no unforseen problems?

I ask this as due to AP units, mine, and I'm sure everybody elses RDCF has sky rocketed. Mine were below 0.5 when doing Multi-beam only. Now both machines are about 5.0. Also because of the server problems, the AP units have had a clear run on the CPU and Beta now has very large short and long term debts. Plus the AP unit I still have left has been and is going to be in EDF,
or whatever JM7 calls it these days, mode, further delaying any Beta downloads.

So for my computers, at least, they are are not likely to download any Beta work for a week or two without intervention.

Andy

Further thoughts on MultiBeam,

Have you any plans to increase sensitivity again, or any other methods of increasing the processing time?

Other methods, larger units. The size of units, 350KByte, has been constant since beginning of Classic, when we were mainly on dial-up. As most of us, that can, are on broadband, is it possible to increase unit size and processing time?

Reasons I ask,
Seti-centric people with latest dual core 2 Xeons are already claiming that 4 cpu and 100 units/cpu are being reached.
Personally I think this could only happen on the most extreme of days, but the next generation of cpu's, 3rd or 4th qtr 2007, will probably reach this limit.

Andy

Reasons I ask,
Seti-centric people with latest dual core 2 Xeons are already claiming that 4 cpu and 100 units/cpu are being reached.
Personally I think this could only happen on the most extreme of days, but the next generation of cpu's, 3rd or 4th qtr 2007, will probably reach this limit.

Reasons I ask,
Seti-centric people with latest dual core 2 Xeons are already claiming that 4 cpu and 100 units/cpu are being reached.
Personally I think this could only happen on the most extreme of days, but the next generation of cpu's, 3rd or 4th qtr 2007, will probably reach this limit.

I have been hitting the limit frequently in recent days. But to be clear, my machine is a dual quad-core (8-way), not dual dual-core.

If I understand correctly, the limit is 100 per core per day, with a total limit of 400. That works for machines with up to 4 cores. With an 8-way machine, that really means 50/core/day. And if you get a bunch of the little WUs (like we have been lately), it is very easy to hit the limit.

I have been hitting the limit frequently in recent days.

I have been hitting the limit frequently in recent days.

Darn it, anyway! I would love to have your problem, you've got a great machine as well.

I thought we were out of AP WUs (the loooooong ones). I was just finishing my last one, it's been running for 4..5 days, and so I thought I could then fix my DCF and start running some short 5.17 WUs because I need the credit! So anyway, the AP WU finished and what do I get? Darn it! Two more AP WUs, just my luck I guess.

My current complaint (it's not a really big deal) is that the pending credit (especially for the AP WUs) is getting to be ridiculous, I've got 9000 pending credits on my one computer. It's taking a month or more for some of the AP WUs to get finished and returned by many users. I guess that's to be expected for Beta so don't go get all excited about my ranting.

I have been hitting the limit frequently in recent days.

Darn it, anyway! I would love to have your problem, you've got a great machine as well.

I thought we were out of AP WUs (the loooooong ones). I was just finishing my last one, it's been running for 4..5 days, and so I thought I could then fix my DCF and start running some short 5.17 WUs because I need the credit! So anyway, the AP WU finished and what do I get? Darn it! Two more AP WUs, just my luck I guess.

My current complaint (it's not a really big deal) is that the pending credit (especially for the AP WUs) is getting to be ridiculous, I've got 9000 pending credits on my one computer. It's taking a month or more for some of the AP WUs to get finished and returned by many users. I guess that's to be expected for Beta so don't go get all excited about my ranting.

I have been hitting the limit frequently in recent days.

Darn it, anyway! I would love to have your problem, you've got a great machine as well.

I thought we were out of AP WUs (the loooooong ones). I was just finishing my last one, it's been running for 4..5 days, and so I thought I could then fix my DCF and start running some short 5.17 WUs because I need the credit! So anyway, the AP WU finished and what do I get? Darn it! Two more AP WUs, just my luck I guess.

My current complaint (it's not a really big deal) is that the pending credit (especially for the AP WUs) is getting to be ridiculous, I've got 9000 pending credits on my one computer. It's taking a month or more for some of the AP WUs to get finished and returned by many users. I guess that's to be expected for Beta so don't go get all excited about my ranting.

I wish I could get at least 1 Astropulse WU, the server thinks I don't have enough memory:

SETI@home Beta Test|Message from server: Your computer has 255.48MB of memory, and a job requires 256.00MB

I have done 1 previous AP task about a month ago with ver 4.12:

http://setiweb.ssl.berkeley.edu/beta/result.php?resultid=1691738
http://setiweb.ssl.berkeley.edu/beta/workunit.php?wuid=437679

I thought I was still waiting for credit for this one, but I've just noticed on the result page it has been granted, but not on the WU page.

I beleive the requirement is 144MB, would it be possible to configure the server so that computers with 256MB or 192MB could get AP tasks?

I have been hitting the limit frequently in recent days.

Darn it, anyway! I would love to have your problem, you've got a great machine as well.

I thought we were out of AP WUs (the loooooong ones). I was just finishing my last one, it's been running for 4..5 days, and so I thought I could then fix my DCF and start running some short 5.17 WUs because I need the credit! So anyway, the AP WU finished and what do I get? Darn it! Two more AP WUs, just my luck I guess.

My current complaint (it's not a really big deal) is that the pending credit (especially for the AP WUs) is getting to be ridiculous, I've got 9000 pending credits on my one computer. It's taking a month or more for some of the AP WUs to get finished and returned by many users. I guess that's to be expected for Beta so don't go get all excited about my ranting.

I wish I could get at least 1 Astropulse WU, the server thinks I don't have enough memory:

SETI@home Beta Test|Message from server: Your computer has 255.48MB of memory, and a job requires 256.00MB

I have done 1 previous AP task about a month ago with ver 4.12:

http://setiweb.ssl.berkeley.edu/beta/result.php?resultid=1691738
http://setiweb.ssl.berkeley.edu/beta/workunit.php?wuid=437679

I thought I was still waiting for credit for this one, but I've just noticed on the result page it has been granted, but not on the WU page.

I beleive the requirement is 144MB, would it be possible to configure the server so that computers with 256MB or 192MB could get AP tasks?

Isn't it actually easier if you looked for a used memory-board instead? a pair of 256MBs are possible to get for 20-30USD nowadays.

I have been hitting the limit frequently in recent days.

Darn it, anyway! I would love to have your problem, you've got a great machine as well.

I thought we were out of AP WUs (the loooooong ones). I was just finishing my last one, it's been running for 4..5 days, and so I thought I could then fix my DCF and start running some short 5.17 WUs because I need the credit! So anyway, the AP WU finished and what do I get? Darn it! Two more AP WUs, just my luck I guess.

My current complaint (it's not a really big deal) is that the pending credit (especially for the AP WUs) is getting to be ridiculous, I've got 9000 pending credits on my one computer. It's taking a month or more for some of the AP WUs to get finished and returned by many users. I guess that's to be expected for Beta so don't go get all excited about my ranting.

I wish I could get at least 1 Astropulse WU, the server thinks I don't have enough memory:

SETI@home Beta Test|Message from server: Your computer has 255.48MB of memory, and a job requires 256.00MB

I have done 1 previous AP task about a month ago with ver 4.12:

http://setiweb.ssl.berkeley.edu/beta/result.php?resultid=1691738
http://setiweb.ssl.berkeley.edu/beta/workunit.php?wuid=437679

I thought I was still waiting for credit for this one, but I've just noticed on the result page it has been granted, but not on the WU page.

I beleive the requirement is 144MB, would it be possible to configure the server so that computers with 256MB or 192MB could get AP tasks?

Isn't it actually easier if you looked for a used memory-board instead? a pair of 256MBs are possible to get for 20-30USD nowadays.

I do have a spare 256MB, but it is SDRAM and the 256MB which is fitted is DDR. My MoBo is an ASRock K7VT2 which has 2 DDR slots and 2 SDRAM slots, but the manual says you can only fit 1 type or the other, not both.

Any opinions on which type is better to get?

I recieved a reply from Eric... Yes I know he has been busy...

One thing that you should notice shortly is that Your Pending Credit has dropped and you should have credit for the bulk of the AP Results... Eric managed fit into "all those things happening" a working AP Validator...

Josh is looking at the AP Results return thus far, scratching his head and trying to make some sense out of what he is looking at... Then what adjustments can be made and what has to be done...

Eric does have the proposed changes from Joe towards 5.18... Getting them incorporated is high the list of things to get done...

A couple of other things to be noted are if you are having problem with contacting the Beta Server, You might need to shutdown BOINC and Restart or Restart the Computer... It would appear that BOINC Collected some trash it refuses to get rid of even though the Servers are Up and Running...

A reminder about the broken Server Status Page... There are enough things going on that it will probably be a while before it is fixed.

Pappa




____________
Thanks to Paul and Friends
Please consider a Donation to the Seti Project

I recieved a reply from Eric... Yes I know he has been busy...

One thing that you should notice shortly is that Your Pending Credit has dropped and you should have credit for the bulk of the AP Results... Eric managed fit into "all those things happening" a working AP Validator...

Josh is looking at the AP Results return thus far, scratching his head and trying to make some sense out of what he is looking at... Then what adjustments can be made and what has to be done...

Eric does have the proposed changes from Joe towards 5.18... Getting them incorporated is high the list of things to get done...

A couple of other things to be noted are if you are having problem with contacting the Beta Server, You might need to shutdown BOINC and Restart or Restart the Computer... It would appear that BOINC Collected some trash it refuses to get rid of even though the Servers are Up and Running...

A reminder about the broken Server Status Page... There are enough things going on that it will probably be a while before it is fixed.

Pappa

Andy, et al

If we can get them catalogged I will run them past Eric

Pappa,
Thanks for passing on the news. It is appreciated.

One other small thing that needs looking at is the bad exit on some windows computers after finding 30 pulses. This may not be an AP only error as it is seen on Multi-Beam and in the standard app Enhanced app (I have not seen it in optimised app).

This AP unit 461257 is an example. Three hosts exited gracefully and Validated, 4 host exitted with - exit code -1073741819 (0xc0000005). All 7 hosts found 30 pulses and all took over 120k sec.

Andy

You missed one
____________

Another one missed (host 7966 on this one).

A different issue on This one . No credit granted / check skipped (host 4872) even though it exited gracefully with 30 pulses.
____________
!!Stupidity should be PAINFUL!!

Another one missed (host 7966 on this one).

A different issue on This one . No credit granted / check skipped (host 4872) even though it exited gracefully with 30 pulses.

And another

Of course this was uploaded and reported today - instantly awarded zero.
____________

Sorry Folks

I should have been looking, "we" have very many reports that are Ap validate issues... Eric got this working inbetween various outage things and something he is doing in the background. I created a thread in Astropulse for the links to these issues.

Validate Errors with AP

Please repost there so I can point Eric at them...


____________
Thanks to Paul and Friends
Please consider a Donation to the Seti Project

A reminder about the broken Server Status Page... There are enough things going on that it will probably be a while before it is fixed.

Pappa

And another

Of course this was uploaded and reported today - instantly awarded zero.