So while we're trying to figure out the problem with some of these workunits causing NAN/infinity fitnesses (and thus causing the boinc client to mark them as an error), I've started some new ones -- which should mean there are less errors floating around.

I've also updated out workunit templates so that after 1 error it should just trash a workunit (I hope). This means the erroneous workunits won't keep getting sent out to users further complicating the problem.

It's not the best solution, but hopefully it will improve things while we figure out what's wrong with the code/input files that's causing the issue for these searches.

--Travis
____________

Looking good, only one "error while computing" today, my RAC is already again over 20,000 :).

That were the good news. As to the not-so-good part:

I've also updated out workunit templates so that after 1 error it should just trash a workunit (I hope). This means the erroneous workunits won't keep getting sent out to users further complicating the problem.

You might want to increase that to 2 (so actually 3): see this WU. I'm not sure how the whole thing is working, on this one new results (_3 & _4) were created after reaching the "too many errors" state, but I thought you might want to have a look at this one.


My system: Win7 x64, ATI HD3850 (not OpenCL capable, Catalyst 11.9) using the 64-bit CAL app v0.82, running 2 WUs at once.