From the wingui-beta-3.02-help-file:
"With version 3.02, we are extending the chirp range analysis so that it can potentially discern signals from hypothetical satellites orbiting earth-sized extrasolar planets. This is an exciting search space never before explored."
Because of a bug in some old 1.x-clients, all current clients will be cut-off then the beta-testing for win-gui is over and new 3.x-clients is released. The chirp range will be extended in all of these new clients, and of course use longer time to process.
For an idea of time, a couple of results:
Beta 3.01: 7,5h (didn't extend chirp range)
Beta 3.02: 12,5h
NT-cmd-3.00: 6,5h
All beta run with screensaver on after 5 min, never goto blank screen, real time priority. (You can't beta-test graphics if the graphics is turned off...)
If we say 2 hours goes to graphics in 3.02, the actual crunching will take 62% longer in next NT-cmd-3.x than the current 3.00.
For the people that still uses 1.x and 2.x since they think 3.00 is too slow, this is terrible news.
"With version 3.02, we are extending the chirp range analysis so that it can potentially discern signals from hypothetical satellites orbiting earth-sized extrasolar planets. This is an exciting search space never before explored."
Because of a bug in some old 1.x-clients, all current clients will be cut-off then the beta-testing for win-gui is over and new 3.x-clients is released. The chirp range will be extended in all of these new clients, and of course use longer time to process.
For an idea of time, a couple of results:
Beta 3.01: 7,5h (didn't extend chirp range)
Beta 3.02: 12,5h
NT-cmd-3.00: 6,5h
All beta run with screensaver on after 5 min, never goto blank screen, real time priority. (You can't beta-test graphics if the graphics is turned off...)
If we say 2 hours goes to graphics in 3.02, the actual crunching will take 62% longer in next NT-cmd-3.x than the current 3.00.
For the people that still uses 1.x and 2.x since they think 3.00 is too slow, this is terrible news.
Comment