I'll gather more data and hopefully describe this better. What I'm seeing right now is that the estimated time remaining is several hours greater than the time until the deadline. (Yesterday I opted out of running FAAH2, but hadn't aborted a couple of WUs because it looked as if they would manage to finish by the deadline. The stats however, are now suggesting that that is unlikely.) The WUs often finish and are accepted, not sure exactly when, but I *think* after the deadline. (Alternatively, I suppose that the estimated time remaining might suddenly lose the last 5 hours or so out of 20.) I suspect that if computing happens after the deadline, then it isn't counted, for whatever reason. I don't care about credit; what worries me is that the biological computations might be wrong, perhaps involving wasted cycles, or perhaps designed by someone who hasn't done a good job of testing. If they haven't fixed these obvious things that look bad to us volunteers, do they know what they are doing with the chemistry?

P.S.: This is not due to confusion over times, I do realize that the Boinc manager displays local time, and the online Results Status uses UTC.

Here are some data. I had two FAAH2 WU's running. Here are lines from three screenshots from the Results Status page online (pipes added for clarity). The strange thing is that one of the two WUs continued running after it was awarded Valid status; it requested credit for that extra work (1.75 hours, 14.01 - 12.26), but it was not granted. 310.8 credit was claimed, but only the earlier 272.0 was granted. 1.75 hours of computing was apparently wasted. As mentioned above, this could produce a lower average credit per CPU hour for this project than for others. What was the WU doing for those 1.75 hours? Did it successfully report the results? I doubt that this is due to the default CPU % discussed in the next post, because these two WU's were running on the same machine (dual processors). I thought this behaviour might be because there's a time delay between credit being claimed and credit being granted, but now, nearly 12 hours later, the status of the strange WU still shows the same disparity, 310.8 claimed, 272.0 granted.

Screen Shot 2015-12-19 at 17.45.21
Result name | Status | Time due/Return Time | CPU Time/Elapsed | Claimed/Granted BOINC Credit
FAH2_avx38747-is_000065_0016_024_0-- | In Progress | 12/20/15 05:46:08 | 12.26 / 0.00 | 272.0 / 0.0
FAH2_avx38747-is_000021_0015_029_0-- | In Progress | 12/20/15 05:44:00 | 14.05 / 0.00 | 310.8 / 0.0

Screen Shot 2015-12-19 at 19.55.21
Result name | Status | Time due/Return Time | CPU Time/Elapsed | Claimed/Granted BOINC Credit
FAH2_avx38747-is_000065_0016_024_0-- | Valid | 12/19/15 23:46:52 | 12.26 / 0.00 | 272.0 / 272.0
FAH2_avx38747-is_000021_0015_029_0-- | Valid | 12/19/15 23:46:45 | 15.85 / 0.00 | 349.6 / 349.6

Screen Shot 2015-12-19 at 21.52.05
Result name | Status | Time due/Return Time | CPU Time/Elapsed | Claimed/Granted BOINC Credit
FAH2_avx38747-is_000065_0016_024_0-- | Valid | 12/19/15 23:46:52 | 14.01 / 0.00 | 310.8 / 272.0
FAH2_avx38747-is_000021_0015_029_0-- | Valid | 12/19/15 23:46:45 | 15.85 / 0.00 | 349.6 / 349.6

Sorry FightAIDS@Home Phase 2 project, I have to bail on this one.
I find it near impossible to complete this project in the time given.
My PC's do not run 24/7.
If the time to return results ever gets extended I will return.

This must be the wrong thread but I don´t know where else to ask, sorry

I had a laptop with an intel core2duo p8800, now I have a core i7 2670QM, it IS somewhat dated now but the core2duo was faster than the i7 and I don´t know why , does anyone know? is it something I have to configure?

Thnak you

Will do, thank you