Hi,
I would like to see, that it is possible to pause a project when ever I like, so that an other is running.

Or better I want to see that I can choose manually the project that should run at this point of time.


<img border="0">
The whole is more then the sum of its particles.
Aristoteles
Best wishes from Berlin(52°35'N,13°23'O), Basti
S@h Berkeley's Staff Friends Club © member

You want to be able to choose not to crunch work that was downloaded, and then not get credit for it, delay everyone elses credit, and delay a scientific result? It would be much more useful to have a way of not downloading the work in the first place, as in a secondary project that would only DL work if the primary project had no work.

> You want to be able to choose not to crunch work that was downloaded, and then
> not get credit for it, delay everyone elses credit, and delay a scientific
> result? It would be much more useful to have a way of not downloading the
> work in the first place, as in a secondary project that would only DL work if
> the primary project had no work.
> <a>
I think he means that is a good idea to switch manualy between the projects. It would be great indeed


S@h Berkeley's Staff Friends Club ©

Well, if you didn't care to lose whatever work you did since the last task checkpoint, you could possibly manually kill the process for the task that you wished to suspend. That is what the BOINC client does anyway when you leave the default option for preemption set to NO for leaving task in virtual memory. I'm not sure whether the BOINC client would pick up the next task or restart that one, though. Could be worth a try...

> Well, if you didn't care to lose whatever work you did since the last task
> checkpoint, you could possibly manually kill the process for the task that you
> wished to suspend. That is what the BOINC client does anyway when you leave
> the default option for preemption set to NO for leaving task in virtual
> memory. I'm not sure whether the BOINC client would pick up the next task or
> restart that one, though. Could be worth a try...
>
I dont think it is a good idea to kill the task this way :)



S@h Berkeley's Staff Friends Club ©

> I think he means that is a good idea to switch manualy between the projects.
> It would be great indeed

No, John is right. This is not a good idea. The very things he mentions are what would happen if users had this control...

> No, John is right. This is not a good idea. The very things he mentions
> are what would happen if users had this control...
>
We have a "Report deadline" which is unconditional. Therefore the supposed delays are preliminarily expected



S@h Berkeley's Staff Friends Club ©

> > No, John is right. This is not a good idea. The very things he mentions
> > are what would happen if users had this control...
>
> We have a "Report deadline" which is unconditional. Therefore the supposed
> delays are preliminarily expected
>

I would like to add my voice to Basti's proposal- since BOINC switches between projects automatically (or at least mine does...) it would be nice to be able to switch to a different project than the one that's currently running. The resource share should not be affected, and the automatic switches should be the same.

While we are at it, my client switches projects every hour or so- is someone for some reason wants to control this variable it could be another nice feature.

_______________
Lior.K

> No, John is right. This is not a good idea. The very things he mentions
> are what would happen if users had this control...

If I have a project that only needs a few more minutes to finish, I would like to let it do so even if that means delaying another project that is days away from completing.

You are asking people to donate their time and resources, and you should try to make it easy to do so on their terms, after all they can just decide to stop participating.

I dislike the way credit is issued in general, and do not believe that that should be used as a justification here.

Loosing users and resources will have a bigger impact on the results.

Some of the projects such as ClimateChange send such large work units that they will take over four months for me complete. This is silly.

The fact that the client kills threads and loses results sounds like more of a design problem.

---

...don

> > I think he means that is a good idea to switch manualy between the
> projects.
> > It would be great indeed
>
> No, John is right. This is not a good idea. The very things he mentions
> are what would happen if users had this control...



Otoh. it would allow to pause a project with long running WUs and a deadline that will be in several months and give more time to one where the WUs are about to expire.

Sometimes it downloads more than I wanted it to because it underestimated the runtime - can happen even with just a small 3 days cache - and requires changes in account_*.xml to give more shares to this specific project. The reason for this seems to be caused by the benchmark, the integer bench result is a bit jumpy on dual CPU.

But from what I heard about the next client, this pause thing has already been implemented anyway - so everything seems fine :-)

> > > I think he means that is a good idea to switch manualy between the


huh huh

right now boinc stopped seti with 9 seconds left to completion. sucka...

if there was a little menu 'Switch Projects NOW!'. cause unfinished one seti was on 4.05 version, and downloaded was on 4.07 version. and lhc is out of wu's now...

---

wbr, Me. Dead J. Dona
<a href="http://business.ua">Business.UA</a>
<a href="http://nesam.net.ua">Not alone in a crowd...</a>

If you wan't to change project without loosing credit, there is an ideal way to do it. I did it myself, when I got tired of CPDN and wanted to get back to S@h untill E@h opens up. You just goes in to your general settings and set those to "0" in allowed harddrive space / cache - this way there want be anymore space for chaching WU and the computer want download this. Then it will spend the remaining time on the rest of the project / ~s that you want to participate in and leave the project with an empty cache alone. When the project you want to leave then reaches "0" then make sure it has send all the results and then detach - it's the best way to leave a project without loosing work - as of today.

I know it works explicicly, even though my CPDN model crashed due to something I have now found out was a Microsoft mistake (#@cking MIcrosoft) - well anyway good luck with detaching - and you are all right - it would be nice if you could in the BOINC client ask for a project to not recieve more work from the work server.

---