I downloaded an Astropulse wu today, either (^%$# has frozen over or the man upstairs granted me one of the items on my bucket list. Haven't seen one of these since the moon turned blue.

---

I don't buy computers, I build them!!

Great luck for you. I've been watching the "ready to send" queue, and I was starting to think they just were not being sent to the feeder (which supplies us with WUs when you request work). I guess that disproves my theory.

---

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

Hang in there, you might get one yet. BTW, the moon turned blue back in 2000.

---

I don't buy computers, I build them!!

Hang in there, you might get one yet. BTW, the moon turned blue back in 2000.

The "blue moon" occurs as the 2nd full moon in a calendar month. It has occured since 2000.

---

Janice

If your unlucky enough to be in the vacinity of a large forest fire the gases given off can often give the moon a slightly blue appearance.

---

Full moon schedule. The last blue moon occurred Dec 31 2009 and the next one will be on Aug 31 2012.

---

Boinc V7.2.42
Win7 i5 3.33G 4GB, GTX470

Hang in there, you might get one yet. BTW, the moon turned blue back in 2000.

The "blue moon" occurs as the 2nd full moon in a calendar month. It has occured since 2000.

Actually, I was referring to the original definition of BLUE MOON ---- one that occurs as the third full moon in a season of four full moons, as described in the Farmer's Almanac. There have been only four since 2000, the last being 20 May, 2008 and then next on 21 Nov. of this year. Most years do not have them. In the first 20 years of this century there will only be eight.

---

I don't buy computers, I build them!!

Just figured I would follow up with the original topic here..

I have managed to procure about two days (of the requested 7) of AP tasks. After many many many "project has no jobs" messages, and then an equal amount of "you don't have an application for..." messages, I managed to get some APs, and in fact.. twice, I got three in one request. I didn't notice until just a few minutes ago when I was looking at my tasks list here and saw sequential WU numbers, then the sent time was the same. That's awesome.

---

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

Boincmgr frequently, but not always, overestimates my wu's time to complete value. Once the wu starts it quickly falls back to the nominal 90m number. This behavior started with changes of the server software a week or two ago. It is a problem because it influences the number of wu's I get, which in turn is currently being scrambled by the extended shutdowns and more user unfriendly changes done by Berkeley.

I know this topic was bantered about on the boards a while back. What was the conclusion? Am I forced to have a lame completion time estimate forever, or is there a solution for me?

I don't know about newer BOINC builds and such, but with 6.2.19, my DCF doesn't seem to be hijacked by the server like I have also read. My DCF was up near 1.000 when AP was more difficult than usual to get, so I let MB run for a few days. When I went back to AP-only, the BOINC estimate was ~180h when it really is only ~24.5, so with a 4-day cache, BOINC stopped asking for work when I had three APs to keep my four cores busy.

Now that I've run through about a dozen APs, the estimate is down to 46 hours, so I have a lot more APs in the cache now than I did last weekend. Still roulette for getting an AP issued when requesting work. Managed to pick up a few more overnight and a few minutes ago picked up...9 of them. Getting close to having my cache filled for the current ETA. Hopefully it will get closer to 30 soon while the gettin' is good.

[edit: nevermind. as I was typing this post, I got two more WUs and now I'm being told I have too many tasks in progress. Oh well.]

---

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