Hi Dave,

Okay thank you very much for this. There was an error in the run, I have corrected it and have set to run at 11pm (UK time) today.

Best wishes,

Andy

Edit: Can't remember how long the script takes to run but if no change by this evening will message Andy again.

Yes, I've written to Andy (who was busy with the BOINC workshop yesterday), and requested a specific chunk of data which will help us localise where the problems start. Once I receive that, I can work out whether we need to search forwards or back to the source of the trouble.

It'll take several steps, and I won't keep up a running commentary, but I'll let you know when we make any significant change that may be observable in your own accounts.

Richard, thanks. This all looks promising, bottom line though is that this conversation needs to be had with Andy/CPDN. No-one on the forums will be able to progress this. There's a tech meeting Monday. I will show them and ask if you can help out. If you have any other input send me a PM.

bullschuck wrote:

Back to the original question for this thread. Any news on awarding credit for completed HADCM3 tasks?
Further news on proposed Mac Intel IFS tasks would be appreciated as well.
Thanks!

Still nothing?

I got a reply back from CPDN admin who checked the tasks for your account. He says: "Beyond a certain date (mid December) we have no trickles for these 14 successful results. Credit on the main site is currently awarded by trickles." So that's the reason, though why no trickles they can't tell, maybe network issues? I'm not very familiar with the trickle mechanism maybe the moderators can jump in on this one.

Hope that's useful.

That's not very useful. There's something broken at cdpn and it's not my network connection.

Sorry, I didn't mean network issues at your end. I was referring to the issues CPDN had around this time. Though my understanding was that only affected the upload server, whereas trickles go to the university site I believe.

bullschuck wrote:

Back to the original question for this thread. Any news on awarding credit for completed HADCM3 tasks?
Further news on proposed Mac Intel IFS tasks would be appreciated as well.
Thanks!

Still nothing?

I got a reply back from CPDN admin who checked the tasks for your account. He says: "Beyond a certain date (mid December) we have no trickles for these 14 successful results. Credit on the main site is currently awarded by trickles." So that's the reason, though why no trickles they can't tell, maybe network issues? I'm not very familiar with the trickle mechanism maybe the moderators can jump in on this one.

Hope that's useful.

I can bring this up at the next CPDN tech meeting. Is it just your HadCM3 tasks? I can't see your computers so I can't get the task ids you've run.

I know they have had problems with the credit script a while ago. I'm not sure if that's the reason. I'll see if I can get an answer for you.

As for the mac Intel OpenIFS tasks, I'm working on this week. It'll go to testing first though before appearing in production.

Back to the original question for this thread. Any news on awarding credit for completed HADCM3 tasks?

Further news on proposed Mac Intel IFS tasks would be appreciated as well.

Thanks!

On the CPDN pages, I have credit for all but the latest task I have run up to 29 January.
I also have credit on the signature box that will appear below.

$ ping -c 5 upload11.cpdn.org
PING upload11.cpdn.org (192.171.169.187) 56(84) bytes of data.

--- upload11.cpdn.org ping statistics ---
5 packets transmitted, 0 received, 100% packet loss, time 4116ms
$ ping -c 5 upload11.cpdn.org
PING upload11.cpdn.org (192.171.169.187) 56(84) bytes of data.

--- upload11.cpdn.org ping statistics ---
5 packets transmitted, 0 received, 100% packet loss, time 4116ms

Anyone else having issues getting the results to upload? I'm just getting timeouts.

See this post in OpenIFS discussion thread.

I have sent an email to Andy.

Edit: Andy says no issues with any of the servers this morning and thinks it may just be the large number of people contacting the servers for work.

If the problem persists do post again ideally with http debug flag set (The one Richard suggested.)