But you can get farely close by setting resource share to 1 for climateprediction and 1000 for seti.
That would make climate prediction run for 1 hour every 40 days or so unless seti runs out of work...
It seems that a large percentage of people want to have one main project and a backup project for when there is no work from the main project. Hopefully the Boinc team will add the ability to set projects as backups. I posted in the ‘Wish List’ a couple of days ago about backup projects.
Personally I wouldn’t set CPDN to run only 1 hour every 40 days as the work units take hundreds of hours to run. They may have a report deadline of about a year (which sounds a lot) but unless your machine is on 24/7 and Seti has a lot of down time you are not likely to finish the work unit. Projects with fairly small work units like Seti that can be done in less than a couple of days are more suitable as backup projects.
> no not really....
> But you can get farely close by setting resource share to 1 for
> climateprediction and 1000 for seti.
> That would make climate prediction run for 1 hour every 40 days or so unless
> seti runs out of work...
> Close enough I'd say
> happy crunching
If you use those number you should stay away from CPDN, because depending on your cpu speed, you would not meet the 1 year deadline and would just screw the project up............... Exampke p4 3.0 about 400 hrs to crunch, useing your 40 to 1 that would = 1600 days on a 3.0 cpu.....plus the hrs that the other project would be crunching, I am lousy at math so some one who is good at maath can figure it out....