Hi Nasher, all the answers are in the preceding pages, but simply, what seems to work most of the time is:

1) top up your queue with WUs for another project like MCM or UGM by forcing a manual update
2) increase your cache size:
Tools -> Computing Preferences -> Network usage -> Minimum Work Buffer - suggest 2 days
3) change device profile to accept only OET WUs

The OET WUs are released in small batches at variable times, so you will get some if and only if your client performs an update during the small window of availability, which triggers periodically by itself but much more frequently if you are returning results. Thus, there is a large element of luck involved and you will most likely not get as many OET WUs as you need to sustain your progress. Thus, as your queue runs low, reverse steps 3 and 2 above, then repeat 1, 2 and 3 :) You will never get more than 25 WUs allocated per core as this is a hard limit imposed by the server.

wow, FINALLY after loading a day of UGM, and switching to ebola solo, Finally get some work units (about 8)...took 3 days
Oh well, maybe i should just leave both selected and not sweat it until the main units come out.
Still need a year and a half for UGM. (or 9.5 for my 10 year goal)

gb... yeah, I had 15 of those OET WUs in PV jail that somebody had in "In Progress" for 5 days !!! Fortunately, yesterday they started to get processed and now I only have 7 waiting to be dispatched. Makes you wonder....

CJSL

Crunching for a better world...

cant agree more

Just one "stupid" question:
Why are members so upset because of the small number of available tasks?
imho:

• OET1 does not lock any resources for other projects. If no task is available, the other projects can take advantage from the available computational resources.
  
• It seems that we are only in the early project phase, consequently, more task will be available later.
  
• By some projects, some tasks must be computed before the rest of the project work can be generated; in this particular case, it seems that OET1 is such a project.
  
• The launch of a new project is often linked to some starting challenges. We used to make such experiences from time to time. Since there were only few new projects during the last 2 years, maybe members miss to remember.

Communication to the members can always be improved. However, regarding OET1, it seems that WCG staff is not the cause for the few available tasks. Furthermore, the project scientists have to generate the work. I think that we need to remain fair and we should stop to complain against WCG respectively WCG staff.

In all cases, members should not forget that they participate as volunteers for supporting science AND science needs time .
In other words, members should be patient, since there is anyway other WCG projects to support.

I wish you all, and your Families as well, a happy Christmas time.
Cheers,
Yves