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: 8
|
![]() |
Author |
|
Sekerob
Ace Cruncher Joined: Jul 24, 2005 Post Count: 20043 Status: Offline |
We've seen it on HDC, on HPF1 and it continues on HCMD Phase 1 and GC.... the Work Units keep trickling in relentlessly every single day since the announcements were circulated that projects closed:
----------------------------------------Yesterday Genome Comparison 0:000:12:25:32 232 8 - Officially Closed July 21,2007 Help Cure Muscular Dystrophy 0:001:09:30:23 906 9 - Closed June 2007 (Phase I) Clearly the work is already covered by other computers processing replicas done through the WU time out system. Almost doubtlessly UD Agent results with BOINC having a expiration warning system, these crunchers switch on their clients probably after an extended hiatus and continue where they left off. But, how do we get the message across that the best thing is to abort the job thru the Operating systems task or process manager and terminating the WCG_xxxxxxxxx.exe process. Since August 15, following results were returned and gone to the bin, WCG committed to credit the time crunching regardless. Genome Comparison - 423 Help Cure Muscular Dystrophy - 357 Tell a friend, tell a team home forum, Ideas?
WCG
Please help to make the Forums an enjoyable experience for All! |
||
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
We've seen it on HDC, on HPF1 and it continues on HCMD Phase 1 and GC.... the Work Units keep trickling in relentlessly every single day since the announcements were circulated that projects closed: Yesterday Genome Comparison 0:000:12:25:32 232 8 - Officially Closed July 21,2007 Help Cure Muscular Dystrophy 0:001:09:30:23 906 9 - Closed June 2007 (Phase I) Clearly the work is already covered by other computers processing replicas done through the WU time out system. Almost doubtlessly UD Agent results with BOINC having a expiration warning system, these crunchers switch on their clients probably after an extended hiatus and continue where they left off. But, how do we get the message across that the best thing is to abort the job thru the Operating systems task or process manager and terminating the WCG_xxxxxxxxx.exe process. Since August 15, following results were returned and gone to the bin, WCG committed to credit the time crunching regardless. Genome Comparison - 423 Help Cure Muscular Dystrophy - 357 Tell a friend, tell a team home forum, Ideas? Instead of BOINC simply warning that your WU is past its due date and you may not receive credit for it, have BOINC forcibly abort any outdated WUs by default? |
||
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
These are probably UD results, since BOINC already warns about work that will miss the deadline. Also, the new BOINC version has the ability to abort work under certain circumstances.
Personally, I don't think it matters. The UD agent will be gone soon enough anyway. |
||
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
These are probably UD results, since BOINC already warns about work that will miss the deadline. Also, the new BOINC version has the ability to abort work under certain circumstances. I am sure there are many, many users who never look at the messages section of BOINC to even notice the warning. What are the circumstances when it can abort? |
||
|
Sekerob
Ace Cruncher Joined: Jul 24, 2005 Post Count: 20043 Status: Offline |
I dont know how the message could be missed.
----------------------------------------1. I thought I was fairly clear it related to UD, not BOINC, but I failed to convey that somehow. 2. BOINC jobs have build in time outs much much shorter, like 3 weeks calendar, 2 weeks CPU. In fact made a post in the FAQ section to say that HPF2 times out now at 6x estimated flops. I'll retire for the day and enjoy the earthy tasting Cantina Tollo, Robino Secco, as nice as some more costly Chileans.
WCG
Please help to make the Forums an enjoyable experience for All! |
||
|
JmBoullier
Former Community Advisor Normandy - France Joined: Jan 26, 2007 Post Count: 3715 Status: Offline Project Badges: ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
As far as HCMD WUs are concerned talking of Boinc is strictly irrelevant since HCMD was UD only.
----------------------------------------Regarding trying to reach those people who are most probably never or very rarely using forums it is probably "Mission: impossible", except that we are in real life and that impossible here really means impossible. The only serious opportunity ever to move things for these members will be the next emailed newsletter announcing the end of the old projects, the new projects, the end of the UD agent and the long awaited automated procedure for migrating from UD to Boinc automatically. Until then there is little motivation for trying to push people to install a soon obsolete version of Boinc with all possible migration trouble. In my team (no dedicated forum, very few readers of the team thread here) only 13 % of all members have installed Boinc, and the majority of active Boinc crunchers are new members who have joined directly with Boinc. Cheers. Jean. |
||
|
twilyth
Master Cruncher US Joined: Mar 30, 2007 Post Count: 2130 Status: Offline Project Badges: ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
I'm not sure when the last newsletter went out, but I think it was way back in June. I think it would help matters considerably if WCG could send out more frequent newsletters - keeping them fairly brief with links for additional information on a give topic. If you don't even try to contact people for 2 or 3 months at a time, it's no surprise that the work they're machines are doing just becomes part of their daily landscape. I think sending out something every week or two is feasible and avoids overloading people with a lot of new information at once. That's especially true for the boinc migration. A lot of people who never even looked at the forums will be here with all sorts of questions. Maybe there isn't any real news on a weekly or biweekly basis, but in those cases you can highlight things you want people to remember - like checking for error messages. It will also reduce the number of bounced emails. If people are hearing from you on a regular basis, they're more likely to log in and update their email address when it changes.
----------------------------------------![]() ![]() |
||
|
knreed
Former World Community Grid Tech Joined: Nov 8, 2004 Post Count: 4504 Status: Offline Project Badges: ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
Actually a newsletter is in the work and will come out sometime in the next two weeks. We wanted to send it a month ago but the work for the Discovering Dengue Drugs - Together and AfricanClimate@Home kept us too busy. Now that things are starting to settle down we are getting the newsletter ready.
In regards to some of the questions above about how BOINC will abort off late workunits (yes - this is off topic since Sekerob's earlier post was about UD). This works with two options turned on: 1) The server sends a message to the clients asking the client to check in no later then three days after its previous communication with the server. There are many reasons why this will happen more frequently then this, but in the worst case three days is the upper limit. 2) If a workunit is canceled, deleted on the server (after being assimilated and moved into the queue to be sent back to the scientists), or the information about the workunit is no longer in the database, then the server will send the abort message to the client. These two things work together to handle the case where someone goes on vacation and shuts off their computer for a week. As soon as they turn their computer back on, condition #1 engages and the client talks to the server. The server will then tell the client to abort a number of the results and the client will then start working on new work. |
||
|
|
![]() |