Why do people keep stating the obvious? We know the work is not continuous, it comes in regular batches. There is nothing wrong. This is just a friendly heads up to the admin if they happen to see it so they can load up more data, which is a good thing.

---

Why did you copy previous post almost word to word?

Why did you copy previous post almost word to word?

He messed up the quoting. The last sentence was his.

people don't understand satire/sarcasm. i didn't mess up any quoting and was never trying to quote. I merely replied in the same manner for greater impact.

---

Now this went too far. Mr P Hucker, as I said I'll not remind second time that any kind of bad language will not be tolerated. Especially if someone is insultс another members of this project no matter how bad it is performed.

Keep it that way ;)

Cheers!

---

“The good thing about science is that it's true whether or not you believe in it.” ― Neil deGrasse Tyson

out of work again

---

A proud member of the OFA (Old Farts Association)

out of work again

---

A proud member of the OFA (Old Farts Association)

Out of work again

---

Why agree to being the Sprint project for BOINC Games and then run out of work?

Stupidity.

Why agree to being the Sprint project for BOINC Games and then run out of work?...

They probably didn't see any downside to simply agreeing, but they could be excluded from other future Sprints based on their performance during this one.

Looking at kiska past 6 months tasks ready to send, the supply of work is like a saw-tooth. https://grafana.kiska.pw/d/boinc/boinc?orgId=1&var-project=Asteroids@Home&from=now-6M&to=now

Maybe the admin or someone here can shed a light on the work generation. Maybe like TN-Grid and Denis?

Hopefully, new tasks will become available soon...

Yes, the work availability is very cyclical and predictable

BG should input the task availability cycle frequency into their selection criteria since they appear to only start new Sprints when it coincides with some international sporting contest.

Best to schedule sprints when projects have just refilled the RTS cache.

In this current situation, with the Sprint starting at the bottom of the Asteroids work availability schedule, it should have been excluded from the pool of choices.

---

A proud member of the OFA (Old Farts Association)

The important question for me is: What is the trigger to generate new work?
After x days?
After x% of the previous batch is sent back?
If someone has time to start the process?

Why agree to being the Sprint project for BOINC Games and then run out of work?

Stupidity.

To make the sprint more interesting. Unknown finish line.

You can see asteroids@home task availability graphs here.
https://grafana.kiska.pw/d/boinc/boinc?orgId=1&var-project=Asteroids@Home&from=now-30d&to=now

The "per app results" on "Asteroids@Home period_search_unsent" is interesting.

Looks like we're finishing them just before the next batch comes in. Looks good to me, we're keeping up with the workload. In a lot of projects there's the feeling of a massive backlog.

OUT OF WORK again, no new tasks

---

Are you sure about that?