Joined: 6 Aug 04
I have two of these running on Linux boxes now and one of them is showing it will take 4,648 hours to complete with a deadline of 26 Feb 2007.
After 78 hours it is showing completed 1.73%.
My concern is that as I don\'t run this box 24/7 I think the likelihood of me completing this is remote. I don\'t want to run this box just to complete clim pred project as that seems to be just adding to global warming.
Is there any point in continuing this in as much as it is unlikly it will be completed in the alloted time?
model hadcm3lb 5.08
Joined: 6 Aug 04
The results will be used anyway. As far as I know that date is for priority setting, but I am probably wrong and will get pounced on because of it :)
I generally just let my Linux boxes run.
Joined: 5 Sep 04
You\'re close Dave.
The deadline is included because it\'s a necessary part of other projects, so something had to be put into that spot in the software.
Every 10 years completed is valuable. And if you can get to the half way point, that\'ll mean that you\'ve completed the hindcast part. Of even more value.
And BOINC V5.* isn\'t very good at estimating completion times for very long projects, because the method was changed to \'do averages\' over several models. Not a good method with climate models.
Try DIY, using the real world time that it takes to complete 1 model year, then multiply by 160. A better estimate will be to use 10 model years when you get that far.
Joined: 25 Nov 05
I also found that the estimation is way off, mine is at 4495 hours at the moment.
Instead I use the percentage and the used CPU time to compute the estimated #hours as follows:
456.5 hours, 13.46% currently done for my model means that total computation time will be 456.5*100/13.46 = 3391.5 hours CPU time.
This number is fairly constant, it is always around 3300 hours.
So after 3391.5-456.5 CPU hours = 2935 CPU hours = 122 CPU days the model will have finished.
Since I run climateprediction for 80% of the time that is
122/0.8 = 152 real days = about 5 months.