290 likes | 414 Views
John Zweizig LIGO/Caltech LLO August 18, 2006. DMT Monitors: Beyond the FOM. Everyone Knows About the FOMs. Other Things Aren't So Obvious. How do I know what's running? What kinds of data are the monitors producing? Where are the output data located? How do I use them?
E N D
John Zweizig LIGO/Caltech LLO August 18, 2006 DMT Monitors: Beyond the FOM
Other Things Aren't So Obvious • How do I know what's running? • What kinds of data are the monitors producing? • Where are the output data located? • How do I use them? • Can I use DMT to look at new things?
Overview • DMT Online • data products • Spi Page • Getting the data • Running existing monitors. • Setting up the environment • Making a PSLmon configuration • Running offline (or online at LHO?)
DMT Data Products • Online DMT viewer objects • dmtviewer (FOMs) • webview • Trends • Everything you see on the FOMs and a lot more are recorded as trends • 1/minute statistical summary (mean, max, min, n, rms)
DMT Data Products • Status reports • Monitor specific status and configuration info (not standardized) • May contain plots, statistics, channel names, etc. • Triggers • Time stamps of interesting events (transients, state changes, readout errors, range overflows, etc) • Lots of metadata to describe transient tim, frequency, etc. • Alarms • flag abnormal run states, failures
Alarms Triggerstatistics Recent triggers Monitor docs Status report Spi Page
Viewing Online Data Objects • webview • Standard browser accessible plots • http://stone.ligo-wa.caltech.edu:9991/monitors.html • dmtviewer • Must install dmtviewer from e.g. ligotools • DMTWEBSERVER=stone.ligo-wa.caltech.edu:9991/LHO,delaronde.ligola.caltech.edu:9991/LLO
Trend Storage/Retrieval • DMT Trend archive directory structure • Online directories: /dmt/<monitor>/H-M-<gps> • Archive: /archive/frames/dmt/LLO/<monitor>/H-M-<gps> • Trend writer class writes to $DMTRENDOUT/. • Read/process/plot trends like any frame (matlab, root/DMT, etc) or dump with trendtable. • Plot trends from control room with dv.
Triggers • Trigger Indicate properties of transient events • Name, subtype • Time: Start, maximum, duration • Frequency: Center, bandwidth, peak • Trigger archival • Triggers generated by monitors, are sent to TrigMgr (and then SeqInsert) to be stored in database
Running a Monitor Trigger output Monitor report Trend output directory
PSLmon • Originally written to look at PSL properties (the only subsystem working at the time) • Doc: http://www.ligo.caltech.edu/~jzweizig/dmt/Monitors/PSLmon • Now – A general purpose set of tools • Band limited RMS (fourier domain) • Glitch finding • Spectra • Coherence (not used/tested/supported)
Configuration File • Shell command like syntax. • Configuration commands • Parameter: Set a run-time parameter • Channel: define a channel to be processed • Filter: Define filters • Band: Create a band-limired RMS tool • Glitch: Create a glitch tool
Design a Filter • Use foton or root to specify a filter and • Look at the Bode plot • Check out the time domain response in root
Running on Bermuda Configuration Script Monitor report files Trend files