| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Completed Research
Forum: FightAIDS@Home
Thread: No Vina just now?? |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 35
|
|
| Author |
|
|
Speedy51
Veteran Cruncher New Zealand Joined: Nov 4, 2005 Post Count: 1296 Status: Offline Project Badges: 
|
Depends how you interpret 1:4, but it was meant as 1 in 4, so your calculation was right. Thanks for confirming my calculation method  |
||
|
|
Seoulpowergrid
Veteran Cruncher Joined: Apr 12, 2013 Post Count: 817 Status: Offline Project Badges: 
|
I am running a 2.93 GHz and 220,351 has spent 14 hours getting to 65%. I'll keep it going for however long it needs, but as the CEP2 WU have limits of 18 hours, is there any limitations for WUs from this project?
---------------------------------------- |
||
|
|
Seoulpowergrid
Veteran Cruncher Joined: Apr 12, 2013 Post Count: 817 Status: Offline Project Badges:
|
Well it hit 22 hours, 800 kb, and uploaded just fine :)
---------------------------------------- |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Hello,
I just noticed this thread. Here's some relevvant info: Back in October 2013, created Vina jobs that used its "flexible" receptors feature. WCG had performed some tests, and started submitting them to donors' machines since about February/March of this year. Since then, WCG has been adjusting parameters so that they run in a reasonable amount of time on your machines. This accounts for longer run times and the jump back to Experiments 97-102. Thanks, Dan |
||
|
|
jay_Orlando
Senior Cruncher USA Joined: Jan 4, 2006 Post Count: 181 Status: Offline Project Badges:
|
ooops.
---------------------------------------- Cancelled some WU when time remaining stopped and elapsed time went over expected time on a fairly fast machine. Should have read forums first. Jay --- edit -- Two cancelled had 17+ hours on a fairly fast machine. I have another https://secure.worldcommunitygrid.org/ms/devi....do?workunitId=1185639974 on a slower machine that has run for 21+ hours and shows over 4 hours remaining. I guess I should let it go to 30 or 35?? Jay ---------- 2nd edit ----- Now is 06 Sept and the WU has been crunching for over 38 hours on a 2.2 Ghz AMD running windows vista. It now shows completion estimate of over 8 hours.. Interesting.... --------- 3rd edit ------- Now is after Noon on 07 September and he WU has been crunching for over 52 hours. shows estimated completion of 3 1/2 hours. But suspending and exiting BOINC for weekly antvirus scan. will start up again afterwards. Oh, have another LEDGa_rig hat has been running for 31 hours. https://secure.worldcommunitygrid.org/ms/devi....do?workunitId=1186093010 ---------- 4th edit ---------- ( Providing comparisons for those also with a Ledge WU. ) Now it is evening on 7 September. One of the Ledge WU finally finished after 57.78 hours. (on 2.2Ghz machine) The other Ledge WU running on the 2.2 Ghz machine says it is 79% done with an elapsed time of 39 hours. My other box, with a 3Ghz CPU has 2 more Ledge WUs https://secure.worldcommunitygrid.org/ms/devi....do?workunitId=1186093010 showing 68% done at 16.5 hours. and https://secure.worldcommunitygrid.org/ms/devi....do?workunitId=1186093141 showing 84% done at 16.3 hours. Both will probably go over the estimated times as did the others. Happy crunching.... Jay  [Edit 5 times, last edit by jay_Orlando at Sep 8, 2014 3:27:16 AM] |
||
|
|
Sgt.Joe
Ace Cruncher USA Joined: Jul 4, 2006 Post Count: 7677 Status: Offline Project Badges: 
|
Just let it run. I have one at 50% on a Xeon e5410 (Linux Mint 16) at 12 hours but it is still incrementing the percentage done. These are just bigger than "normal" units.
----------------------------------------Edit: Update The unit got finished finally. FAHV_x3VQ7_IN_LEDGFa_rig_0220690_0019 CPU Time: 24.20 Elapsed Time: 24.51 Points: 64.8 Points per Hour: 2.68 The "normal" points per hour on this machine for a FAHV unit is usually substantially greater than 30. Whew ! These must be especially hard to crunch. I can see why why they would run a massive amount of time on an android unit. Cheers
Sgt. Joe
----------------------------------------*Minnesota Crunchers* [Edit 1 times, last edit by Sgt.Joe at Sep 6, 2014 12:21:02 PM] |
||
|
|
Eric_Kaiser
Veteran Cruncher Germany (Hessen) Joined: May 7, 2013 Post Count: 1047 Status: Offline Project Badges:
|
The queue for android vina seems to run dry. Some of my devices don't receive any new wu.
---------------------------------------- |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Sure you have changed you 'beta' profile. That flow suddenly dried up today, so allowed fahv again and got my 1.5 days worth. The pc on linux is getting them fine too, albeit, the balance stags still in favor of faah. It's chewing on the last 3 big x3vq. One is on 49 percent after 13 hours.
----------------------------------------[Edit 1 times, last edit by Former Member at Sep 18, 2014 8:34:31 AM] |
||
|
|
Eric_Kaiser
Veteran Cruncher Germany (Hessen) Joined: May 7, 2013 Post Count: 1047 Status: Offline Project Badges:
|
I double checked this. I switched the devices back to the profile that allows 'normal' work.
----------------------------------------One device has 4 in progress and 8 waiting (4 cores). The second device has 1 in progress and doesn't get any more (4 cores). The third device has none and doesn't get any (2 cores). No work available. All three devices use the same profile. The fourth device is continuing work for another project for a couple of days but is allowed to do beta testing. It is planned to be back for wcg in 2-3 weeks (4 cores). The fifth device (my smartphone) will go offline. I used it only for supporting beta. It's only a temporary boinc device. [Edit 2 times, last edit by Eric_Kaiser at Sep 18, 2014 9:28:20 AM] |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
There's vina for android alright, boatloads of the x3vq that no mobile owner wants or could process in time. Send these all back, noting the suffixes to include _9, _10 and _11, the end of the lemming off the cliff lane.
World Community Grid 7.16 fahv FAHV_x3VQ7_IN_FBPb_rig_0220468_0028_10 00:00:00 (00:00:00) 9/18/2014 12:51:50 PM 9/18/2014 12:53:51 PM 0,00 Aborted (203) Tablet-01 World Community Grid 7.16 fahv FAHV_x3VQ7_IN_FBPb_rig_0220428_0008_6 00:00:00 (00:00:00) 9/18/2014 12:51:50 PM 9/18/2014 12:53:51 PM 0,00 Aborted (203) Tablet-01 World Community Grid 7.16 fahv FAHV_x3VQ7_IN_FBPb_rig_0220435_0049_7 00:00:00 (00:00:00) 9/18/2014 12:51:50 PM 9/18/2014 12:53:51 PM 0,00 Aborted (203) Tablet-01 World Community Grid 7.16 fahv FAHV_x3VQA_IN_FBPa_rig_0222219_0032_8 00:00:00 (00:00:00) 9/18/2014 12:48:49 PM 9/18/2014 12:51:50 PM 0,00 Aborted (203) World Community Grid 7.16 fahv FAHV_x3VQ7_IN_FBPb_rig_0220538_0019_6 00:00:00 (00:00:00) 9/18/2014 12:48:49 PM 9/18/2014 12:51:50 PM 0,00 Aborted (203) World Community Grid 7.16 fahv FAHV_x3VQ5_A_IN_LEDGFb_rig_0220022_0059_8 00:15:44 (00:14:08) 9/18/2014 11:58:29 AM 9/18/2014 12:01:31 PM 89,83 Aborted (203) World Community Grid 7.16 fahv FAHV_x3VQ5_A_IN_LEDGFb_rig_0220040_0026_10 00:00:00 (00:00:00) 9/18/2014 11:58:29 AM 9/18/2014 12:01:31 PM 0,00 Aborted (203) World Community Grid 7.16 fahv FAHV_x3VQ5_A_IN_LEDGFb_rig_0220065_0061_9 00:00:00 (00:00:00) 9/18/2014 11:58:29 AM 9/18/2014 12:01:31 PM 0,00 Aborted (203) World Community Grid 7.16 fahv FAHV_x3VQ5_A_IN_LEDGFb_rig_0220089_0058_11 00:00:00 (00:00:00) 9/18/2014 11:58:29 AM 9/18/2014 12:01:31 PM 0,00 Aborted (203) World Community Grid 7.16 fahv FAHV_x3VQA_IN_LEDGFa_rig_0222584_0008_10 07:45:31 (07:13:54) 9/18/2014 11:42:15 AM 9/18/2014 11:44:26 AM 93,21 Aborted (203) |
||
|
|
|