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: 90
Posts: 90   Pages: 9   [ Previous Page | 1 2 3 4 5 6 7 8 9 | Next Page ]
[ Jump to Last Post ]
Post new Thread
Author
Previous Thread This topic has been viewed 394003 times and has 89 replies Next Thread
KerSamson
Master Cruncher
Switzerland
Joined: Jan 29, 2007
Post Count: 1670
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: FightAIDS@Home Beta Test Feb 13, 2013 (Issues Thread)

Hi,
I am a little bit surprised. Several WUs have been aborted by server during the work and not before starting.
I know that this Beta is running with a Quorum 2, but I do not really appreciate that WUs become aborted during the work is being done.
By the way, my current queue is not very big (usually <2 days) and I do force the start of beta WUs as soon as I notice them.
Cheers,
Yves
----------------------------------------
----------------------------------------
[Edit 1 times, last edit by KerSamson at Feb 15, 2013 4:21:48 PM]
[Feb 15, 2013 4:20:25 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 Beta Test Feb 13, 2013 (Issues Thread)

KerSamson,

There's 2 types of server abort...

1) When the task is redundant, not yet started
2) Started, but bad task/batch.

Plz confirm that the quorum was reached and validated as the reading of your post does not permit to take that as done.
[Feb 15, 2013 4:41:05 PM]   Link   Report threatening or abusive post: please login first  Go to top 
KerSamson
Master Cruncher
Switzerland
Joined: Jan 29, 2007
Post Count: 1670
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: FightAIDS@Home Beta Test Feb 13, 2013 (Issues Thread)

Hi Rob,
I am not baby sitting the hosts.
But usually, in case of server abort before the WU computation is started, there is no claim.
In the specific cases of the last two days, several times the hosts claimed some credit.
Additionally, I know that I forced the start of several beta WUs that seem to not be completed.
Yves
----------------------------------------
[Feb 15, 2013 8:42:06 PM]   Link   Report threatening or abusive post: please login first  Go to top 
de291@comcast.net
Cruncher
USA
Joined: Dec 8, 2008
Post Count: 36
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: FightAIDS@Home Beta Test Feb 13, 2013 (Issues Thread)

I have completed 6 Betas which seemed to run just fine but report Error in results and running 3 more now.
Mac OS X 10.8.2 BOINC 7.0.31
----------------------------------------
David

----------------------------------------------------------------------------------------------------------------------------

