I have had a hard time getting any new tasks in the last day or so. Help is appreciated!

Yeah, me too, so it seems to be a general problem. There are People who reported the same in the general technical issues thread.

So there is no pProblem with your and my machine. Perhaps proteine research is finally done :-)

Yeah, me too, so it seems to be a general problem.

And no message from Admins

---

They might be working on a software update or smth. While waiting I started to crunch WCG cancer markers and folding@home.

---

They might be working on a software update or smth.

I don't think so. No new app in Ralph@Home.

While waiting I started to crunch WCG cancer markers and folding@home.

I turn my cores to Tn-Grid

---

I agree, a message from the admins would have been a good thing. That would have probably prevented dozens of crunchers having doubts about the own hardware and software setup.

Let's assume they are so busy to to solve the problem, there is no time to inform the users.

Meanwhile I switched to WCG Cancer markers, too. Obviously it seems not only to me to be the second best for unemployed cpu cores :-)

Meanwhile I switched to WCG Cancer markers, too.

That is one of my standards. But WCG/MIP is a close match to Rosetta, since it employs the Rosetta code in some fashion.
I have to limit MIP to only two at a time however (using an app_config.xml file) in order to prevent them from slowing down. It is apparently a cache limitation.

---

Unsent count = 0 for both Rosetta and Mini. See this @ Computing-> Server Status then scroll down.
Someone forgot to stoke the fire !!

How odd.
I'm seeing this:
Tasks ready to send
8079
But then, under the tasks by application heading, 0 for each and every application.
What gives?
And here I had just started crunching on this project again.
Oh well.

How odd.
I'm seeing this:
Tasks ready to send
8079
But then, under the tasks by application heading, 0 for each and every application.
What gives?
And here I had just started crunching on this project again.
Oh well.

It’s a long standing discrepancy in the database, work units counted into the system when they’re released and not counted out when they expire / are aborted / fail, possibly to do with orphaned work units. The discrepancy does change over time, not so long back it was 8086.

As a bug it’s minor and therefore of low priority for a fix as long as people are aware of it and know to look at the project counts for accurate figures.

I would point out that the first paragraph is an educated guess and that I am not part of the team but, honestly, I would not stress over it.

I agree, a message from the admins would have been a good thing. That would have probably prevented dozens of crunchers having doubts about the own hardware and software setup.

Let's assume they are so busy to to solve the problem, there is no time to inform the users.

You have to use your imagination and imagine what the admins are thinking.

You have to use your imagination and imagine what the admins are thinking.

They are thinking they have plenty of computer support and don't need to think anything about it.

---

How odd.
I'm seeing this:
Tasks ready to send
8079
But then, under the tasks by application heading, 0 for each and every application.
What gives?
And here I had just started crunching on this project again.
Oh well.

It's a cached number meaning it won't change if I download 20 or 200 workunits until the page gets refreshed.