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: 1
|
![]() |
Author |
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Cruncher-selectables for:
----------------------------------------1] maxCrunchTimes: -- 1hr, 2hrs, 4hrs, 8hrs, 12hrs, 16hrs, 20hrs. -- 1day, 2days, 3days, 4days, 5days, 6days, 7days. 2] project relativeWeights Rationale: 1] A 16hrs crunchTime, for example, that may be opted by a group of crunchers may be considered as way too long for another group of crunchers. There is no such thing as a "best crunchTime" that every cruncher would be happy to crunch by, nor for the application to be coded to aim for. Rather than work out a "reasonable compromise" (science needs versus cruncher needs), let the science select (and optimize for) their target crunchTime and for crunchers to choose. No need for the science and the crunchers to wear the same one-size-fits-all crunchTime shirt. 2] A group of crunchers wanting to focus on, for example, cancer-related WUs may want to spread the crunchTime equally on all cancer-related projects while others may want, say: 10% on HFCC, 50% on C4CW, and 40% on DSFL. The current method that roughly effects the same result -- is to go on exclusiveMode: select one project, track the runtimes/badges there, and switch to another project as soon as a desired objective is reached for the current exclusive project, de-select that project, and repeat the steps for another project. That is tedious and inefficient. Notes: 1] The existing ways are not lost. WCG would simply put a "(recommended)" next to the selectables that best matches the existing way. Thus, for the current C4CW, the option -- "maxCrunchTime: 4hrs (recommended)" -- best reflects C4CW's existing crunchTime. 2] There is also proposed, a "random" option or the "come what may" option. Here, the science is given a free reign to use whatever amount of runtime it sees fit. Some crunchers may be happy to join in. 3] The granularity of the options may not be critical. The used granularity in the example above is for demonstration purposes only. ; [Edit 1 times, last edit by Former Member at Sep 9, 2011 12:19:20 PM] |
||
|
|
![]() |