The Site > Old Forums > Team RC5 > don't want OGR

don't want OGR

In the config, you have to go to the load work precedence setting, and set it to OGR=0.

(option (2) Buffer and Buffer Update Options. Then click on option (9) Load-work precedence. Under New Setting enter the following: RC5-72,OGR-P2=0 and then go back to main menu.)

Thanks a lot. I suppose no one is writing apps for this at all anymore. Again thanks.

I'm not sure anyone ever created any sort of fancy GUI for it. We've always run it off a shell, and in the background.

With the -install command?

reply to DaMan666
What is wrong with the OGR? Since one OGR just finished I like to start projects that can be completed in my lifetime unlike RC encryption :-p

Whatdo you mean. Jst look at this progress meter.
»stats.distributed.net/projects.p···ect_id=8

I think other people have the same idea.
»stats.distributed.net/projects.p···ct_id=26

The new OGR-26 is already 70% done. If there are no other projects after then then I am installing »en.wikipedia.org/wiki/World_Community_Grid
»en.wikipedia.org/wiki/Folding@home

Or Maybe help the end of the world with the Large Hadron Collider project
»lhcathome.cern.ch/

said by DaMan666:

Whatdo you mean. Jst look at this progress meter.
»stats.distributed.net/projects.p···ect_id=8

OGR-25 ended within our lifetimes...

OGR-NG is going to end within our lifetimes...

And then they will bring on OGR-27 which undoubtedly will end within our lifetimes, but will be a much more aggressive one than the NG project. NG was really just to try out the new algorithms and make sure everything is/was going okay.

Maybe you will get a shot at boinc one of these years in the distributed.net efforts, but they have said that the traditional client will continue as well.

As for long projects, you probably really mean RC5-72, which will go on for a max of six hundred plus years at present rates. However, that was before the CUDA clients started coming into play. Beta3 is now out for the rc5-72 CUDA fans, both in Linux and windows. The speed on them is phenomenal compared to the standard cpu. So for arguments sake, it is probable that the CUDA client could reduce that by a factor of 10. That's now, it will continue to drop. The work now is going in to increasing the size (variable) of the work unit in order to better utilize the crunching power of the gpu. There is a (relatively speaking of course) huge amount of time spent setting up the unit for crunching and shutting it down, for each work unit. The intent is to keep the gpu crunching more efficiently by increasing the size of the work unit and reducing the wasted setup time. That will considerably alter the rapidity of work being completed.

And while some may say that the RC5-72 project is a waste now that the answer is known, it is providing some valuable gpu programming experience for some people that will be very beneficial to distributed.net's future gpu endeavors.

So actually it's all pretty cool in it's own way.