I don't know what was done in 5.07, but it doesn't want to stop working.

The difference you are seeing is more likely due to the specific WU you were crunching that the application version. And as for it continuing to run after you suspend it, I've seen this before as well, the BOINC Manager basically loses contact with the processes that are doing the crunching (regardless of what project those processes are crunching for). I find that if I restart BOINC, I regain control over what is running and what is suspended.

If you have not already done so, you may want to change your General Preference to NOT run while you are using your computer. That should help avoid conflicts with your work. You might also configure it to only run during specific times of day (when you are not using your computer).

If you have further problems or questions, I'd suggest creating a thread in the Q&A board for Windows, because this doesn't sound like something v5.07 would have caused.

---

Add this signature to your EMail:
Running Microsoft's "System Idle Process" will never help cure cancer, AIDS nor Alzheimer's. But running Rosetta@home just might!
https://boinc.bakerlab.org/rosetta/

I don't know what was done in 5.07, but it doesn't want to stop working.

The difference you are seeing is more likely due to the specific WU you were crunching that the application version. And as for it continuing to run after you suspend it, I've seen this before as well, the BOINC Manager basically loses contact with the processes that are doing the crunching (regardless of what project those processes are crunching for). I find that if I restart BOINC, I regain control over what is running and what is suspended.

I don't think it has to do with BOINC. BOINC can suspend SETI without any problems at the same time when Rosetta runs like a "virus" :) ignoring any suspend atemtpts. It did not behave like this 2-3 weeks ago. This is something recent. WU's should not have much to do with ability to suspend the process.

Restarting BOINC might be a workaround (I'll try it), but I think new version of the process has some issues it did not have before :)

I'll have to remove Rosetta from my laptop since there is no other time I can run it under present conditions. Currently, the priority setting "feels" almost like it is ignored for Rosetta process. It competes with other Windows applications as if it was created with the same or higher priority.

Regards,
Bogdan

---

I don't know what was done in 5.07, but it doesn't want to stop working.

The difference you are seeing is more likely due to the specific WU you were crunching that the application version. And as for it continuing to run after you suspend it, I've seen this before as well, the BOINC Manager basically loses contact with the processes that are doing the crunching (regardless of what project those processes are crunching for). I find that if I restart BOINC, I regain control over what is running and what is suspended.

I don't think it has to do with BOINC. BOINC can suspend SETI without any problems at the same time when Rosetta runs like a "virus" :) ignoring any suspend atemtpts.

Just tried another WU. I played with suspend/resume. What happens is that for Rosetta, when you suspend the process it does not exit. It still sits in memory, not using any CPU. For SETI it exits and does not keep using virtual memory. I'm guessing that at some point something may go wrong and in addition to sitting in memory after being suspended, it would keep using it, i.e. running...

Regards,
Bogdan

---

I don't know what was done in 5.07, but it doesn't want to stop working.

The difference you are seeing is more likely due to the specific WU you were crunching that the application version. And as for it continuing to run after you suspend it, I've seen this before as well, the BOINC Manager basically loses contact with the processes that are doing the crunching (regardless of what project those processes are crunching for). I find that if I restart BOINC, I regain control over what is running and what is suspended.

I don't think it has to do with BOINC. BOINC can suspend SETI without any problems at the same time when Rosetta runs like a "virus" :) ignoring any suspend atemtpts.

Just tried another WU. I played with suspend/resume. What happens is that for Rosetta, when you suspend the process it does not exit. It still sits in memory, not using any CPU. For SETI it exits and does not keep using virtual memory. I'm guessing that at some point something may go wrong and in addition to sitting in memory after being suspended, it would keep using it, i.e. running...

Regards,
Bogdan

Actually there is a setting in your general preferences whether suspended (preempted) application should stay in memory or not. When exited some computer time is lost since after a restart the app starts from the latest checkpoint, so leaving in memory is recommended. The process gets out of RAM to the swap file if the RAM is neeed and takes no CPU time while it's suspended.

What is strange is that the general setting for leaving in memory or not is the same for all BOINC projects. So it should behave identical for Seti and Rosetta. Can you check what you have in your general settings and report back?

---

I don't know what was done in 5.07, but it doesn't want to stop working.

The difference you are seeing is more likely due to the specific WU you were crunching that the application version.

I don't think it has to do with BOINC. BOINC can suspend SETI without any problems at the same time when Rosetta runs like a "virus" :) ignoring any suspend atemtpts. It did not behave like this 2-3 weeks ago. This is something recent. WU's should not have much to do with ability to suspend the process.

Currently, the priority setting "feels" almost like it is ignored for Rosetta process. It competes with other Windows applications as if it was created with the same or higher priority.

My point was that many of the more recent WUs use more memory and do more paging than the WUs of a month ago. I believe it is the memory utilization and paging that makes you "fell it" on your PC. Even though the BOINC work runs at the lowest possible priority, once it sends a request to the disk, your click over in MS Word or whatever has to wait for that BOINC disk request to complete before it can proceed to resolve a disk request from your user application. This is why the application is impacted, even though it has a higher priority for CPU time.

Not being able to suspend a task is a second issue, that I believe rests with BOINC, we'll table that one, because it seems less significant to you than being able to make use of your laptop while BOINC is running.

Please review your General Preferences, specifically
"Do work while computer is in use?" -- I think you want NO
"Do work only after computer is idle for xx" -- How many minutes would make it likely you have left your PC for a while? 5? 10?, you may want to increase it. Be sure your BOINC Manager Command tab shows "run based on preferences" for these to take effect.
"Use no more than x% of total virtual memory", you may want to reduce it, say 10% a day until it settles down.

If you have further problems or questions, I'd suggest creating a thread in the Q&A board for Windows, because this doesn't sound like something v5.07 would have caused.

---

Add this signature to your EMail:
Running Microsoft's "System Idle Process" will never help cure cancer, AIDS nor Alzheimer's. But running Rosetta@home just might!
https://boinc.bakerlab.org/rosetta/

This question maybe the dumbest question I have asked yet . Pardon my newbiness but is the data produced in those units that resulted "in errors" used by the scientists? In simpler words was the computing time involved in those "erroneous units" lost to science or not?

Be gentle in your answer: I am a newbie watch me look dumb :)

