You have little control over what specific projects are assigned for a particular HW set. The best you've got is varying the client-type variable and that really does not do what you want but it will allow you to vary the pool of projects from which you will get assigned one. There are individuals that chase points by constantly moving from pool to pool finding the one with the best projects or avoiding the one currently having the lowest PPD projects. Projects frequently move between the different risk pools with the general direction being internal->beta->advanced->general release but if a new problem is found projects can go backwards to get more testing. Projects that are based on older projects previously vetted can go through this process very quickly and other totally new projects can take a very long time to get to general release.AizenSou wrote:Could you tell how to get the right projects? I think the client fetches the project automatically for you??
Thanks in advance.
Within a client-type pool you can also add a few flags that will filter out projects. Many CPU projects will be limited to specific number of CPU cores. You eventually will be able to specify a specific disease preference but that capability is not currently enabled at the server level. At one time you could specify small, normal and big WU's for uniprocessor projects, but those settings are no longer used. There are real issues with using these types of filtering flags for you can very easily limit your projects to none available where you won't get assigned anything.
client-type has six choices: general release (no client-type defined); advanced; bigadv; beta; bigbeta; and internal. Each of those have their own set of work servers and pool of different projects. The difference between them is the amount of risk taking you are willing to accept because they are simply collections of projects that are more or less tested. The higher the risk, the more likely the project will fail giving far less points.
Internal, requires that you specify a project-key to pick a specific project and those projects generally don't give out any points but 1 point per project is common.
Beta means the project has been internally tested and is now ready for a broader audience but still quite risky and points are often off norms for they are still being fine-tuned. There is absolutely no support in the general forums for anything closed beta with even a mention of anything closed-beta gets your post edited/removed or even the thread closed and locked. If you are willing to run beta then it is recommended that you join the beta test team for that gives you access to the beta forums where all support is done but you need to be willing to accept and abide by the rules and responsibilities of being a beta tester.
bigbeta is used to select between a collection of beta bigadv projects for CPU's that currently require a minimum of 24+ CPU cores. Since bigadv is EOL (End of Life) and will end within 6 months I seriously doubt that there are any projects in this category anymore.
bigadv is used to select between a collection of projects for CPU's that currently require a minimum of 24+ CPU cores. They are EOL and will cease operation within 6 months.
Advanced means the project has completed beta testing but there still may be issues outstanding.
Then there is general release (no client-type defined) where the project has completed all testing and is considered stable and in its final state.