I get 2 ap wu's

Then you should be able to receive AP work units... have you get some MB work units or nothing at all?

It has MB units no problem there just noticed everyone talking about the splitters working and wondered why I haven't received any. Still getting the No work message but will let it keep trying. Thanks.

Out of all of my machines that I have set to allow AP work Only 1 of them got 1 AP tasks. I have their venue set to:
Run only the selected applications
SETI@home Enhanced: no
Astropulse: yes
Astropulse v5: yes
If no work for selected applications is available, accept work from other applications? yes
So normally they roll the message you are seeing constantly.

---

SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[

I too have gotten only 1 AP since they have been out in the field again, and it was a shorty (500 credit or so).

---

"Life is a tragedy for those who feel, and a comedy for those who think."

"I never get into an argument that I cannot win."

I gave up still havn't got any and still get the message to check my web settings...

---

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

The problem isn't a lack of settings, it's a lack of Astropulse.

As I understand it, a tape yields approximately 1 Astropulse work unit for every 40 Multibeam workunits.

So, without an explicit "Astropulse 5.05" switch, the odds of getting one aren't very good.

With an explicit "Astropulse 5.05" switch, the odds of running out of work are very high -- or the odds of getting Multibeam because the three AP in the feeder queue have been issued is very high.

In other words, I'm not sure the switch would actually "work" -- at least not the way most seem to want it to work.

---

The problem isn't a lack of settings, it's a lack of Astropulse.

As I understand it, a tape yields approximately 1 Astropulse work unit for every 40 Multibeam workunits.

So, without an explicit "Astropulse 5.05" switch, the odds of getting one aren't very good.

With an explicit "Astropulse 5.05" switch, the odds of running out of work are very high -- or the odds of getting Multibeam because the three AP in the feeder queue have been issued is very high.

In other words, I'm not sure the switch would actually "work" -- at least not the way most seem to want it to work.

As long as there are far more empty pockets looking for AP work than there are AP WUs being split and sent, the odds of you getting any just because your switches are on are still not too good. Best to have it all turned on and take what comes down the pipe.

---

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

Not sure I want AP 505, I have just got an AP WU with estimated elapse of 635 hours , with deadline of abot 620 hours !

---

The estimated time to completion is just that, estimated. BOINC Manager is just being overly cautious with this first one. As it runs you should see the time drop fast as the % done goes up.

---

PROUD MEMBER OF Team Starfire World BOINC

The estimate is wrong. My P-M needs for one AP WU 34 hours and your i7 should be much faster than that even without optimized apps. No need to worry.

---

Not sure I want AP 505, I have just got an AP WU with estimated elapse of 635 hours , with deadline of abot 620 hours !

Don't worry - on Your computers:
Intel(R) Core(TM) i7 CPU 860 @ 2.80GHz
Intel(R) Core(TM)2 Quad CPU Q9400 @ 2.66GHz

it can/will be finished in ~25 hours with standard app (~15 h with optimized app)

---

 


- ALF - "Find out what you don't do well ..... then don't do it!" :)
 

Well indeed the I7 is hours off every 5 mins, BUT if that the estimate and the deadline is.....then why schedule it .
And BOINC manager has gone for it, in that it is running it at 'High Priority' to make sure it gets done !

Off thread, but I also have 48hours of GPU work stacked up, but until the AP WU arrived nothing Q'd for the CPUs ... bit odd, unless it could see it coming !?

---

hiamps:
I gave up still haven't got any and still get the message to check my web settings...

My settings:

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


The messages:

03-02-10 12:12:31 SETI@home Sending scheduler request: To fetch work.
03-02-10 12:12:31 SETI@home Requesting new tasks
03-02-10 12:12:37 SETI@home Scheduler request completed: got 1 new tasks
03-02-10 12:12:37 SETI@home Message from server: No work can be sent for the applications you have selected
03-02-10 12:12:37 SETI@home Message from server: No work is available for Astropulse v5
03-02-10 12:12:37 SETI@home Message from server: You have selected to receive work from other applications if no work is available for the applications you selected
03-02-10 12:12:37 SETI@home Message from server: Sending work from other applications
03-02-10 12:12:40 SETI@home Started download of 28se06aa.23988.81890.4.10.150
03-02-10 12:12:57 SETI@home Finished download of 28se06aa.23988.81890.4.10.150


As you can see I get MB tasks, I will get AP task if I am lucky (they are "rarities")
*

---

 


- ALF - "Find out what you don't do well ..... then don't do it!" :)
 

Well indeed the I7 is hours off every 5 mins, BUT if that the estimate and the deadline is.....then why schedule it .
And BOINC manager has gone for it, in that it is running it at 'High Priority' to make sure it gets done !

