Everything seems to be running fine, but occasionally I see "Computation Error" in the "Status" column on the "Work" tab. Happened yesterday again. It's gone now, I assume it cleared itslef. Is there something I should do to keep this from happening?

Windows XP, Pentium 4 class, BOINC 5.2.13

---

So the wu is invalid ?

---

So the wu is invalid ?

No idea. All I know is sometimes I see that there is a Computational Error, and then later it is gone.

---

So the wu is invalid ?

No idea. All I know is sometimes I see that there is a Computational Error, and then later it is gone.

Just looking at your results files, it looks as though the computation errors you are getting will not get credit. When you say that they are there and then they are gone, i assume you mean from the Work Unit queue on your system in the BOINC manager display. If that is the case, what you are seeing is normal behavior. When the WU errors out it will be listed in the work Queue as a client error or a computation error until the system "reports" its results. When it reports, the listing for the WU on your system will disappear. After that the only place you can see the error is in your stats here at the project web site.

They will be listed there for a while until the project cleans its data base, which happens every few days to a few weeks, then they will be gone from there as well.

The errors you are getting are a bit difficult to diagnose, but based on the error information it seems as though they may be related to a known bug. The fix for the bug is to set your preferences to "keep application in memory durring swaps" to YES. In effect if your are running more than one project this would keep the rosetta application in memory when the other project is active and vise-versa.

If you are only running one project, then you should avoid shutting BOINC down, suspending active work units, suspending project activity for R@H, or rebooting your system. All of these activities interupt the work unit in progress and can cause errors when the WU restarts.

As I said the project team is aware of the bug and they are working on a fix.

Regards
Phil

---

We Must look for intelligent life on other planets as,
it is becoming increasingly apparent we will not find any on our own.

So the wu is invalid ?

No idea. All I know is sometimes I see that there is a Computational Error, and then later it is gone.

Just looking at your results files, it looks as though the computation errors you are getting will not get credit. When you say that they are there and then they are gone, i assume you mean from the Work Unit queue on your system in the BOINC manager display. If that is the case, what you are seeing is normal behavior. When the WU errors out it will be listed in the work Queue as a client error or a computation error until the system "reports" its results. When it reports, the listing for the WU on your system will disappear. After that the only place you can see the error is in your stats here at the project web site.

They will be listed there for a while until the project cleans its data base, which happens every few days to a few weeks, then they will be gone from there as well.

The errors you are getting are a bit difficult to diagnose, but based on the error information it seems as though they may be related to a known bug. The fix for the bug is to set your preferences to "keep application in memory durring swaps" to YES. In effect if your are running more than one project this would keep the rosetta application in memory when the other project is active and vise-versa.

If you are only running one project, then you should avoid shutting BOINC down, suspending active work units, suspending project activity for R@H, or rebooting your system. All of these activities interupt the work unit in progress and can cause errors when the WU restarts.

As I said the project team is aware of the bug and they are working on a fix.

Regards
Phil

When setting "keep application in memory durring swaps" to yes, what kind of memory is consumed? RAM, harddrive or other?

Thanks,

Jonas

---

So the wu is invalid ?

No idea. All I know is sometimes I see that there is a Computational Error, and then later it is gone.

Just looking at your results files, it looks as though the computation errors you are getting will not get credit. When you say that they are there and then they are gone, i assume you mean from the Work Unit queue on your system in the BOINC manager display. If that is the case, what you are seeing is normal behavior. When the WU errors out it will be listed in the work Queue as a client error or a computation error until the system "reports" its results. When it reports, the listing for the WU on your system will disappear. After that the only place you can see the error is in your stats here at the project web site.

They will be listed there for a while until the project cleans its data base, which happens every few days to a few weeks, then they will be gone from there as well.

The errors you are getting are a bit difficult to diagnose, but based on the error information it seems as though they may be related to a known bug. The fix for the bug is to set your preferences to "keep application in memory during swaps" to YES. In effect if your are running more than one project this would keep the rosetta application in memory when the other project is active and vise-versa.

If you are only running one project, then you should avoid shutting BOINC down, suspending active work units, suspending project activity for R@H, or rebooting your system. All of these activities interrupt the work unit in progress and can cause errors when the WU restarts.

As I said the project team is aware of the bug and they are working on a fix.

Regards
Phil

When setting "keep application in memory during swaps" to yes, what kind of memory is consumed? RAM, harddrive or other?

Thanks,

Jonas

The application will be moved to your virtual memory during an application swap. It will then be put back in RAM when Roestta starts up again. In addition to the above, you should consider setting the time between application swaps to something like 120 min to provide enough time for Rosetta to "Checkpoint" between swaps. for more detail on this and other related topics please take some time to browse the FAQs thread linked from my signature.

---

Moderator9
ROSETTA@home FAQ
Moderator Contact

Thanks

---