---

Was the computing time involved in those "erroneous units" lost to science or not?

The project values everything they learn. This is why they give credit, even if a WU errors out. They take the perspective that if there is an error, and noone reports it, then we all lose. WITH the report, they can learn why it failed, fix it, and take steps to avoid others encountering problems in the future.

Edison tried more than 1,000 things before he found a filiment for a hypothetical light bulb. Not all of the new science the project tries is going to produce fruitful results, but it adds to the list of things they know doesn't work :)

---

Add this signature to your EMail:
Running Microsoft's "System Idle Process" will never help cure cancer, AIDS nor Alzheimer's. But running Rosetta@home just might!
https://boinc.bakerlab.org/rosetta/

has anyone come across their screensaver freezing up on them? the best i can tell, it only happens when the rosetta is running as a screensaver. rosetta work units hit 100% and then it freezes. im pretty sure it has to do with my intel graphics/video card because i had this same problem with einstein as well. if the workunit doesnt hit 100%, it is fine.

5/8/2006 10:03:09 PM|rosetta@home|Sending scheduler request to https://boinc.bakerlab.org/rosetta_cgi/cgi
5/8/2006 10:03:09 PM|rosetta@home|Requesting 0 seconds of work, returning 1 results
5/8/2006 10:03:10 PM|rosetta@home|Scheduler request to https://boinc.bakerlab.org/rosetta_cgi/cgi succeeded
5/8/2006 10:03:32 PM||request_reschedule_cpus: project op
5/8/2006 10:03:35 PM|rosetta@home|Sending scheduler request to https://boinc.bakerlab.org/rosetta_cgi/cgi
5/8/2006 10:03:35 PM|rosetta@home|Requesting 8640 seconds of work, returning 0 results
5/8/2006 10:03:36 PM|rosetta@home|Scheduler request to https://boinc.bakerlab.org/rosetta_cgi/cgi succeeded
5/8/2006 10:03:36 PM|rosetta@home|Message from server: Not sending work - last RPC too recent: 25 sec
5/8/2006 10:03:36 PM|rosetta@home|No work from project
5/8/2006 10:03:37 PM|rosetta@home|Deferring communication with project for 4 minutes and 1 seconds

---------------------------------------------------------------------------

