just got my 10,012,024 back, Woo and Hoo :-)

Hooray! .. and my 120,000. Good Job team! Thanks for the hard work.

Looks like its time to fill up our cache's before all those part timers appear:-)

---

Kevin

just got my 10,012,024 back, Woo and Hoo :-)

I'm pleased to see that you are content with the result.

Credit problems occur. They always trigger an uproar ... They are are always resolved -- though perhaps not as quickly as participants want. If one considers operational priorities and short staff, one can infer reasons for one's delayed expectations.

By the way, your credits were apparently heavily weighted in early days of CPDN's boinc era. Hence your huge percentage jump. (You beat my high-jump.)

For what's it's worth, most of the people posting in defense of patience are what we used to call Beta testers -- for which, in recent years, NO CREDIT is awarded. They are dedicated to the advancement of Climate Science -- period. (Please don't think I'm here giving myself a pat on the back -- I'm much too old for such trivialities.)

Hang in there, Helix!

Best regards.

---

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

Some things never change... death, taxes, and CPDN credit problems.

I've been away from the project for over a year and returning I see that there's still endless discussion about CPDN credits. In fact, it still the most active - it's at the top of the non-sticky threads list, where it always has been.

I have participated in many different projects, and this is the only one that I have ever experienced credit issues with.

The other projects' credit systems just work.

For me, personally, I don't care much about whether I get CPDN credits or not.

But it would be nice if this can be fixed, once and for all. There's too much time and energy being wasted in this never-ending squabble.

Credits have increased a good bit, and recent avg too. Of course hard to know if the figures are "correct", but at least in the right direction and that's encouraging.

One thing is still puzzling. The "Your Computers" page shows my Linux machine twice, one listing is is for Linux OS, the other Windows. This makes sense insofar as it is a Linux box running BOINC under Wine. However the only BOINC client running is the Windows/Wine version. I haven't had the Linux BOINC client online since December 2015. It's still showing avg credit of 209.94, which is slightly lower than yesterday's reported average.

I'd attributed this misrepresentation to the recent/current server crash and maybe that's still affecting the report. It leaves a question whether the other credits are accurate. BTW the Linux/Windows "computers" have separate IDs: Windows == 1389186, Linux == 1373243. Should add that prior to the crash the Linux side wasn't showing up at all in the "active" list.

Anyway glad to see there's evidence of progress, maybe it will just take more time to completely straighten things out.

I have participated in many different projects, and this is the only one that I have ever experienced credit issues with.

The other projects' credit systems just work.

Other projects use boinc's credit scheme. This one, thanks to its longer tasks, does not --> because of its longer tasks (much shorter now than they used to be).

Other projects award credit if and only if your result is confirmed by another computer's result -- AFTER a successful completion. Not so here. Credit is awarded as a task progresses and you get to keep credit whether or not the task completes successfully. Such a deal!

Credits are recomputed, daily (normally), from the beginning. It's expensive to run and, in the end, has always put things together as they should be.

---

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

MossyRock

The reason for the problem this time, is the server failure, and it's replacement by the slave server. This resulted in the loss of pre-2011 archived credits. Which are now back.
This is what has been talked about for the past 3 weeks.

And if you do go further down this thread to read about it, you'll find cake here and there. :)

jrapdx

That's odd about your computers. My pure Linux machines, which underwent Wine surgery in January, are only listed as being older than 30 days.
The 2 listed as "current", are both listed as Windows XP Pro, which is as it should be.

And the Top participants list appears to be back to normal. Plus some extra is listed there for me, which is probably about right for the models that I finished during the outage.

A tribute to all who contributed to the return of credits. Good work.

Les, thanks for all your efforts here in the forum. Have you ever considered opening a pre-school center? ;-)

I see my credits are back.
Thanks!

Heyyyooooooooooooooo! Its all back online! Big ups to the hard workers out there!

Crunch on

Keith

Have you ever considered opening a pre-school center? ;-)

Luckily, I'm too old for that.
I just listen to the screaming in shopping centres. (What you would call a mall.)
:)

That's odd about your computers. My pure Linux machines, which underwent Wine surgery in January, are only listed as being older than 30 days.

Certainly seems odd to me too. Prior to the crash the Linux OS had indeed faded into the older than 30 days list. I had assumed the reappearance of the Linux side was the result of "reading old tapes" when things were messed up, but don't know what's going on now.

Curiously during the outage Wine BOINC/CPDN was running flawlessly, but today the system "froze" again requiring manual reboot. Didn't cause any tasks to fail, so that's a good thing. Still seems like something's flaky in this system but not yet been able to pin it down.

I'm almost afraid to ask this. Seems like folks are getting a mite testy.

Should I be looking at my BOINC Manager Statistics display for the wayward credits, or will they only be repaired in my account statistics in CPDN?

I ask because they do seem to be back in my CPDN account, but my local statistics are still short.

I've updated CPDN a couple of time this past few days, but still no joy.

Thanks for all your work.

---

Just clicked on the update button for CPDN on this machine and it is now showing the credits from the out period.

Will get around to checking my other boxen later today.

Hi Thund3rbird

Ask away, we need to know if there's any problems still lurking around somewhere.

I hadn't thought to look at BOINC Manager until you mentioned it, but both show something similar:
A fairly steep drop to the bottom, a horizontal section, and then a long shallow climb back to where it was before.

The data for this "Manager credit" comes from the project's server, every time the two talk.

(At this point, I had a lot more written down, but thought of something, had a look, and have changed it. :) )

Your computers haven't run anything since just before the crash, so my new guess is that your Manager missed it:
1) You completed some work and uploaded the results.
2) The crash occurred.
3) The problem was fixed.
4) Your computer contacted the server, and got the current situation. It then literally "connected the dots", and as you never got any "dots" during the crash period, you won't get to see the channel that's been excavated for the new road/railway/canal.

I'm confused, but heartened.
Getting the archived credit restored - good -
My boincmanager graphs on my hosts were fairly stable, then a drop, a low plateau, then an upswing another plateau.
But now another plateau --
Have the last 3 days trickles posted? Doesn't seem so for me.

Like Les posted, report problems, (Ignore flames)

Keep on crunching.

I really don't care much about credits as such, but when credit reporting is stable, it's one easy factor in my decision to replace (or not) one of my hosts (which I do every year or so)
I look at the box with lowest average credit as first candidate for upgrade. That doesnt work lately. (Partly because of using wine on linux, and VM's, etc) But I can work with "TS/sec" or other measures.

---

Hi Eirik

"Latest trickles" may just be the good old "Automatic Script Not Running" problem again.
Seeing it's currently daytime in the UK, I'll send an email to have that looked at.

OK, everyone put their ear plugs in, there's going to be screaming.

The scripts are currently planned to be run once per week, over the weekend. (The data they have to get through must be huge by now.)

Plans for a more frequent running are being discussed.

edit

Update:
Update to my previous email: credits are set to start calculating at 9am (UK time) on Saturdays. So sometime on Sunday morning volunteers should see their credit updated.