Index  | Recent Threads  | Unanswered Threads  | Who's Active  | Guidelines  | Search
 

Quick Go ยป
No member browsing this thread
Thread Status: Active
Total posts in this thread: 95
Posts: 95   Pages: 10   [ Previous Page | 1 2 3 4 5 6 7 8 9 10 | Next Page ]
[ Jump to Last Post ]
Post new Thread
Author
Previous Thread This topic has been viewed 13400 times and has 94 replies Next Thread
armstrdj
Former World Community Grid Tech
Joined: Oct 21, 2004
Post Count: 695
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: FightAIDS@Home - Phase 2 - AsyncRE - Beta Test Oct 11, 2017

That is correct additional information is needed from longer into the simulation.
Thanks,
armstrdj
[Dec 12, 2017 4:18:14 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
Re: FightAIDS@Home - Phase 2 - AsyncRE - Beta Test Oct 11, 2017

FAH2_ 9999983_ avx38789_ 000001_ 000007_ 039_ 1-- Microsoft Windows 10 Core x64 Edition, (10.00.15063.00) - In Progress 11/27/17 07:04:54 11/28/17 07:04:54 <-- resend
FAH2_ 9999983_ avx38789_ 000001_ 000007_ 039_ 0-- Microsoft Windows 10 Core x86 Edition, (10.00.14393.00) 718 Valid 11/26/17 07:04:49 11/27/17 07:08:38 23.95 <-- mine

That's relatively quick. Some of mine break through 40 hours and then there are some machines taking twice that.
FAH2_ 9999986_ avx38789_ 000001_ 000405_ 047_ 2-- Linux 4.7.6-040706-generic 718 Valid 12/12/17 06:06:10 12/13/17 09:26:01 6.18 250.3 / 232.5
FAH2_ 9999986_ avx38789_ 000001_ 000405_ 047_ 1-- Linux 2.6.18-6-686 718 Valid 12/11/17 06:06:03 12/12/17 23:23:46 40.44 232.5 / 232.5 <-- mine
FAH2_ 9999986_ avx38789_ 000001_ 000405_ 047_ 0-- Linux 4.8.0-59-generic 718 Valid 12/10/17 06:05:56 12/13/17 11:42:35 76.69 354.0 / 232.5
[Dec 14, 2017 8:55:56 PM]   Link   Report threatening or abusive post: please login first  Go to top 
adriverhoef
Master Cruncher
The Netherlands
Joined: Apr 3, 2009
Post Count: 2166
Status: Recently Active
Project Badges:
Reply to this Post  Reply with Quote 
Re: FightAIDS@Home - Phase 2 - AsyncRE - Beta Test Oct 11, 2017

Result Name: FAH2_ 9999984_ avx38789_ 000001_ 000906_ 130_ 0--
Result Name                                 OS           AVN Status Sent Time         Due / Return Time CPUh  Claimed/Grant.
FAH2_9999984_avx38789_000001_000062_137_0-- Linux Fedora 718 Valid 12/15/17 16:05:47 12/15/17 17:17:00 1.16 36.1/36.1
FAH2_9999984_avx38789_000001_000969_141_0-- Linux Fedora 718 Valid 12/18/17 15:06:08 12/18/17 16:17:55 1.16 38.6/38.6
FAH2_9999984_avx38789_000001_000461_146_0-- Linux Fedora 718 Valid 12/21/17 00:06:23 12/21/17 01:17:37 1.15 30.0/30.0
FAH2_9999984_avx38789_000001_000961_147_0-- Linux Fedora 718 Valid 12/24/17 16:06:26 12/24/17 17:17:43 1.15 29.6/29.6
FAH2_9999984_avx38789_000001_000605_160_1-- Linux Fedora 718 Valid 12/25/17 06:19:03 12/25/17 07:31:35 1.18 34.1/34.1
FAH2_9999984_avx38789_000001_000495_162_0-- Linux Fedora 718 Valid 12/27/17 06:06:35 12/27/17 07:19:42 1.14 29.4/29.4
FAH2_9999984_avx38789_000001_000263_163_0-- Linux Fedora 718 Valid 12/31/17 21:06:53 12/31/17 22:21:13 1.18 27.8/27.8
FAH2_9999984_avx38789_000001_000518_169_0-- Linux Fedora 718 Valid 1/5/18 01:07:34 1/5/18 02:20:19 1.15 29.1/29.1
FAH2_9999984_avx38789_000001_000237_173_0-- Linux Fedora 718 Valid 1/5/18 22:08:04 1/5/18 23:22:25 1.17 28.7/28.7
FAH2_9999981_avx38789_000001_000022_176_0-- Linux Fedora 718 Valid 1/6/18 12:06:40 1/6/18 13:19:22 1.17 29.1/29.1
FAH2_9999984_avx38789_000001_000886_177_0-- Linux Fedora 718 Valid 1/9/18 01:08:33 1/9/18 02:27:39 1.17 37.1/37.1
FAH2_9999984_avx38789_000001_000835_188_0-- Linux Fedora 718 Valid 1/9/18 16:07:48 1/9/18 17:19:12 1.17 27.8/27.8
FAH2_9999981_avx38789_000001_000064_194_0-- Linux Fedora 718 Valid 1/10/18 08:16:52 1/10/18 09:29:47 1.15 38.0/38.0
FAH2_9999984_avx38789_000001_000160_195_0-- Linux Fedora 718 Valid 1/17/18 03:07:36 1/17/18 04:21:47 1.15 40.5/40.5
FAH2_9999984_avx38789_000001_000821_207_0-- Linux Fedora 718 Valid 1/18/18 06:07:53 1/18/18 07:19:17 1.17 27.5/27.5
FAH2_9999981_avx38789_000001_000037_219_0-- Linux Fedora 718 Valid 2/1/18 18:05:53 2/1/18 19:05:32 0.95 37.5/37.5
FAH2_9999981_avx38789_000001_000005_226_0-- Linux Fedora 718 Valid 2/1/18 18:05:53 2/1/18 19:15:28 1.13 44.5/44.5
FAH2_9999981_avx38789_000001_000025_246_0-- Linux Fedora 718 Valid 2/4/18 22:05:59 2/5/18 00:25:00 0.95 36.7/36.7
FAH2_9999981_avx38789_000001_000014_246_0-- Linux Fedora 718 Valid 2/11/18 05:06:32 2/11/18 06:07:11 0.97 41.2/41.2
FAH2_9999981_avx38789_000001_000020_250_0-- Linux Fedora 718 Valid 2/13/18 11:06:18 2/13/18 12:05:46 0.96 39.6/39.6
FAH2_9999981_avx38789_000001_000094_272_0-- Linux Fedora 718 Valid 2/20/18 01:07:01 2/20/18 02:05:48 0.95 37.7/37.7
FAH2_9999981_avx38789_000001_000018_290_0-- Linux Fedora 718 Valid 3/1/18 23:06:53 3/2/18 00:06:33 0.95 34.7/34.7
FAH2_9999981_avx38789_000001_000062_304_0-- Linux Fedora 718 Valid 3/1/18 23:06:53 3/2/18 00:06:33 0.96 34.9/34.9

----------------------------------------
[Edit 20 times, last edit by adriverhoef at Mar 2, 2018 1:22:21 AM]
[Dec 15, 2017 7:30:04 PM]   Link   Report threatening or abusive post: please login first  Go to top 
OldChap
Veteran Cruncher
UK
Joined: Jun 5, 2009
Post Count: 978
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: FightAIDS@Home - Phase 2 - AsyncRE - Beta Test Oct 11, 2017

Started running some low power Machines that take longer than 24h to complete Betas currently.

Not an issue for normal work I think but with what I guess are resends only getting 24h.....

My question then is should I abort or will the server learn not to send
----------------------------------------

[Dec 29, 2017 3:48:09 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
Re: FightAIDS@Home - Phase 2 - AsyncRE - Beta Test Oct 11, 2017 [ Issues Thread ]

We've had a few very brief power cuts this afternoon. After the most recent (at about 18:12) an in-progress and checkpointed beta unit seems to have restarted from the beginning, rather than the checkpoint which it apparently successfully used on each previous occasion. I looked at the WU properties as soon as I noticed and saw:

FAH2_ 9999985_ avx38789_ 000001_ 000166_ 098_ 0
CPU time at last checkpoint: 05:21:42
CPU time: 05:24:10
Elapsed time: 05:28:00
Estimated time remaining: 92d 02:46:59 [!!!]
Fraction done: 0.247%
Progress rate: 6.840% per hour

For now I'm letting it run.

[Edited to add:]

I just checked on this, and it went Invalid. The result log was as follows:

<core_client_version>7.6.22</core_client_version>
<![CDATA[
<stderr_txt>
INFO: result number = 0
%IMPACT-I: Requested file to open for appending md.out Does not exist.
Opening it as a new file.
%IMPACT-I: Softcore binding energy with umax = 1000.00000
%IMPACT-I: Using AGBNP2: Analytical Generalized Born Model + Analytic
Non-Polar Hydration Model
%IMPACT-I: Hybrid potential for binding with lambda = 0.32354
agbnpf_assign_parameters(): info: attempting to load from SQL tables.
[12:11:08] INFO: Checkpointed. Progress 1000 of 30000 steps complete CPU time 1649.578125
[12:38:11] INFO: Checkpointed. Progress 2000 of 30000 steps complete CPU time 3259.625000
[13:05:08] INFO: Checkpointed. Progress 3000 of 30000 steps complete CPU time 4862.687500
[13:32:26] INFO: Checkpointed. Progress 4000 of 30000 steps complete CPU time 6486.890625
[13:59:30] INFO: Checkpointed. Progress 5000 of 30000 steps complete CPU time 8095.765625
[14:26:29] INFO: Checkpointed. Progress 6000 of 30000 steps complete CPU time 9700.250000
[14:53:28] INFO: Checkpointed. Progress 7000 of 30000 steps complete CPU time 11304.578125
[15:20:33] INFO: Checkpointed. Progress 8000 of 30000 steps complete CPU time 12913.843750
[15:47:26] INFO: Checkpointed. Progress 9000 of 30000 steps complete CPU time 14511.156250
[16:14:10] INFO: Checkpointed. Progress 10000 of 30000 steps complete CPU time 16098.375000
[16:40:58] INFO: Checkpointed. Progress 11000 of 30000 steps complete CPU time 17689.546875
[17:08:08] INFO: Checkpointed. Progress 12000 of 30000 steps complete CPU time 19301.859375
INFO: result number = 0
%IMPACT-I: Softcore binding energy with umax = 1000.00000
%IMPACT-I: Using AGBNP2: Analytical Generalized Born Model + Analytic
Non-Polar Hydration Model
%IMPACT-I: Hybrid potential for binding with lambda = 0.32354
agbnpf_assign_parameters(): info: attempting to load from SQL tables.
INFO: result number = 0
%IMPACT-I: Softcore binding energy with umax = 1000.00000
%IMPACT-I: Using AGBNP2: Analytical Generalized Born Model + Analytic
Non-Polar Hydration Model
%IMPACT-I: Hybrid potential for binding with lambda = 0.32354
agbnpf_assign_parameters(): info: attempting to load from SQL tables.
INFO: result number = 0
%IMPACT-I: Softcore binding energy with umax = 1000.00000
%IMPACT-I: Using AGBNP2: Analytical Generalized Born Model + Analytic
Non-Polar Hydration Model
%IMPACT-I: Hybrid potential for binding with lambda = 0.32354
agbnpf_assign_parameters(): info: attempting to load from SQL tables.
[18:43:27] INFO: Checkpointed. Progress 1000 of 30000 steps complete CPU time 20943.953750
[19:10:29] INFO: Checkpointed. Progress 2000 of 30000 steps complete CPU time 22534.610000
[19:37:23] INFO: Checkpointed. Progress 3000 of 30000 steps complete CPU time 24125.141250
[20:04:03] INFO: Checkpointed. Progress 4000 of 30000 steps complete CPU time 25700.625625
[20:30:43] INFO: Checkpointed. Progress 5000 of 30000 steps complete CPU time 27275.063125
[20:57:34] INFO: Checkpointed. Progress 6000 of 30000 steps complete CPU time 28866.844375
[21:24:15] INFO: Checkpointed. Progress 7000 of 30000 steps complete CPU time 30445.422500
[21:50:54] INFO: Checkpointed. Progress 8000 of 30000 steps complete CPU time 32015.781875
[22:17:44] INFO: Checkpointed. Progress 9000 of 30000 steps complete CPU time 33600.750625
[22:44:34] INFO: Checkpointed. Progress 10000 of 30000 steps complete CPU time 35183.016250
[23:11:48] INFO: Checkpointed. Progress 11000 of 30000 steps complete CPU time 36791.235000
[23:38:55] INFO: Checkpointed. Progress 12000 of 30000 steps complete CPU time 38392.469375
[00:05:41] INFO: Checkpointed. Progress 13000 of 30000 steps complete CPU time 39969.969375
[00:32:24] INFO: Checkpointed. Progress 14000 of 30000 steps complete CPU time 41549.844375
[00:59:03] INFO: Checkpointed. Progress 15000 of 30000 steps complete CPU time 43122.516250
[01:25:48] INFO: Checkpointed. Progress 16000 of 30000 steps complete CPU time 44701.516250
[01:54:38] INFO: Checkpointed. Progress 17000 of 30000 steps complete CPU time 46299.813125
[02:21:50] INFO: Checkpointed. Progress 18000 of 30000 steps complete CPU time 47904.625625
[02:49:11] INFO: Checkpointed. Progress 19000 of 30000 steps complete CPU time 49518.047500
[03:16:37] INFO: Checkpointed. Progress 20000 of 30000 steps complete CPU time 51136.750625
[03:43:51] INFO: Checkpointed. Progress 21000 of 30000 steps complete CPU time 52742.516250
[04:11:02] INFO: Checkpointed. Progress 22000 of 30000 steps complete CPU time 54345.750625
[04:38:30] INFO: Checkpointed. Progress 23000 of 30000 steps complete CPU time 55963.531875
[05:05:44] INFO: Checkpointed. Progress 24000 of 30000 steps complete CPU time 57566.735000
[05:32:58] INFO: Checkpointed. Progress 25000 of 30000 steps complete CPU time 59172.485000
[06:00:07] INFO: Checkpointed. Progress 26000 of 30000 steps complete CPU time 60775.360000
[06:27:30] INFO: Checkpointed. Progress 27000 of 30000 steps complete CPU time 62388.828750
[06:54:38] INFO: Checkpointed. Progress 28000 of 30000 steps complete CPU time 63988.906875
[07:21:53] INFO: Checkpointed. Progress 29000 of 30000 steps complete CPU time 65594.516250
[07:49:12] INFO: Checkpointed. Progress 30000 of 30000 steps complete CPU time 67204.172500
%IMPACT-I: Species 1 written to SQL file md-out1.dms
%IMPACT-I: Species 2 written to SQL file md-out2.dms
07:49:14 (2308): called boinc_finish(0)

</stderr_txt>
]]>

You can see that it restarted three times, though without time stamps it's impossible to see how far it might have got each time. It's also impossible to tell why the last time was different, or in what way it was considered invalid.

I'm not sure it's worth spending any time over. I'll put it down as JOOTT.
----------------------------------------
[Edit 1 times, last edit by Former Member at Jan 10, 2018 10:48:54 AM]
[Jan 8, 2018 6:43:18 PM]   Link   Report threatening or abusive post: please login first  Go to top 
NixChix
Veteran Cruncher
United States
Joined: Apr 29, 2007
Post Count: 1187
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: FightAIDS@Home - Phase 2 - AsyncRE - Beta Test Oct 11, 2017 [ Issues Thread ]

I seem to get FAHB beta work only when I have my FAHB-enabled profile selected, even though all profiles are enabled for beta work.

Cheers coffee
----------------------------------------

[Jan 28, 2018 5:35:52 AM]   Link   Report threatening or abusive post: please login first  Go to top 
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
Re: FightAIDS@Home - Phase 2 - AsyncRE - Beta Test Oct 11, 2017 [ Issues Thread ]

I suspect some other factors are causing that effect, like when a machine on that profile happens to request work. For the time being, you could try a profile that has just FAAH selected (along with Beta enabled) and with a slightly larger cache than usual. If you run that for most of a day, say, and only occasionally load up with another profile with a smaller cache, you should obtain more Beta units smile
[Jan 28, 2018 8:03:45 AM]   Link   Report threatening or abusive post: please login first  Go to top 
Crystal Pellet
Veteran Cruncher
Joined: May 21, 2008
Post Count: 1322
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: FightAIDS@Home - Phase 2 - AsyncRE - Beta Test Oct 11, 2017 [ Issues Thread ]

I seem to get FAHB beta work only when I have my FAHB-enabled profile selected, even though all profiles are enabled for beta work.

Cheers coffee

Beta's are sent with every profile when requesting work at the moment beta's are in the queue, but the chance to get beta's with only FAH2 selected is much bigger.
When you have a 1 day buffer with only FAH2's processing, your buffer still needs more work, cause you only get as many FAH2's as you have cores and not more.
[Jan 28, 2018 8:59:00 AM]   Link   Report threatening or abusive post: please login first  Go to top 
Seoulpowergrid
Veteran Cruncher
Joined: Apr 12, 2013
Post Count: 817
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: FightAIDS@Home - Phase 2 - AsyncRE - Beta Test Oct 11, 2017 [ Issues Thread ]

I opened the BOINC software and saw the WU
FAH2_ 9999985_ avx38789_ 000001_ 000105_ 124_ 0--
was near the end of calculations, maybe 90% or such, I'm not sure as I saw the completed percentage just back to around 60% with the Remaining Time showing --- which means the file is basically done. Another five seconds later it said the file was completed, uploaded, and Results Status page shows it as a valid WU.

As the file said it is valid I don't have a reason to doubt it, but this "twitch" near the end is something I am not used to.

Edit: Unsure if it is important, but the CPU time/Elapsed time is 3.70 / 5.82. The same machine also crunched WU FAH2_ 9999985_ avx38789_ 000001_ 001000_ 139_ 0-- and the CPU time/Elapsed time was 3.72 / 4.85. All other Beta WU's CPU/elapsed time are basically 1:1 but these two are exceptions.
----------------------------------------

----------------------------------------
[Edit 1 times, last edit by Seoulpowergrid at Jan 30, 2018 8:06:14 AM]
[Jan 30, 2018 8:03:09 AM]   Link   Report threatening or abusive post: please login first  Go to top 
NixChix
Veteran Cruncher
United States
Joined: Apr 29, 2007
Post Count: 1187
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: FightAIDS@Home - Phase 2 - AsyncRE - Beta Test Oct 11, 2017 [ Issues Thread ]

I seem to get FAHB beta work only when I have my FAHB-enabled profile selected, even though all profiles are enabled for beta work.

Cheers coffee

Beta's are sent with every profile when requesting work at the moment beta's are in the queue, but the chance to get beta's with only FAH2 selected is much bigger.
When you have a 1 day buffer with only FAH2's processing, your buffer still needs more work, cause you only get as many FAH2's as you have cores and not more.
Normally that is the case Crystal Pellet, but I stand by my observation that these betas are only going out to FAHB profiles. I am not seeing the beta sent to my machines that have a beta-enabled profile, but not FAHB. I have been watching carefully since I first noticed. I post this since the techs did not state it as part of the plan; maybe it was not intentional.

If anyone is getting FAHB beta without having FAHB selected please post a reply.

Cheers coffee
----------------------------------------

[Jan 31, 2018 4:38:29 AM]   Link   Report threatening or abusive post: please login first  Go to top 
Posts: 95   Pages: 10   [ Previous Page | 1 2 3 4 5 6 7 8 9 10 | Next Page ]
[ Jump to Last Post ]
Post new Thread