The goal is that a BOINC server with the default settings should address these issues in a way appropriate to a production project: - validation - credit granting - job runtime estimation - assignment of deadlines
Of course, everything can be overridden, but this should be the exception rather than the rule. Expecting project admins to understand a bunch of complex issues and sift through mountains of configuration options has, I think, significantly limited the adoption of BOINC by scientists. -- David Lynn W. Taylor wrote: > I have only one question: > > Is BOINC responsible for keeping the projects from doing stupid things > (unreasonable deadlines, unique credit practices, replication of 1), or > should BOINC provide tools and suggest good practices and then leave it > to the projects. _______________________________________________ boinc_dev mailing list [email protected] http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, visit the above URL and (near bottom of page) enter your email address.
