Just lost 15 jobs due to this "computation error" in the work section anyone here have any ideas.Useing 4.81 version running windows XP pro, cpu is a barton 2500+ and 1 gig of memory.

---

Visit us at Christianboards.org

This is a known issue...

Read this thread: https://boinc.bakerlab.org/rosetta/forum_thread.php?id=726

---

So i take it that there is no cure for this?? so i spent 1-2 hours downloading jobs to have them all be of no use(by the way iam on dial-up@32Kbps)it seems almost a waste of time then.

---

Visit us at Christianboards.org

So i take it that there is no cure for this?? so i spent 1-2 hours downloading jobs to have them all be of no use(by the way iam on dial-up@32Kbps)it seems almost a waste of time then.

If you are on dial-up, the best thing you can do is "Suspend" Rosetta until after the holidays. Let your CPU work on some other projects, and then we'll be here waiting for you with all problems solved! :-)

(Fingers crossed...)

---

So i take it that there is no cure for this?? so i spent 1-2 hours downloading jobs to have them all be of no use(by the way iam on dial-up@32Kbps)it seems almost a waste of time then.

Though all projects try to be problem free, so far none of them have much made it. So, we live with it and work around the issues. If you want *MY* list of known issues (though some of these issues do not affect me - like screen savers; i don't use the screen savers) ...

CPDN: Model *ALWAYS* crashes on the PowerMac, usually on model re-starts
SAH: Enhance application and AstroPulse not out yet
EAH: Screen saver crashes on some systems
PPAH: Crash pops dialog box halting system processing till clicked (real bad for systems I don't check daily)
LHC: Screen saver crashes; intermittant work
RAH: 1% bug (cost me 25 hours once ... sob)
SDG: Web site still partly written in Hungarian, no interaction to speak of with participants
PG: Not really science
WCG: 31 digit Account Key, I can get a 32 digit if I detach and lose work then reattach (will likely drain WCG when LHC gets work and do it at that time, giving LHC roughly 20%).

So, there you have it ... all projects have problems ... we just have to make the best of it ... though it is easier for me with cable access ...

If you can afford the connect time, it still is usefull to run and crash and let the project have the bad result back. How can they fix it if they don't know what is broken? :)

Hope you can stay, or, if you detach, you come back soon ...

---

If you are on dial-up, the best thing you can do is "Suspend" Rosetta until after the holidays. Let your CPU work on some other projects, and then we'll be here waiting for you with all problems solved! :-)

(Fingers crossed...)

That's not exactly a fix.

---

Visit us at Christianboards.org

That's not exactly a fix.

No, it isn't.

It *IS* an appropriate and responsible solution to the immediate problem.

I will bet that you did not schedule a lot of work over the holidays ... we have to remember that the project people are just that sometimes ... people I mean ... they need time off too ...

Only on TV can problems be solved in 30 minutes (well, 20) ... the real world takes longer ... :)

---

That's not exactly a fix.

No, it isn't. It's a temporary workaround to avoid wasting a participant's resources.

And?

---

So the fact that I have the same problem with 6 machines, 3 different OS's, Cable internet. The best solution is work another project? Thats 2 members of the same team with CPU's working at 100% for nothing.....Sounds like my team will have to see about a new project if that keeps up.

---

http://www.christianboards.org/forum.php
http://usalug.org/phpBB2/index.php

So the fact that I have the same problem with 6 machines, 3 different OS's, Cable internet. The best solution is work another project? Thats 2 members of the same team with CPU's working at 100% for nothing.....Sounds like my team will have to see about a new project if that keeps up.

The suggestion was "if you are on dial-up, you should probably suspend Rosetta until after the holidays, when they can get the problem solved". This is because of the ratio of download time to crunching time; dial-up people are spending too high a percentage of their time on non-productive work.

If you can afford the connect time, it still is usefull to run and crash and let the project have the bad result back. How can they fix it if they don't know what is broken? :)

So, the recommendation for _you_ is to keep on crunching. You certainly _could_ suspend Rosetta, but you could do that just because it's Friday and you prefer not to do bio projects on Fridays. That's up to you. From the project's perspective, it would be far better if you and the rest of your team members who are not on dialup just continued processing. That would be the best contribution to the project that you can make, assisting in getting the "short WUs" flushed through.

On dial-up or paying by the MB for bandwidth - Suspend Rosetta until after holidays.
Have full-time internet connection -
a) Wish to make contribution to project - keep crunching
b) Wish to insure that you don't lose any credit - Suspend Rosetta until after holidays.

