I get it that there was a host provider change, but it has been weeks. Cmon. Is it time to drop this project since it is really just dead and a cpu sink?

When the programmers at Oxford (I understand there are just the two of them) have some spare time from dealing with scientists sending out badly configured work units, resolving the problems that make a lot of one type of task crash on most windows boxes, another half dozen jobs I know about and probably a lot more I don't then they will run the credit script and at some point set it up so it is automated again.

Until then, most of us just carry on because we think the work itself is valuable.

CPDN gives less credit than some other projects/cpu cycle so it is not the one to go for if credit is a major factor in choosing projects anyway.

Not at all.

If you look at other threads that have discussed credits, you will see that Credits are applied, but only when they run the script manually.

The Science is valuable and you will get credit eventually.

Got enough credits now, Sprecher?
:)

Glad to report that as of this morning, everything is back to normal. The zillions have disappeared and the credits are as they should be.

Well, credits are just feedback indicating that the power and time you are committing are in fact being processed and used for a good purpose. Not having the project update tells me I should be devoting resources elsewhere. Most projects do eventually die. I guess I would like to know if this one is finishing up, or is this just a blip.

Of course, the credits are nice. I am on a team after all and feel inadequate what with my 53rd ranking or so, but that is beside the point.

Anyone else missing their graph data of cpdn credits? Since this credit stuff has been going on i haven't had the cpdn credit graph in boinc. My credits are back to normal but the graph is still missing.

My graph is still there but up until the weekend it had been flat since the previous blip. I now shows another strange blip and some normal activity since Andy ran the credit update script manually.

Same here. The graph has not changed since the first appearance of the zillions, that is to say the bottom line has not changed - the crazy peaks are there.

That crazy peak will be there for a month until it moves off the left hand side of the graph. The problem is that the peck is so high that it flattens the vertical scale of the graph so much that any new credits (measured in a few thousands) will be invisible.

The only way to fix this (other than to wait a month) is to either highlight CP in the �Projects� tab and click the �reset button� or to detach and reattach to the project. CAUTON: doing either of these things will wipe out any running or �waiting to run� CP WU�s on you machine.

---

However if you move to user average view you can see that things are changing.

That crazy peak will be there for a month until it moves off the left hand side of the graph. The problem is that the peck is so high that it flattens the vertical scale of the graph so much that any new credits (measured in a few thousands) will be invisible.

The only way to fix this (other than to wait a month) is to either highlight CP in the �Projects� tab and click the �reset button� or to detach and reattach to the project. CAUTON: doing either of these things will wipe out any running or �waiting to run� CP WU�s on you machine.

That would be the proverbial 'sledgehammer to crack a nut'.

Simpler, and less drastic:

Locate the file 'statistics_climateprediction.net.xml' in the root of your BOINC data folder.
Open it for editing with a plain-text editor like Notepad.
Find the <daily_statistics> block with the faulty value in it, and delete the entire block:

    <daily_statistics>
        <day>1413072000.000000</day>
        <user_total_credit>6873330.210698</user_total_credit>
        <user_expavg_credit>287.342895</user_expavg_credit>
        <host_total_credit>1981899.114743</host_total_credit>
        <host_expavg_credit>286.210316</host_expavg_credit>
    </daily_statistics>

I'll leave it to you to find out if you should have stopped BOINC first - that's one I don't know.