[Feb 15, 2013 9:04:03 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 Beta Test Feb 13, 2013 (Issues Thread)

Earlier, I reported in this thread that I received 7 FAAH Beta WU's, 6 ran on on my two F-18-x86_64 and one on my F-17-i386 laptop. All 7 validated and points awarded but the 6 that ran on the 64 bit machines all reported zero cpu hours with a total of 28.57 calender hours expended. So far, the only time I have been credited for this beta run is the 13.37 cpu hours expended on the i386 laptop. Might this be due with the application's inability to parse the init_data.xml file due to no end tag as noted in the stderr.txt output copied below from one of the 6 WU's in question. Does this mean I will loose the approximately 28 hours run time invested?

Result Log

Result Name: BETA_ faah38222_ ZINC14140957_ xPR_ wC6_ 11_ 1ref9_ 01_ 2--
<core_client_version>7.0.29</core_client_version>
<![CDATA[
<stderr_txt>
parse_init_data_file: no end tag
13:57:04 (13108): Can't parse init data file - running in standalone mode
INFO:[13:57:04] Start AutoGrid...

autogrid4: Successful Completion.
INFO:[13:59:02] End AutoGrid...
INFO:[13:59:02] Start AutoDock...
INFO: In AutoDock main_autodock()
Beginning AutoDock...
INFO: Setting num_generations: 10000
About to enter main loop...(dockings already completed: 0)
_maxGenSeenSoFar changed: 2500
_maxGenSeenSoFar changed: 2626
_maxGenSeenSoFar changed: 2758
_maxGenSeenSoFar changed: 2896
_maxGenSeenSoFar changed: 3041
_maxGenSeenSoFar changed: 3194
_maxGenSeenSoFar changed: 3354
_maxGenSeenSoFar changed: 3522
_maxGenSeenSoFar changed: 3699
_maxGenSeenSoFar changed: 3885
_maxGenSeenSoFar changed: 4080
_maxGenSeenSoFar changed: 4285
_maxGenSeenSoFar changed: 4500
_maxGenSeenSoFar changed: 4726
_maxGenSeenSoFar changed: 4963
_maxGenSeenSoFar changed: 5212
_maxGenSeenSoFar changed: 5473
_maxGenSeenSoFar changed: 5747
_maxGenSeenSoFar changed: 6035
_maxGenSeenSoFar changed: 6337
_maxGenSeenSoFar changed: 6654
_maxGenSeenSoFar changed: 6987
_maxGenSeenSoFar changed: 7337
_maxGenSeenSoFar changed: 7704
_maxGenSeenSoFar changed: 8090
_maxGenSeenSoFar changed: 8495
_maxGenSeenSoFar changed: 8920
_maxGenSeenSoFar changed: 9367
_maxGenSeenSoFar changed: 9836
_maxGenSeenSoFar changed: 10328
Updating Best Energy for WU: 0.00
Finished Docking number 0
parse_init_data_file: no end tag
14:12:47 (13318): Can't parse init data file - running in standalone mode
Restoring grahics. bestEnergy: -8.423280 maxGenSeen: 10328
AG Check: Found receptor.A.map
INFO:[14:12:47] Start AutoDock...
INFO: In AutoDock main_autodock()
Beginning AutoDock...
INFO: Setting num_generations: 10000
About to enter main loop...(dockings already completed: 1)
Updating Best Energy for WU: -8.42
Finished Docking number 1
Finished Docking number 2
Finished Docking number 3
Finished Docking number 4
Finished Docking number 5
Finished Docking number 6
Finished Docking number 7
Finished Docking number 8
Updating Best Energy for WU: -9.91
Finished Docking number 9
Finished Docking number 10
Finished Docking number 11
Finished Docking number 12
Finished Docking number 13
Finished Docking number 14
Finished Docking number 15
Finished Docking number 16
Finished Docking number 17
Finished Docking number 18
Finished Docking number 19
Finished Docking number 20
Finished Docking number 21
Finished Docking number 22
Finished Docking number 23
Finished Docking number 24
Finished Docking number 25
Finished Docking number 26
Finished Docking number 27
Finished Docking number 28
Finished Docking number 29
Finished Docking number 30
Updating Best Energy for WU: -10.03
Finished Docking number 31
Finished Docking number 32
Finished Docking number 33
Finished Docking number 34
Finished Docking number 35
Finished Docking number 36
INFO:[20:19:01] End AutoDock...
INFO:[20:19:02] Start AutoGrid...

autogrid4: Successful Completion.
INFO:[20:19:31] End AutoGrid...
INFO: In AutoDock main_autodock()
Beginning AutoDock...
INFO: Setting num_generations: 27000
About to enter main loop...(dockings already completed: 37)
Finished Docking number 0
20:20:13 (13318): called boinc_finish

</stderr_txt>
]]>
[Feb 15, 2013 9:43:18 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 Beta Test Feb 13, 2013 (Issues Thread)

Hi Rob,
I am not baby sitting the hosts.
But usually, in case of server abort before the WU computation is started, there is no claim.
In the specific cases of the last two days, several times the hosts claimed some credit.
Additionally, I know that I forced the start of several beta WUs that seem to not be completed.
Yves

The cases of not-started, server aborted Betas I've had, showed a claim, no computation time, which as earlier discussed in this thread goes out without any log entry in a v7 client, and misreporting as "error" rather than server aborted [code 202]:

BETA_ faah38223_ ZINC04919667_ xPR_ wC6_ 11_ 1ref9_ 00_ 1-- 1854592 Error 15-2-2013 7:58:00 15-2-2013 6:16:53 0,00 123,5 12,51 BETA Windows 7 - 64 I7-2670QM 2700 14-2-2013 17:46:32 0,00

The techs would have to tell if they forced aborts of already started [beta] tasks that were not bad. It would be against prior established practice.
[Feb 15, 2013 10:05:54 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 Beta Test Feb 13, 2013 (Issues Thread)

Earlier, I reported in this thread that I received 7 FAAH Beta WU's, 6 ran on on my two F-18-x86_64 and one on my F-17-i386 laptop. All 7 validated and points awarded but the 6 that ran on the 64 bit machines all reported zero cpu hours with a total of 28.57 calender hours expended. So far, the only time I have been credited for this beta run is the 13.37 cpu hours expended on the i386 laptop. Might this be due with the application's inability to parse the init_data.xml file due to no end tag as noted in the stderr.txt output copied below from one of the 6 WU's in question. Does this mean I will loose the approximately 28 hours run time invested?

Result Log

Result Name: BETA_ faah38222_ ZINC14140957_ xPR_ wC6_ 11_ 1ref9_ 01_ 2--
<core_client_version>7.0.29</core_client_version>
<![CDATA[
<stderr_txt>
parse_init_data_file: no end tag
13:57:04 (13108): Can't parse init data file - running in standalone mode
INFO:[13:57:04] Start AutoGrid...

autogrid4: Successful Completion.
INFO:[13:59:02] End AutoGrid...
INFO:[13:59:02] Start AutoDock...
INFO: In AutoDock main_autodock()
Beginning AutoDock...
INFO: Setting num_generations: 10000
About to enter main loop...(dockings already completed: 0)
_maxGenSeenSoFar changed: 2500
_maxGenSeenSoFar changed: 2626
...
INFO:[20:19:01] End AutoDock...
INFO:[20:19:02] Start AutoGrid...

autogrid4: Successful Completion.
INFO:[20:19:31] End AutoGrid...
INFO: In AutoDock main_autodock()
Beginning AutoDock...
INFO: Setting num_generations: 27000
About to enter main loop...(dockings already completed: 37)
Finished Docking number 0
20:20:13 (13318): called boinc_finish

</stderr_txt>
]]>

Fear the time is lost. Not saying it's your quite alpha 7.0.29 client [what OS? Linux?], but my 7.0.39 64 bit Linux and 7.0.52 64 bit W7 did not log a "can't parse...", clean log, time properly recorded on all 14 results.
[Feb 15, 2013 10:30:06 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 Beta Test Feb 13, 2013 (Issues Thread)

Rats, I was afraid of loosing the time. All OS's are Fedora and the 7.0.29 client came from the Fedora repo's. Thanks for the reply Sek.
[Feb 15, 2013 11:49:47 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 Beta Test Feb 13, 2013 (Issues Thread)

by my observation new BETA WUs are at least 3 times slower than usual FAAH WUS

my core2duo core finishes a FAAH WU in around 5 hours, but with these betas it done around 12% in 2 hours


Yes, these are huge. My Celeron 2.53 grabbed a couple:
17.67 hours
19.23 hours

Core2duo laptop would be about the same if running full speed, but as I run it slow to keep it cool: 31.65 hours.
[Feb 16, 2013 2:22:25 AM]   Link   Report threatening or abusive post: please login first  Go to top 
ca05065
Senior Cruncher
Joined: Dec 4, 2007
Post Count: 325
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: FightAIDS@Home Beta Test Feb 13, 2013 (Issues Thread)

I have noticed an oddity where two work units were declared valid but had processed different number of dockings.

BETA_ faah38222_ ZINC09364504_ xPR_ wC6_ 11_ 1ref9_ 00_ 3-- 711 Valid 2/13/13 23:43:51 2/14/13 13:43:08 5.49 169.5 / 187.4
BETA_ faah38222_ ZINC09364504_ xPR_ wC6_ 11_ 1ref9_ 00_ 1-- 711 Valid 2/13/13 23:32:26 2/15/13 13:12:29 9.09 205.3 / 187.4
BETA_ faah38222_ ZINC09364504_ xPR_ wC6_ 11_ 1ref9_ 00_ 2-- 711 Error 2/13/13 23:32:10 2/13/13 23:43:28 0.00 63.5 / 0.0
BETA_ faah38222_ ZINC09364504_ xPR_ wC6_ 11_ 1ref9_ 00_ 0-- 711 Server Aborted 2/13/13 23:32:02 2/15/13 16:03:06 0.00 130.4 / 0.0

mine:

Result Log

Result Name: BETA_ faah38222_ ZINC09364504_ xPR_ wC6_ 11_ 1ref9_ 00_ 3--
<core_client_version>7.0.36</core_client_version>
<![CDATA[
<stderr_txt>
INFO:[07:06:09] Start AutoGrid...

autogrid4: Successful Completion.
INFO:[07:07:13] End AutoGrid...
INFO:[07:07:13] Start AutoDock...
INFO: In AutoDock main_autodock()
Beginning AutoDock...
INFO: Setting num_generations: 10000
About to enter main loop...(dockings already completed: 0)
_maxGenSeenSoFar changed: 2500
_maxGenSeenSoFar changed: 2626
_maxGenSeenSoFar changed: 2758
_maxGenSeenSoFar changed: 2896
.
. lines removed
.
_maxGenSeenSoFar changed: 8090
_maxGenSeenSoFar changed: 8495
_maxGenSeenSoFar changed: 8920
_maxGenSeenSoFar changed: 9367
_maxGenSeenSoFar changed: 9836
_maxGenSeenSoFar changed: 10328
Updating Best Energy for WU: 0.00
Finished Docking number 0
Updating Best Energy for WU: -6.92
Finished Docking number 1
Finished Docking number 2
Finished Docking number 3
Finished Docking number 4
Finished Docking number 5
Updating Best Energy for WU: -7.16
Finished Docking number 6
Finished Docking number 7
Updating Best Energy for WU: -7.34
Finished Docking number 8
Finished Docking number 9
.
. lines removed
.
Finished Docking number 45
Finished Docking number 46
Finished Docking number 47
Finished Docking number 48
Finished Docking number 49
Finished Docking number 50
Updating Best Energy for WU: -7.40
Finished Docking number 51
Finished Docking number 52
Finished Docking number 53
Finished Docking number 54
Finished Docking number 55
Finished Docking number 56
Finished Docking number 57
Finished Docking number 58
Finished Docking number 59
Finished Docking number 60
Finished Docking number 61
Finished Docking number 62
INFO:[12:35:46] End AutoDock...
INFO:[12:35:46] Start AutoGrid...

autogrid4: Successful Completion.
INFO:[12:36:01] End AutoGrid...
INFO: In AutoDock main_autodock()
Beginning AutoDock...
INFO: Setting num_generations: 27000
About to enter main loop...(dockings already completed: 63)
Finished Docking number 0
12:36:33 (2228): called boinc_finish

</stderr_txt>
]]>


other valid:

Result Log

Result Name: BETA_ faah38222_ ZINC09364504_ xPR_ wC6_ 11_ 1ref9_ 00_ 1--
<core_client_version>7.0.28</core_client_version>
<![CDATA[
<stderr_txt>
INFO:[16:07:50] Start AutoGrid...

autogrid4: Successful Completion.
INFO:[16:11:22] End AutoGrid...
INFO:[16:11:22] Start AutoDock...
INFO: In AutoDock main_autodock()
Beginning AutoDock...
INFO: Setting num_generations: 10000
About to enter main loop...(dockings already completed: 0)
_maxGenSeenSoFar changed: 2500
_maxGenSeenSoFar changed: 2626
_maxGenSeenSoFar changed: 2758
_maxGenSeenSoFar changed: 2896
.
. lines removed
.
_maxGenSeenSoFar changed: 8090
_maxGenSeenSoFar changed: 8495
_maxGenSeenSoFar changed: 8920
_maxGenSeenSoFar changed: 9367
_maxGenSeenSoFar changed: 9836
_maxGenSeenSoFar changed: 10328
Updating Best Energy for WU: 0.00
Finished Docking number 0
Updating Best Energy for WU: -6.92
Finished Docking number 1
Finished Docking number 2
Finished Docking number 3
Finished Docking number 4
Finished Docking number 5
Updating Best Energy for WU: -7.16
Finished Docking number 6
Finished Docking number 7
Updating Best Energy for WU: -7.34
Finished Docking number 8
Finished Docking number 9
.
. lines removed
.
Finished Docking number 45
Finished Docking number 46
Finished Docking number 47
Finished Docking number 48

</stderr_txt>
]]>
[Feb 16, 2013 10:52:20 AM]   Link   Report threatening or abusive post: please login first  Go to top 
Posts: 90   Pages: 9   [ Previous Page | 1 2 3 4 5 6 7 8 9 | Next Page ]
[ Jump to Last Post ]
Post new Thread