It all depends on what your goals are, but it's ultimately up to you.

---

I will keep flushing them through for you on my two machines...broadband and no limit....Mewrry Christmas

---

I'll run through what I can, but if I get too many, I'll shut down my machines on dialup, and save the 'leccy bills.. I cant afford to run through too much. If i can catch some of the bad ones, I'll be happy to be able to help as much as poss.


<edit> And oh yes.. Merry Christmas =D </edit>

---

After a review of all machines on this project 7 are showing a 60% (Correction its a 90%) failure rate with the client. I am ending my involvement in this project since I cant seem to get a straight answer to any of the questions I ask. GOOD BYE...

---

http://www.christianboards.org/forum.php
http://usalug.org/phpBB2/index.php

I cant seem to get a straight answer to any of the questions I ask. GOOD BYE...

Could have sworn I gave a very straight and definitive answer to the question... it's a temporary problem, it will be solved after the holidays, there is NO way to get it solved before then, so, anyone wanting to continue can continue, anyone wanting to suspend Rosetta until it IS solved, should do so.

???

---

Just for info - SETI sent out a bunch of bad WUs not too long ago. Anyone complaining about running for 30 seconds and not getting credit, should look here.

Nobody's perfect. But at least the Rosetta folks are _trying_ to do the right things, and giving credit when possible.

---

The random number seed issue should be resolved by now. There is still a 7% chance of getting a bad seed but this is no different than previous runs weeks before. When I and others get back from holiday break, we will fix it completely and grant credit to those affected by the recent issues.

I still have no understanding as to why all of my machines have had 3 days of these failures. Was I just plain hit with bad odds of recieving so many bad jobs? I have to leave for Iraq, I want to know if keeping these machines running is worth it. These Machines ran without problem for the month I was in Afghanistan for Find-a-Drug. Remotes keep droping the client and I have to restart them about every week. Now I look at my results for this day alone and have not contributed any good job all day.

---

http://www.christianboards.org/forum.php
http://usalug.org/phpBB2/index.php

We live in an imperfect world where not everything runs smoothly. That's life.

Yes, Rosetta has had problems and is still recovering from it. So have other projects (and I've participated in a few). Some of those took a lot longer to recover.

You're not the only one who has had problems with this batch of bad work units. I've had dozens, if not hundreds of them myself. I decided to not download any new Rosetta work for a few days and reduce my resource share temporarily. This problem will take some time to clear up but signs are that it is getting there.

Most of the problems were in jobs from batches 204 to 207. If you are having problems with other batches, perhaps the problem is elsewhere, e.g. hardware problems.

And you have been given straight answers.

So the fact that I have the same problem with 6 machines, 3 different OS's, Cable internet. The best solution is work another project?

Yes. That's the beauty of BOINC.

Thats 2 members of the same team with CPU's working at 100% for nothing.....

More like thousands of members of hundreds of teams having CPUs working in short bursts on work units that have a problem. It pales into insignificance with problems I have experienced on other projects.

Sounds like my team will have to see about a new project if that keeps up.

That's your choice and I have done so myself with some projects, after giving them time to sort out their problems. Let us know when you find a project that runs perfectly - I am yet to find one.

Edit: Some of your machines also fall below the recommend specs to run Rosetta. For instance, one of your machines has only 128MB RAM and a number of them are runnng Windows ME, which is not officially supported.

---

*** Join BOINC@Australia today ***

Remove me as a member of this forum Administrator.

---

http://www.christianboards.org/forum.php
http://usalug.org/phpBB2/index.php

Just lost 15 jobs due to this "computation error" in the work section anyone here have any ideas.Useing 4.81 version running windows XP pro, cpu is a barton 2500+ and 1 gig of memory.

I`m using 4.8 and am losing at least 50% of WUs also from "computation error". It doesn`t happen on other BOINC projects, and I`m sure my computer is OK. I guess Rosetta will have to sort out it`s act before it loses all it`s clients.

---