I am not sure if this sounds silly or not. I think I am correct in that the credits are based on the trickles received by the server for each task. How feasible would it be for there to be a script downloaded to the host computer with each model that then calculates the credit based on the trickles sent to the server. This could then be uploaded to the database at a later date say with the zip files.

I think I am correct in that the credits are based on the trickles received by the server for each task.

Yes, that is the case.

How feasible would it be for there to be a script downloaded to the host computer with each model that then calculates the credit based on the trickles sent to the server. This could then be uploaded to the database at a later date say with the zip files.

I have no idea of whether BOINC has the ability to run a script to do this or not. My guess is it probably does. I don't know how easy it would be to guard against credit fraud. - Not a major issue at the moment but if at some point this project is whitelisted again for BOINC Gridcoin mining then any vulnerability to this would likely lose the project its whitelisted status pretty quickly.

I was thinking more in terms of a script in each CPDN model rather than BOINC in general. Something that perhaps could automatically attach the credits to the zip or stderr files - but maybe that would be too difficult.

Credit script has been run again and now also uncompleted tasks with trickles were awarded with credit.

---

Credit script has been run again and now also uncompleted tasks with trickles were awarded with credit.

Lack of Linux tasks means I have to look carefully at my average credit going down to see if there has been a change.

Edit: But good news, I just hope the daily script will be working soon. - That could mean a whole lot of redundant threads here :)

Latest update on the credit situation. Not sure how many weeks will be needed to check all is working as it should. I would guess three to four but that may be just me picking a number out of thin air.

Hi All,

A short update on the CPDN credit calculation:

So the current plan with this is to run the current credit calculation in parallel to a new credit calculation over a number of weeks.

This will enable a like-for-like comparison to be made with the current and new credit calculations of the credit and RAC values after running for a number of weeks. This will not effect the credits that volunteers see, volunteers will still see the results from the current credit calculation.

The current credit calculation will run every Saturday at 00:00, and the new credit calculation will run: Tuesday, Wednesday, Thursday and Friday.

Best regards,

Andy

The result of the latest credit run isn't shown in Boincstats, so it seems export doesn't work.

I finished a task at 2 am UTC today and the task already shows the credit. But it looks like it has not yet been added to my total credit, but I'm not 100% sure what my total credit was yesterday. Does anybody else see this kind of behavior?

---

Does anybody else see this kind of behavior?

Unable to diagnose anything from my own account till some more Linux work becomes available however I wonder if the swift update of the credit for the task is from the new script which is probably not publishing to your account which will mean waiting till the weekend until debugging complete on new script.

The result of the latest credit run isn't shown in Boincstats, so it seems export doesn't work.

It could be that the export part is still to be handled on the weekend run.

---

The result of the latest credit run isn't shown in Boincstats, so it seems export doesn't work.

It could be that the export part is still to be handled on the weekend run.

If only we were told what the calculation method will be, we wouldn't need to guess :)

"To comply with the Data Protection Act 1998, we are required to only keep personal data for as long as it is absolutely necessary."

Nineteen years on it's a bit of a stretch to describe the DPA as a new law.

One of the points of the legislation of to make sure that data processors do not hold onto personal data long after it has ceased serving any purpose.

Deleting accounts after 3 years of inactivity ignores the fact (rather obvious from the posts of others) that the retained data still serves clear purposes.

It lets volunteers resume their efforts after a break without having to start again at the beginning. And it means that even if you move onto other projects and never return that the credits you've amassed for CPDN remain a permanent part of your Boinc tally. This is how Boinc works!

The DPA is supposed to protect the interests of data subjects (that's us). There is nothing in it which requires or justifies trashing data that the vast majority of would prefer you retain and which allows us to keep our Boinc history complete.

---

The Scottish Boinc Team

This thread has been running for three months. It is interesting to note that in that time we have not had any input from an Administrator. It makes me think that perhaps we do not have one.

Is this an oversight? Not appointing an Administrator to the forum whose words would clarify the official policy of this project. The lack of such appointment as exist in all other BOINC project suggests to me that we as volunteer users are unimportant to this project.

Despite contradiction by some,credit is an important aspect to us users. You have not been able to fix the problem in three months and indeed made the problem worse by declaring that under certain circumstances you will delete all our accumulated credits. Is this the way to thank us for helping you? No other BOINC project UK or otherwise have ever treated us this way.. Shame on you.

The note above that the Credit was granted but that it does not show on external Stat sites is being overlooked.

On Climate Prediction the credit script was successfully run and credit granted. The fact that it has not been successfully exported is a 2nd issue that no one has responded to.

Thanks
Bill F

---

In October 1969 I took an oath to support and defend the Constitution of the United States against all enemies, foreign and domestic;
There was no expiration date.

Credits still seem broken. There's an additional reason why credits are important to me, and that's because I'm on a team. Therefore there is a sense of duty to my teammates to do my best in the various projects in which we participate, of which Climate Prediction is one. A very worthy one, I might add, so it's with great ambivalence that I have had to cut down greatly on the amount of work I'm doing for the project, yet not cutting it off completely. I do hope this problem eventually gets addressed, it's my wish to divert more resources to this project on a permanent basis.

Email sent to project list. I don't know if the problem is the url having changed again or the current script not updating the page the external sites look at. (Or a third option I know nothing about!).

I will report back when I see an answer though am busy this week so it may not be till next week even if I get a reply quickly.

Hopefully this will be sorted soon.

Thanks for this. Andy would normally deal with this and is away for the next few weeks. Mamun will be in later in the week so I will take a look with him then and see whether we can see what is going on.

Credit updated when I looked this morning. Can someone who looks at these things tell me if it has been picked up by external sites yet? thanks.

Credit updated when I looked this morning. Can someone who looks at these things tell me if it has been picked up by external sites yet? thanks.

Nothing has appeared yet (at Free-DC or Formula Boinc) it might need more time but the usual place for collecting stats is still listing files not updated since November...

https://www.cpdn.org/cpdnboinc/stats/

...Can someone who looks at these things tell me if it has been picked up by external sites yet? thanks.

Not yet at BOINCstats; however, I don't think they pick up any available update until later in the day. That also assumes they are looking in the right directory for the export (which has been an issue in the past).

---