Personally I think you, like Seti, will come to regret that decision. Seti has by far the most number of people signing up to crunch for it, they do the most PR stuff so why wouldn't people start there? BUT they are also the project that most people then leave for other projects too!! Seti has numerous problems such as not being able to get the grants like they have in the past etc and are now shut down at least 2 days per week every week, this has also affected their ability to retain people who pay to crunch too. The people that do crunch there are aware of that and work around it but since people are leaving the project it also means they no longer have as many people doing the crunching and their time frame to analyze the data is reduced as a result. In short it's your decision and your project and your decisions will affect how long it keeps going at the current rate.

Some projects pay a lot of credits for the crunching power users bring, some projects pay much less, it all depends on your goals and your ability to keep people crunching and projects such as Collatz, they currently pay the most of any gpu project, sometimes struggle to keep things running smoothly and cheater free. If your desires are to get thru the data faster then pay more credits, if your ability to expand or keep your existing hardware running is reduced then reducing the amount of credits you pay is the easiest way to keep users away.

It has recently come to my attention that the Qsqrt421 cases suffer from the same problem that the Bounded app did a couple weeks ago. I am currently looking into a similar fix for these WUs.

The stderr for this WU looks particularly bad. I suspect it could take at least another 6 days to finish. I wont feel bad if you decide to kill it. Either way I will get you manual credit for the lost CPU cycles.

If anyone else has one of these bad WUs please report, either by message board or private message, so I can try and remove them from the system.

Sorry for the inconvenience!

Thanks/Ed

The second one is now at 775 hours, still progressing (says 50% now, up from 49% yesterday).

http://numberfields.asu.edu/NumberFields/workunit.php?wuid=12404866

No happy returns from anyone yet.

Just got home from vacation and checked this WU again. It's at 1342 hours and 52%. Looks like it's been completed by Capital Avionics on 3/24. I assume that I should abort it?

Yes, you can abort that one. I'll give you credit for it when I get home later. Thanks!

It has recently come to my attention that the Qsqrt421 cases suffer from the same problem that the Bounded app did a couple weeks ago. I am currently looking into a similar fix for these WUs.

The stderr for this WU looks particularly bad. I suspect it could take at least another 6 days to finish. I wont feel bad if you decide to kill it. Either way I will get you manual credit for the lost CPU cycles.

If anyone else has one of these bad WUs please report, either by message board or private message, so I can try and remove them from the system.

Sorry for the inconvenience!

Thanks/Ed

The second one is now at 775 hours, still progressing (says 50% now, up from 49% yesterday).

http://numberfields.asu.edu/NumberFields/workunit.php?wuid=12404866

No happy returns from anyone yet.

>>>The second one is now at 775 hours, still progressing (says 50% now, up from 49% yesterday).
>>>http://numberfields.asu.edu/NumberFields/workunit.php?wuid=12404866
>>>No happy returns from anyone yet.

I've been running that one too. On an i7-2600. For 1354 hours now. It's currently at 50.565%.

Sigh.

It has recently come to my attention that the Qsqrt421 cases suffer from the same problem that the Bounded app did a couple weeks ago. I am currently looking into a similar fix for these WUs.

The stderr for this WU looks particularly bad. I suspect it could take at least another 6 days to finish. I wont feel bad if you decide to kill it. Either way I will get you manual credit for the lost CPU cycles.

If anyone else has one of these bad WUs please report, either by message board or private message, so I can try and remove them from the system.

Sorry for the inconvenience!

I have 2 of these WUs running at the moment. One at 271 hours and the other at 385 hours. Leave them run?

http://numberfields.asu.edu/NumberFields/workunit.php?wuid=12420089

http://numberfields.asu.edu/NumberFields/workunit.php?wuid=12404866

Thanks/Ed

Someone has returned a result that was validated on the first of the two work units, so you might just as well abort it and crunch some work unit that has not yet been solved. The other one has not been solved yet, so you can continue on that one.

Thanks for catching that Jesse.

Ed - you can go ahead and abort that WU. I gave you the canonical credit for it. Thanks!

It has recently come to my attention that the Qsqrt421 cases suffer from the same problem that the Bounded app did a couple weeks ago. I am currently looking into a similar fix for these WUs.

The stderr for this WU looks particularly bad. I suspect it could take at least another 6 days to finish. I wont feel bad if you decide to kill it. Either way I will get you manual credit for the lost CPU cycles.

If anyone else has one of these bad WUs please report, either by message board or private message, so I can try and remove them from the system.

Sorry for the inconvenience!