Simple test of Bits++ interface in normal mode. Writes CLUT
frame buffer, so this is how Bits++ should be configured to
This test routine employs the PTB imaging pipeline to do the
If the optional ‘whichScreen’ screen index of the Bits++ screen is left
out, the script will choose the display with the highest screen id.
If everything works correctly, you should see the following:
- First some random color “junk” on the Bits++ display for 3 seconds.
- Then a black screen.
- Then, on each keystroke, an increase in display luminance.
- After twenty keystrokes, a fully white display.
- After another keystroke, the Bits++ should revert to a normal desktop