New Canadian Brewer Spectrometer Network (CBSN) Control Software by: Tom Grajnar Ozone and UV Network Manager

New CBSN Brewer Software—Why? n n To provide an up-to-date Brewer spectrometer control standard for the global Brewer user community which can be easily implemented and accessed by all users. n n To take advantage of technological enhancements n n More user friendly windows interface n n Demand from the global user community n n Lack of a viable alternative

Philosophy Behind New Software n n A global Brewer Network solution n n Simplicity—in all aspects n n Accessibility—by all users n n Transparency—ability of end-user to test ideas fairly easily n n Operation engine vs analysis engine

User Interface—General Appearance n n Same general appearance as GWBasic software n n More detailed: – –Station information – –Measurement information – –Diagnostic information

User Interface—Components n n Header window: – –Time information – –Station information – –Brewer information n n Current observation window: – –Real time display of current measurement progress n n Measurement summary window: – –All ozone and uv measurement types – –System Diagnostic information – –Warning messages (temp, humidity etc.)

User Interface—Ozone Measurements n All ozone measurement types to be processed and displayed in real time n Processing algorithms for o3 from uv, um, gi and red will have to be incorporated n Will allow operators to note relative differences and changes in o3 measurement types enhancing diagnostics n Will allow for real-time incorporation of all ozone measurement types into data bulletins

Sample of User Interface

Stages of Software Development n n (1) Conversion from GW Basic version to the extent that it will run a MKII Brewer with old electronics (re-structured code) n n (2) Upgraded with ability to run all Brewer models (II, III, IV, V, NO2 only) with old or new electronics n n (3) Stakeholder polling for input on potential upgrades followed by prioritization and implementation

Monitoring Development Status n n Bi-Weekly reports provided detailing: n n 1) Software Progress n n 2) Updated timeline n n 3) Differences from GW Basic Version n n 4) Potential upgrades to consider for Stage 3