Calling people a loser, and telling them to "sign off" the project? Yeah, you're really all about the cause.

Guessing you were a legacy at Carleton - I always knew those of us from the U of M have more class.

Perhaps the tone could be changed before the moderators have to step in.

No doubt there is an element of frustration creeping in. A simple task neglected: how so? It's a reasonable question.

The moderators have done what they can to communicate all our various frustrations at this deficiency and others. I'm sorry to say that absent of any communication from the project itself then people will have to make their own calculations as to whether to participate or not. People are different and their sums will add up differently - to require a particular result is to suppose that everyone is the same. If you believe that then dealing with a credit hiatus is the least of your problems.

I don�t know if my eyes are playing tricks on me or what, but, it looks like the credit script ran.

---

I don�t know if my eyes are playing tricks on me or what, but, it looks like the credit script ran.

May have started but didn't get as far as my machine's stats. :(

Mind you, more work for when my current tasks finish in a few days time is more important to me than exactly when my credit gets updated. I know it will happen at some point.

For what it's worth, no credits have been sent to any of my three machines since June 3. And one machine finished a task a couple of days ago, apparently successfully, and this site shows 0 credits granted.

Hopefully it will all come out in the wash sooner than later . . .

---

No credit for work already accomplished means I will not work for this site.

---

How sad.

Issues associated with June maintenance are well described on these boards, as are numerous comments by moderators and other participants that credits always catch up.

---

"We have met the enemy and he is us." -- Pogo
Greetings from coastal Washington state, the scenic US Pacific Northwest.

Issues associated with June maintenance are well described on these boards . . .

Not everyone has the time to read every bloody post . . .

---

It was in News and Announcements, which is near the top of this section.
And for years we have been telling people, if they subscribe to it they'll get an email whenever there's a new post there.

Just a thought... would it be possible to put a message regarding credit updates on users' main account page or somewhere they can't miss it? I suspect a lot of people are signing up for CPDN just like they do with other projects without being aware that there is going to be a long delay in getting credits. Most people aren't going to search through forum messages to see what's going on and I know for a fact that some have given up on this project because they think it's "broken". I came to the forum and learned what's really going on but plenty of people won't bother doing that or won't even think of it as an option - they'll just give up. The stats for this project do seem to indicate that it has an unusually high rate of people dropping out.

I'm sticking with it because I think it's such a great project but I have to admit that I'm still scaling down my contributions until I can be sure that it's actually going to mean something. Unfortunately credits are the only "proof" (using the term very loosely) that it's working. I say again, for most of us it's not about competing for credits, it's about getting feedback that our work is being received and processed.

All the best with your ongoing efforts to make CPDN work well. Your work is very much appreciated. FWIW I'll do my best to keep people I know interested and supportive.

[quote]Just a thought... I suspect a lot of people are signing up for CPDN just like they do with other projects without being aware that there is going to be a long delay in getting credits. [quote]

I think the main reason for the high drop our rate is the length of the WU�s. For someone used to WU�s from other projects that can be completed in a few hours the run time of our WU�s comes as a shock. I have seen several postings on this site from shocked newbies asking if the estimated run time of several hundred or over a thousand hours can be right.

---

Just a thought... I suspect a lot of people are signing up for CPDN just like they do with other projects without being aware that there is going to be a long delay in getting credits.

I think the main reason for the high drop our rate is the length of the WU�s. For someone used to WU�s from other projects that can be completed in a few hours the run time of our WU�s comes as a shock. I have seen several postings on this site from shocked newbies asking if the estimated run time of several hundred or over a thousand hours can be right.

You get the same question on other projects, asking if a runtime of a few hundred hours can be right (especially if it over-runs the project's typical deadline - usually one or two weeks).

Usually, BOINC has vastly over-estimated the runtime for a newly-attached host, and they can be reassured that it's nothing to be worried about. It must come as more of a shock here, to be told that it's true...

I joined this project back in the days of the 160 year Hadcm3 models. Added to that was that I was running a 1.2 GHz, single core machine with 256 KB of RAM. The running time was over 3300 hours. Running about 20 hours a day they took 7 or 8 months to finish just one model.

---

Hi Chaps and Chapesses,

Last week our BOINC server suffered a corrupted hard drive and had to be restored from a backup. This meant that various fixes that had been put in place during the 'at-risk' period we have had for the last three weeks were undone - and one of these was a patch to allow the credit scripts to run correctly on our servers.

CPDN uses a custom credit generation script which I have spent today fixing.

The script is running, but given the age of CPDN and the large number of users, it takes several hours to complete.

I am hopeful that the script will complete successfully this time, which means that you should get your credits in a few hours (it is currently 5 pm BST).

Sorry for the inconvenience.

Jonathan
CPDN Sys-Admin

Big Smile! :)

Credits are flowing

Thanks for your hard work

---

Admin Jonathan Miller wrote:

I am hopeful that the script will complete successfully this time...

Yes, indeed. Everything looks good from my end, as best I can tell. Thanks for the update, Jonathan, and keep up the good work.

Cheers,

MarkR

---

Credits are flowing

And so is work, a few thousand .eu tasks seem to have been able to squeeze down the pipe once it was unblocked.

Thanks Jonathan! Exciting to see the credits going again. Hope everything is coming together well at your end.

Also thanks to those who replied to my last message. Good point about people probably dropping out due to the length of time the WUs take to process. I've actually realized that I've only got a couple of computers that I can run this project on - I don't think most of my computers would be able to finish WUs before the deadlines. This isn't the only project with that problem of course but it must be frustrating for some people.

Anyway, I'm just glad I can be part of this project. Look forward to seeing how it progresses.

I've actually realized that I've only got a couple of computers that I can run this project on - I don't think most of my computers would be able to finish WUs before the deadlines.

No, you're fine. CPDN accepts work that finishes after deadline.

Deadlines are a BOINC feature that CPDN uses for two things:-

• To re-issue work to another computer, if no results have come back yet. (Unfortunately many computers accept tasks and then "go dark".)
  
• As a crude prioritisation mechanism. For instance, the RAPID-RAPIT/CHAAOS researchers wanted to get some results in a hurry last year (I'm guessing for IPCC AR5--but I'm not confident about that), so those units have a very short deadline. But I understand that they are still taking and using results that come in after deadline.
  

So don't worry about the deadlines. Keep crunching!