Hi there. I am a bit confused. why are you cutting down on the amount of time need to crunch a fah work unit? won't this stop you from getting the propper data?
as I understand, the long work units are from the most resistant strain of the virus.
I am really baffled, can someone please explain? thanks.

Hello whocrazy,
If you watch the FAAH graphics, you will see that it repeats a number of times and each time it usually produces a lot of temporary dots on the screen. The work unit is really a package that can bundle up more or fewer of these iterations. So the staff can adjust the amount of work required by each work unit.

Lawrence

oh wow. I didn't know you could do that.
btw, is it possible to make exceptions for people with fast computers and also for people who keep their machines turned on all the time?
IE, the really fast machines like mine could do the 30 hour work units, and the slower ones or the ones that aren't active a lot could do the fast work units.
Thanks.

Hello Lawrence,

IMHO WCG had on the list, that we volunteers get the possibility to define in our device profile, whether we prefer long or short Work Units to receive.

Cheers

My immediate reaction is that I would choose shorter WU to reduce a number of risks I believe are present when running longer WU. What would happen if you ran out of short (or long) WU? Don't you risk the wrath of members if you then send long (or short) WU instead? It doesn't seem to me that users have adequate information in order to make a reasonable decision on the WU length. The length of a WU sent to any computer should be based only on the ability of that computer to crunch the WU. I don't want to see you change the points per hour and base that on WU length. From my view this will raise more questions than it will provide answers, but as you work out the design, maybe the questions will be answered.