| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Completed Research
Forum: FightAIDS@Home Phase 2
Thread: 24 Hour Deadline too Short |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 112
|
|
| Author |
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
If you would bother to read the replys to page 1 one of this thread, you would find the answer as to why there is a 24 hour deadline.
If your computer isn't fast enough to do the WUs in the the 24 hour time frame, then find another project to run. We are here for the benefit of the researchers, not the other way around. |
||
|
|
KLiK
Master Cruncher Croatia Joined: Nov 13, 2006 Post Count: 3108 Status: Offline Project Badges: 
|
FAHB project returns partial results during calculations. So no need to to go 100%. ;)
---------------------------------------- |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
FAHB project returns partial results during calculations. So no need to to go 100%. ;) If you are talking about trickle messaging, they don't do that anymore and haven't done it since 2017 when they converted to AsyncRE. With AsyncRE, there isn't any trickle messages and no intermediate results. |
||
|
|
Sir Antony Magnus
Cruncher Joined: Feb 13, 2019 Post Count: 2 Status: Offline |
Sorry I disagree with "we are here solely for the benefit of researchers". This is a mutual game played, therefore it should have the mutual parties agree on specifics with regard to speed. My statement was cast in the hopes of landing on the researchers eyes, if you don't like what I say then move on! I have opted out of FAAH2 by the way, looked for other projects with far less demanding time schedules.
----------------------------------------[Edit 1 times, last edit by Sir Antony Magnus at Feb 24, 2019 2:44:04 AM] |
||
|
|
BladeD
Ace Cruncher USA Joined: Nov 17, 2004 Post Count: 28976 Status: Offline Project Badges: 
|
Sorry I disagree with "we are here solely for the benefit of researchers". This is a mutual game played, therefore it should have the mutual parties agree on specifics with regard to speed. My statement was cast in the hopes of landing on the researchers eyes, if you don't like what I say then move on! I have opted out of FAAH2 by the way, looked for other projects with far less demanding time schedules. You did the right thing. I'm surprised that people aren't talking about the fact that the WUs are 4x larger than when this topic was started.  |
||
|
|
GB033533
Senior Cruncher UK Joined: Dec 8, 2004 Post Count: 198 Status: Offline Project Badges: 
|
Can I just add my tuppence worth to this topic, and bump it back up the list.
----------------------------------------The 24 hours deadline is too short, and each wu I do causes anxiety about getting it returned in time (I usually miss the deadline, but still get credit as I beat the resend wu, which is a waste of time and effort for them). Even just increasing to 48 hours would be better, and reflect the increase in size.  |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Can I just add my tuppence worth to this topic, and bump it back up the list. The 24 hours deadline is too short, and each wu I do causes anxiety about getting it returned in time (I usually miss the deadline, but still get credit as I beat the resend wu, which is a waste of time and effort for them). Even just increasing to 48 hours would be better, and reflect the increase in size. I think the reason for the deadline being only 24h was mentioned in this thread several times. One computation consists of many workunits and the result of one workunits are needed to create the next. Only after a "chain" of many successive workunits is computed, there is a useful result for the researchers. That is the reason why there must be a short deadline, else it would simply take too long to get a useful result. I can understand, that it may be frustrating, if workunits do not meet the deadline. And for FAH2 this can happen regularly for computers that are not running daily for many hours, that is true. However, keep in mind that we volunteers are here to support scientific research. If there is some inconvenience involved with it, I think we should accept that, as long as there is a good reason for that. And I think with the short deadline of FAH2 this is the case. You are right, that missing deadlines can be a waste of ressources. And I think the best solution for that is, if it happens regularly, to deactivate FAH2 in your device profile. There are enough computers running 24/7, that can handle them without any problem. Let them do the work and concentrate on the projects that run fine for you... |
||
|
|
nickoli
Senior Cruncher USA Joined: Nov 28, 2005 Post Count: 167 Status: Offline Project Badges: 
|
Let's not get it twisted: we are here to assist in science, not get a shiny badge or a pat on the back. FAAH2 has a good reason for the 24 hour window. Those whose machines cannot accommodate that should simply crunch on another project. A 24 hour deadline is not completely unreasonable for the average machine (I am finishing FAAH2 WUs in 5hr.) I trust the FAAH2 team to have made this decision because it is necessary to find better molecules to combat this disease, and the workflow they outline in their latest update shows why this deadline makes sense to find better molecules even faster. It's cool that they are being so aggressive in their modeling with this linked, asynchronous approach. Kudos to FAAH2.
---------------------------------------- |
||
|
|
Jean-David Beyer
Senior Cruncher USA Joined: Oct 2, 2007 Post Count: 335 Status: Offline Project Badges:
|
I have a relatively slow machine by today's standards. A four-core 64-bit Xeon with a 1.8 GHz clock. My FAH2 work units take about 9 hours to complete. When I have enough work units, all four cores run FAH2 work units.
----------------------------------------Currently I have 5 FAH2 work units (four are running), and three HST1 work units (one about 30% complete), and some Rosetta@home work units waiting around for a spare core.  |
||
|
|
sean0118
Cruncher Australia Joined: Feb 7, 2010 Post Count: 33 Status: Offline Project Badges:
|
I think the 24h deadline is crazy, even if it's convenient for the reasons given in this thread. I will not be running FAAH2 anymore.
|
||
|
|
|