picked up 10 so far I can't expect any more today, due to 1 laptop..

Is that for our day or UTC time/date?

Cheers.

Unless another file comes along I've racked up 47 for the 19th Apr UTC.

Cheers.

I don't believe it...….151 for the 19th.

---

SETI@home classic workunits 4,019
SETI@home classic CPU time 34,348 hours

Man, this is almost like the old days when you could have a full 10-day cache of nothing but these. It's been a great run for like a week now.

Can you tell when AP has been available to me?

---

Linux laptop:
record uptime: 1511d 20h 19m (ended due to the power brick giving-up)

Unless another file gets loaded I've got 17 for the 20th Apr UTC.

Cheers.

Managed 25 for the 20th

---

SETI@home classic workunits 4,019
SETI@home classic CPU time 34,348 hours

My 2 rigs randomly picked up 16 for the 21st Apr UTC.

Cheers.

12 for the 21st her....and none so far today.

---

SETI@home classic workunits 4,019
SETI@home classic CPU time 34,348 hours

I got 8 resends for the 22nd Apr UTC and an old rig that I fired up here late last night managed to catch 1 of them.

Cheers.

2 resends for me.

---

SETI@home classic workunits 4,019
SETI@home classic CPU time 34,348 hours

what does it mean when results returned and awaiting validation is larger than results out in the field??

is that a bunch of inconclusive results that need a third try??

what does it mean when results returned and awaiting validation is larger than results out in the field??

is that a bunch of inconclusive results that need a third try??

Probably a bit of that, but also probably just a lot of slower hosts that haven't gotten around to crunching and returning yet.

I notice for me, since I'm all on CPU, I almost always get paired up with GPUs who turn the results around within 2-6 hours, but for me, it'll be a few days before crunching even starts on some of those, and then will take 8-12 hours to crunch them.

---

Linux laptop:
record uptime: 1511d 20h 19m (ended due to the power brick giving-up)

Just 1 resend here for the 23rd Apr UTC.

Cheers.

what does it mean when results returned and awaiting validation is larger than results out in the field??

is that a bunch of inconclusive results that need a third try??

Generally the faster a machine is, the more Validation pendings there will be. The slower the machine, the less there will be.
An extremely fast machine will always be waiting on other, not so fast systems, to return their work so it can be Validated, and Credit granted.

eg Keith Myers system.
Average turnaround time 0.15 days
500 In progress, 5103 Validation pending.

The other end of the scale, a laptop,
Average turnaround time 8.96 days
200 In progress, 11 Validation pending.

---

Grant
Darwin NT

Very true

Another Arecibo file has popped up, and it's being split for AP.

---

Grant
Darwin NT

26 arrived here for the 34th Apr UTC.

Cheers.

Bummer none for me the past few days, but for some reason I've still got 16 that have arrived between the 15th and 20th that my queue hasn't gotten around to processing yet.

Other than "babysitting" the queue by suspending non-AP tasks, is there some way to help encourage BOINC to process the AP tasks sooner?

It seems to have a strong bias for processing the non-AP tasks first as I can crack through 200-250+ of those a day (or all of the non-AP GPU queue 2-3 times) yet the AP tasks sometimes just sit "waiting" for their turn. I'd think perhaps the tasks with sooner deadlines would be processed first, but that never seems to be the case either. For example out of my tower's queue of 200 work units total (100 CPU/100 GPU) the earliest deadline units are due 14th of May, latest 25th of June, and the current ones running are due: 17th of June (2x GPU non-AP units) and 15th of June (3x CPU non-AP units).

---

Bummer none for me the past few days, but for some reason I've still got 16 that have arrived between the 15th and 20th that my queue hasn't gotten around to processing yet. Other than "babysitting" the queue by suspending non-AP tasks, is there some way to help encourage BOINC to process the AP tasks sooner? It seems to have a strong bias for processing the non-AP tasks first as I can crack through 200-250+ of those a day yet the AP tasks sometimes just sit "waiting" for their turn. I'd think perhaps the tasks with sooner deadlines would be processed first, but that never seems to be the case either. For example out of my tower's queue of 200 work units total (100 CPU/100 GPU) the earliest deadline units are due 14th of May, latest 25th of June, and the current ones running are due: 17th of June (2x GPU non-AP units) and 15th of June (3x CPU non-AP units).

BOINC always makes sure that work is done on a FIFO basis regarding tasks unless deadlines are forced to come into play (and nothing other than personal intervention will override that).

Cheers.

BOINC always makes sure that work is done on a FIFO basis regarding tasks unless deadlines are forced to come into play (and nothing other than personal intervention will override that).

Cheers.

Ha - taking another look at my AP page... I've got to look at the correct column. I have actually gotten a few more units the past few days. Currently it's just past 04:15 local time. Guess it's time to go to bed.

---