The x2 quorum is here to stay, there are not any plans to remove it or how to properly validate the results if it was removed. Since these are all unique comparisons being made, sometimes over 3.6 billion comparisons in a work unit it would be hard to verify that a single run of one was proper.

The expected runtime for each work unit is to average around 3 hours. This is for the entire grid average. We did some shuffling of the genes in the files to help randomize what genome sequences are next to each other. In theory this will help level out the runtimes and the output sizes.

The 7 day deadline is here to stay as well, we may adjust that in the future, but since the results can be decent size, we need to have a 7 day deadline to help the storage on the backend from getting filled up. Again if situations change then we may modify this, it is just a setting where x2 quorum is a major code change. We are targetting a 3 hour average on the grid right now, which is pretty small and the workunits will checkpoint at every chance they can (BOINC settings).

I have not run the script that opts members in to new projects. This is a script that has not been run since our last project launch and I need to confirm that everythign for it is in order. Since our last project launch we changed how the database field for project preferences is stored, thus I am testing it extensively.

......we are running the project at Lowest priority allowed that has monitoring associated with it on the backend. Basically every 5 seconds the feeder tries to fill up the buffer, but if someone with a request for 50 work units comes along, they may suck it dry for that 5 seconds. We have plenty of work for the project lined up, but we need to see the impact of the new project with storage aspects on the backend, thus the lowest priority (weight) in the the feeder.