I have just started on CPDN and as far as I can see there are over 7000 hours to complete. As the experiment appears to have a report deadline next november surely my experiment is doomed not to finish?

Bit depressing that !

Hope I have misunderstood the information.

---

The estimate is often very inaccurate. It\'s based on the Boinc benchmarks, and for some reason your benchmarks are very low, hence the estimate will be for a long time. The most accurate way to tell is to look at the \'s/ts\' (seconds per timestamp) figure displayed on the \'show graphics\' screen (press \'Z\' followed by \'8\'). Multiply the s/ts figure by 4.1 million to get the overall estimate.

As it happens, the \'deadline\' is ignored, so it doesn\'t matter how long it takes.

---

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

your computer seems to be running a bit slow (8.9 seconds per timestep) considering it\'s a P4/3.2GHz (I have a P4/3.2GHz at home and it gets 2.1 seconds per timestep). I\'m not sure quite why it\'s so slow, but if it\'s running at 8.9 secs per timestep it could indeed take over a year to finish a complete 160 model-year run!

Given the extremely low benchmarks, and the much higher s/TS than expected, I wonder if thermal throttling is occurring.

I have just started on CPDN and as far as I can see there are over 7000 hours to complete. As the experiment appears to have a report deadline next november surely my experiment is doomed not to finish?

Bit depressing that !

Hope I have misunderstood the information.

James,

There certainly seems to be something odd about your PC speed - it should be going a lot quicker. I see a few things which are of concern:
Your processor speed benchmarks (look on your computer page) are very slow and suggest your machine is running a quarter of its proper speed. These should show numbers which are equivalent to your processor speed, so 3200 integer speed (or maybe 1600x2, since you have a dual core processor). But definitely not 600. This may mean someone has set up your computer wrong in the first place (an upgrade perhaps?), or there was a heavy application running when the benchmark was run. The suggestion about overheating is valid, but I think unlikely. You may want to suspend the project and run the PC benchmark tests manually (advanced options - run CPU benchmarks) to see whether this is just anomalous reporting, or check your BIOS settings on the PC.
Secondly, I see you are not running the latest version of the software. The latest version is 5.8.11. I think I saw in one of your error messages that you are running 5.4.1. Perhaps an undate may help.
A couple of the error messages from crashed models seem to point to files getting corrupted. I have no clue what this means, except to wonder whether the shutdown sequence is not happening properly. Perhaps the update will help.

Look at your hardware settings to start with, see whether you can get the CPU benchmarks up to the proper amount, and see what happens.

Good luck.

Anthony

I am running a P4 3.0 gighertz system with 2 gig of ram. I do run 2 tasks at the same time (seti an CPDN) the CPDN esimate to completion is 2935 hours adverage. Is this normal? That would be like 122+ days.

It\'s well within the deadline.

I am running a P4 3.0 gighertz system with 2 gig of ram. I do run 2 tasks at the same time (seti an CPDN) the CPDN esimate to completion is 2935 hours adverage. Is this normal? That would be like 122+ days.

It\'s well within the deadline.

Very normal. My P4 Xeon 2.8G HT does them in 132 days. This is shared with other projects, but hardly ever gets swapped out.

---