Is this a bug? The system would not send me a workunit because the time between BOINC returning a workunit and getting a workunit was to recent. That makes no sense to me. I have to wait to get a workunit after reporting one? HMMMMMMm.

---

Have the developers found a solution to the "107" types of errors that keep proping up?

---

sorry I guess this is in the wrong forum

---

I have been attached to Rosetta@home for many moons, but as of the last few months I have had a disturbing problem; I never get any tasks--ever. I have tried resetting the whole Rosetta project, I have tried MANY times to schedule a new task (or request a new task--whichever), with no luck. What's wrong?

Here is a sample log. They're all the same:

Sun Dec 17 05:49:48 2006|rosetta@home|Sending scheduler request to https://boinc.bakerlab.org/rosetta_cgi/cgi
Sun Dec 17 05:49:48 2006|rosetta@home|Reason: Requested by user
Sun Dec 17 05:49:48 2006|rosetta@home|(not requesting new work or reporting completed tasks)
Sun Dec 17 05:49:53 2006|rosetta@home|Scheduler request succeeded
Sun Dec 17 05:59:03 2006||Rescheduling CPU: project reset by user
Sun Dec 17 05:59:03 2006|rosetta@home|Resetting project
Sun Dec 17 05:59:03 2006||Rescheduling CPU: exit_tasks
Sun Dec 17 05:59:19 2006|rosetta@home|Sending scheduler request to https://boinc.bakerlab.org/rosetta_cgi/cgi
Sun Dec 17 05:59:19 2006|rosetta@home|Reason: Requested by user
Sun Dec 17 05:59:19 2006|rosetta@home|(not requesting new work or reporting completed tasks)
Sun Dec 17 05:59:24 2006|rosetta@home|Scheduler request succeeded


Can anyone tell me what the heck is going on?! I'm stumped.

---

Are you using a BOINC account manager?

---

What's listed on the Projects and Tasks tabs of the Boinc manager screens under Status?

---

Well, I repaired it...I think. I decided to "detach," which I did not want to do in case I would lose data. However, once I detached and then re-attached (or whatever it's called), everything went back to normal...for now. I think that I am attached to my old account, but the stats look bad in my graph. I'll wait to see if everything evens out.

Thanks for the prompt help attempts. I will definitely return if something else goes wrong.

John

---

My question is similar to one below.

Sometimes my laptop tries to communicate with R@H and if I am not connected to the net, it keeps trying until it fails four times. Then comes the kicker: it ceases communications for an entire week!! I lost 12+ hours of crunching yesterday when it decided not to communicate, even after finishing all of the current tasks. What do I do to get BOINC to keep trying for a day or so until I get back online to update the tasks? A couple of times when this happened I was only offline for a couple of crunching hours. I do have BAM! for my manager.

---

(Click for detailed stats)

My question is similar to one below.

Sometimes my laptop tries to communicate with R@H and if I am not connected to the net, it keeps trying until it fails four times. Then comes the kicker: it ceases communications for an entire week!! I lost 12+ hours of crunching yesterday when it decided not to communicate, even after finishing all of the current tasks. What do I do to get BOINC to keep trying for a day or so until I get back online to update the tasks? A couple of times when this happened I was only offline for a couple of crunching hours. I do have BAM! for my manager.

It shouldn't back off that much.. :eek:

But you can use the 'Advanced -> Retry communications' will kick communication into action again.

---

Team mauisun.org

It shouldn't back off that much.. :eek:

But you can use the 'Advanced -> Retry communications' will kick communication into action again.

I was just thinking that perhaps there is a setting that is different from the norm that might be the cause. I looked, and reset the activity tab to => Run based on preferences, rather than => Run always. Don't know if that will help, but that's the only thing I can see that is different that I've changed for that computer.

---

(Click for detailed stats)

It shouldn't back off that much.. :eek:

But you can use the 'Advanced -> Retry communications' will kick communication into action again.

I was just thinking that perhaps there is a setting that is different from the norm that might be the cause. I looked, and reset the activity tab to => Run based on preferences, rather than => Run always. Don't know if that will help, but that's the only thing I can see that is different that I've changed for that computer.

The run always just makes the computer ignore specified timings to run and the only run when not in use.

The network one may make a difference, not sure if it really does though (again I think that just makes it ignore the netwrok restrictions)

Though this should really be in a new thread by itself ;)

---

Team mauisun.org