Buglets:

"Radiation period" in red text is erratic - it's appearance doesn't correspond with the actual radiation calculation period.

+++

Initially the display seems to play fair with the CP model but after a while it hogs almost all of the CPU - I found that if I increase the priority of "hadsm3um_4.02_windows_intelx86.exe" to 'below normal' then the visualisation still runs okay, although a little 'glitchy' when moving or altering the window, but it then takes sub 20 % of the CPU. The graphics card in that machine, Emma, is an ATI 8500LE, ie. reasonably modern - the CPDN classic visualisation only takes ~2% of the CPU whilst the display is updating & zilch during the radiation calculations.

+++

The screensaver looks okay, it looks the same as you leave the graphics setup by the look of it but it doesn't move around at all thus negating the whole idea behind a screensaver, avoiding CRT screen burn in... :-(

The radiation period's supposed to be every timestep that's a multiple of 7.
Yes quite right i think we need to optimize the performance of the GL display.
Dave_A just included in the api a signal to the client to indicate what
mode the core client was in. something for the next release.