Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
![]() |
World Community Grid Forums
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
No member browsing this thread |
Thread Status: Active Total posts in this thread: 234
|
![]() |
Author |
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Of the 20 results on the android tablet with 7.32, 40% turned valid, where before had double that number. One turned invalid, never seen with 7.16. One last is now at 49 hours, at 46 percent, other 3 cores punching out simap at the rate of 3 per 2 hours, all 22 so far -not- failed.
Decided to track the wcg credit stats for android, and the last 7 days yielded 17) 342,334 18) 331,729 19) 265,192 20) 199,435 21) 183,050 22) 145,141 23) 108,508 As in yesterday only 108.5k credit. Either there's a massive amount of time locked up in pending validation and unfinished work, or members started voting in even bigger number with the toes first. |
||
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Mentioned before here jeanguy. each rig seems to have a different threshold but there is a time based line which, if crossed, triggers an anti cheat mechanism. This then give a flat rate figure (amount of points) regardless of how much longer the wu takes. The catch for us honest workers though is that particularly long wu's, such as recent FAHV offerings, get caught as well Hello OC, I am aware of the cause and effect for the anti-cheating. My question still remains: Why are people that are being unjustlly hit by a defective and non-discreminating anti-cheating protocol seeing their hard earned WU credit award adjusted markedly downwards without anybody correcting this undesirable discrepancy? Uplinger posted I have just kicked off a script that will grant everyone credit/runtime/points for file size too big issue. It is running right now so you may see this appear shortly. I'm also looking into doing the same for users who have hit the ....???? He has written a script to redress a situation where folks were not awarded due credit for work done due to "file size too big" and then says he is looking into doing the same for user who have hit the ... (unspecified in post). This is great, but in all fairness, shouldn't a corrective action scripts be written and processed for all significant transgressions or omissions by WCG credit/runtime/pts award process. Uplingeer, can a script be written to correct the unjustfied work credit denial due to unplanned extremely long FAHV WUs and a limited and non-discrinimatory anti-cheating ptotocol? Did you implement any other corrective scripts as hinted in your quote above above? Thank you... |
||
|
Sgt.Joe
Ace Cruncher USA Joined: Jul 4, 2006 Post Count: 7696 Status: Offline Project Badges: ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
Well, something appears to have been fixed. I have now returned 3 of these long units which have been validated. Two of them running on Linux and one on Windows.
----------------------------------------Linux units - Mint 16 - Xeon E5410 FAHV_ x3ZSO_ B_ IN_ LEDGFa_ rig_ 0226963_ 0019_ 1-- T7400 Valid 9/21/14 06:36:19 9/24/14 10:05:12 26.76 / 27.00 351.0 / 425.1 FAHV_ x3ZSO_ B_ IN_ LEDGFa_ rig_ 0226973_ 0026_ 0-- T7400 Valid 9/21/14 06:36:19 9/24/14 10:05:12 25.09 / 25.30 328.9 / 208.3 Windows unit - Vista - Q6600 FAHV_ x3ZSO_ B_ IN_ LEDGFb_ rig_ 0226993_ 0013_ 0-- Birthday Valid 9/21/14 01:05:45 9/24/14 09:04:24 53.65 / 53.65 87.8 / 217.1 These really do throw a wrench in the scheduling gears. I have returned the Q6600 to MCM1 where most of my emphasis is because it is a better use of resources for that type of machine. Cheers
Sgt. Joe
*Minnesota Crunchers* |
||
|
pmm1018
Senior Cruncher USA Joined: Dec 29, 2006 Post Count: 222 Status: Offline Project Badges: ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
As in yesterday only 108.5k credit. Either there's a massive amount of time locked up in pending validation and unfinished work, or members started voting in even bigger number with the toes first. I think the majority of us Andriod FAHV crunchers are still here, we're just bogged down with these long-running tasks. My Andriod device hasn't connected to WCG since Sept 18th. The next time it does, will be to report a unit currently at 75.0% complete in over 68 hours of crunching. It's due on Sept 29th and I should make the deadline. ![]() ![]() |
||
|
Eric_Kaiser
Veteran Cruncher Germany (Hessen) Joined: May 7, 2013 Post Count: 1047 Status: Offline Project Badges: ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
One of my androids is receiving the shorter wu while one other is finishing some of the last long running ones within the deadline.
----------------------------------------I'm fine with it. ![]() |
||
|
JSYKES
Senior Cruncher Joined: Apr 28, 2007 Post Count: 201 Status: Offline Project Badges: ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
I've had several of these long running FAHV WU's - typically running 54 to 60hrs - but the credit being given is paltry - 87 points!! I have 100 points for a 6 hours WU - what's going on? If the WU's take longer to run, there should be commensurate points, otherwise its not worth running them!! If this continues, I think I'll switch out of FAHV entirely, as it's not productive use of CPU time.
----------------------------------------![]() |
||
|
OldChap
Veteran Cruncher UK Joined: Jun 5, 2009 Post Count: 978 Status: Offline Project Badges: ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
Each rig has a time limit in which to complete a given wu. go over it and ...well you see what happens.... 2 points per hour here.
----------------------------------------Rather than recall these long wu's that error out anyway we get to run them for some reason ....and we get re-sends too. I notice one with: World Community Grid 7.32 FightAIDS@Home - Vina FAHV_x3VQ8_B_IN_LEDGFa_rig_0221726_0049_11 77.93% 01d,17:04:14 I seem to have another 3 days 18 hours worth of these based on a projected runtime of ~5.5 hours. considering I am looking at a reality of one here that took 28 hours to reach 75% then a whole bunch of these will exceed deadline. then error out. then get re-issued. What good is this to the science? In fact Stuff it .... They can have all of these back. If they can't be bothered sorting them out I can't be bothered running them either. ![]() [Edit 1 times, last edit by OldChap at Sep 25, 2014 11:10:08 PM] |
||
|
Sgt.Joe
Ace Cruncher USA Joined: Jul 4, 2006 Post Count: 7696 Status: Offline Project Badges: ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
FAHV_ x3ZSO_ B_ IN_ Y3a_ rig_ 0227275_ 0019_ 3-- - In Progress 9/26/14 07:19:38 9/29/14 19:19:38 0.00 0.0 / 0.0
----------------------------------------FAHV_ x3ZSO_ B_ IN_ Y3a_ rig_ 0227275_ 0019_ 2-- - In Progress 9/24/14 19:43:09 9/28/14 07:43:09 0.00 0.0 / 0.0 FAHV_ x3ZSO_ B_ IN_ Y3a_ rig_ 0227275_ 0019_ 1-- 732 Error 9/21/14 18:15:29 9/24/14 19:43:03 43.11 483.8 / 483.8 FAHV_ x3ZSO_ B_ IN_ Y3a_ rig_ 0227275_ 0019_ 0-- 732 Error 9/21/14 18:14:53 9/26/14 07:19:05 27.63 216.5 / 0.0 < Mine They still appear to be sending out some of the WU that will give the "131" error of a too big file size result. Cheers
Sgt. Joe
*Minnesota Crunchers* |
||
|
nittany85
Cruncher United States of America Joined: Apr 29, 2007 Post Count: 17 Status: Offline Project Badges: ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
My machines are still working on a few of the long Vina jobs but it also looks like all of the new ones waiting to be worked on are the shorter jobs. While there may still be a few of the long jobs in the system we will soon be done with them. No need to give up on this project because of this issue.
|
||
|
pmm1018
Senior Cruncher USA Joined: Dec 29, 2006 Post Count: 222 Status: Offline Project Badges: ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
Vaild! Booyah! I think I set a record.... 83.6 hours for a single work unit on my Samsung Galaxy S4.
----------------------------------------![]() FAHV_ x3ZSO_ B_ IN_ FBPb_ rig_ 0226582_ 0058_ 2-- 732 Valid 9/20/14 08:19:02 9/25/14 06:27:05 83.63 449.9 / 472.3 ![]() ![]() [Edit 1 times, last edit by pmm1018 at Sep 26, 2014 1:16:06 PM] |
||
|
|
![]() |