I currently have two units running which have expired.
http://climateapps2.oerc.ox.ac.uk/cpdnboinc/workunit.php?wuid=8522433
http://climateapps2.oerc.ox.ac.uk/cpdnboinc/workunit.php?wuid=8552887

How long will these units be valid for ? Should I abort them or can the time be extended so I can complete them ?

The deadlines are not enforced, you can continue running them to your heart's content. The effect of the deadline is that another user will be given a copy of the same workunit.

---

I'm a volunteer and my views are my own.
News and Announcements and FAQ

Ok, thanks for the quick reply. I will run them to completion then.

Just for completeness, the tasks wont be accepted by the BOINC software without a completion date. Recently some CPDN tasks had a very short completion date that many computers didn't stand a chance of making. This was because of a deadline the researchers set and they wanted to get as many results back quickly to generate the next set of tasks as possible. They were even then still able to use later returns, just not for designing the next stage of the experiment.

Sorry that i didn't find anything better category to place this question but I just rejected two big global models because i wasn't sure how long it will take: After two hours of crunching i calculated from the used processor time and how much it had completed (which was about 0,035%) that it would take aproximately 6600 hours/wu. BUT: Remaining time in the boinc manager showed 595 hours from the very beginning and counted down steadily. Now which one could be right? I could try it if it was that smaller one but I just can't keep computer on and crunchin some 250 days from now on. Some time ago i got old computers going to recycling and fixed them little to do some 'boincin' but 1,86Ghz core2duo seems to be slightly slow for cpdn. Any chance to make it with smaller wu's? Deadline should be longer then , relatively.

Regards, o-pekka

Those particular work units tell lies. They falsely report the percentage completed. Long term this is not a problem but in the short term it can mess up estimates for other tasks and if you run more than one project mess up things like how long it spends on each project. Again a short term problem. With luck the next batch of these work units will have this problem resolved.