Off thread, but I also have 48hours of GPU work stacked up, but until the AP WU arrived nothing Q'd for the CPUs ... bit odd, unless it could see it coming !?

Just FYI:
"High Priority" - it does NOT mean the process (AP app) run in High CPU Priority (it still runs at low Priority as you can see in Windows Task Manager) -
"High Priority" means that this WorkUnit will be computed first in preference to other WUs
When in "High Priority" mode BOINC will not download new WUs

After finishing this AP WU your BOINC will learn how fast your CPU/APapp combination is and give more reasonable estimate in the future (e.g. 40 h).

If you install the optimized app you will see AP WUs complete in 10-15 h & estimate will go down to 20-25 h

If you want more work (for CPU & GPU) you can increase your WU cache:
(in ACCOUNT -> Computing preferences)
Maintain enough work for an additional 2 days
.

---

 


- ALF - "Find out what you don't do well ..... then don't do it!" :)
 

And BOINC manager has gone for it, in that it is running it at 'High Priority' to make sure it gets done !

As the estimate becomes more accurate, and there is no longer any question that it will finish on time, it will "fall out" of priority.

Also, "priority" is really only about the order work is done. BOINC doesn't do anything to get more time.

---

BOINC doesn't do anything to get more time.

Horrible Boinc Work-around #28 -- If estimates and deadlines are upsetting you, just set your clock back a month :-)

Those red bangs send the wrong message to the user. It implies crisis & mismanagement (although the second part may be slightly true, we're still grateful for any free cpu cycles the project gets).

At it's simplest, Boinc has two methods to determine what WU to crunch.
#1 -- Download order (w/shuffles between projects each hour).
#2 -- Deadline order -- signified with a red bang (interupts shuffles, downloads, etc).
Users don't get to select which mode to operate in. Boinc makes that determination based on the variables it has collected over time (although we can certainly force the later by being overly greedy on work buffers).

BOINC doesn't do anything to get more time.

Horrible Boinc Work-around #28 -- If estimates and deadlines are upsetting you, just set your clock back a month :-)

Those red bangs send the wrong message to the user. It implies crisis & mismanagement (although the second part may be slightly true, we're still grateful for any free cpu cycles the project gets).

At it's simplest, Boinc has two methods to determine what WU to crunch.
#1 -- Download order (w/shuffles between projects each hour).
#2 -- Deadline order -- signified with a red bang (interupts shuffles, downloads, etc).
Users don't get to select which mode to operate in. Boinc makes that determination based on the variables it has collected over time (although we can certainly force the later by being overly greedy on work buffers).

I'm sorry, but I don't believe your "work around #28" is a good idea.

BOINC works on the assumption that the estimates are low.

The reason is simple.

If you assume they're high, and to compensate you don't go into "priority" mode as a result, you'll miss the deadline.

If you assume that they're accurate, and the actual time is high, you'll miss the deadline.

If you assume that they're low, and you put extra work on that WU early as a result, you'll always hit the deadline without fear.

Setting the clock back a month (or manually adjusting the DCF smaller, same thing) bypasses the safeties that make sure work is delivered ahead of deadlines.

Your observation that people think that "priority" work is a horrible problem that must be fixed is a tough one, and I struggle with that in my own projects.

You need something that says "I'm doing this one now" without some variation of "because it might be horribly, dangerously late!"

It's a no-win situation. The best solution may be to hide the work unit list and the whole scheduling process entirely.

---

I'm sorry, but I don't believe your "work around #28" is a good idea.

Awww, you missed the word 'Horrible.' I did skip mentioning 'Super Horrible Evil Bad Work-around #29" tho... which would be to set your clock forward 30 days .... which actually solves the scheduling crisis by triggering a mass abort.

I'm sorry, but I don't believe your "work around #28" is a good idea.

Awww, you missed the word 'Horrible.' I did skip mentioning 'Super Horrible Evil Bad Work-around #29" tho... which would be to set your clock forward 30 days .... which actually solves the scheduling crisis by triggering a mass abort.

.... except the average reader here may think your use of "horrible" means "it's horrible that we have to do this" instead of "this is really a horrible idea that doesn't fix anything."

---

.... except the average reader here

Point taken.

** EVERYBODY ** Never joke around with your clock, nothing good will come of it, pls leave it sync'd to a reliable time source.

After finishing this AP WU your BOINC will learn how fast your CPU/APapp combination is and give more reasonable estimate in the future (e.g. 40 h).

.

Yes of course this is the first AP WU done on this system, which is why it's so wildly out !

Thanks for that !

Happy now, sort of, still don't see why so many GPU WUs

---