Contents

MOPSIC MONITOR
1. Information displayed
2. Indication of Problems
COORDINATES MONITOR
1. Information displayed
2. Indication of Problems
INSTABILITIES MONITOR
1. Information displayed
2. Indication of Problems

In this wiki we aim to create a guide of the info displayed by the different monitors running at the telescope. The monitors Mopsic Monitor, and MonCoo must be running always at the telescope. The only exception is in case of maintenance time, when the version of mopsic can be changed, or doing Absorber measurements with MAMBO2 in stow position (in which case the mopsic monitor must be replaced by the MonInst monitor).

MOPSIC MONITOR

This monitor displays and reduces all the observations of the bolometer MAMBO2 and continuum data from heterodyne receivers. The vncviewer port of this monitor is the 27.

Information displayed

General Info

This figure shows the normal display of the monitor.

From this snapshot we can see that the last pointing was done on G34.3, using the bands E1 and E3, at freq. 173.507GHz and 267.557 GH, 2160 seconds ago, the scan was the 214 and it consisted on 4 subscans. There were some spikes. We can also see the previous pointing and focus corrections and the elevation and azimuth of the source. All this information and more is shown in the monitor. Where all these is would be explained in the following lines. However, before reading futher, I recommend you to have a first look to the snapshot and try to locate this info by yourselves.

All the panels showed by the monitor display at their top the same info in the same order: SOURCE #SCAN TELESCOPE DATE FRONTEND BACKEND. This stands for all the monitors
In the shell where the monitor was launched, it can be read how long the data has not changed. This means that during this time no continuum data, with EMIR, HERA or MAMBO2 has been taken. This can be used to see if the data is created. For instance, in case MAMBO is used and the monitor does not show the new data, this would mean that the fits are not being created, which could point towards an ABBA failure. Note that a certain scan would only be shown once at least the first subscan has finished.
In the shell where the monitor was launched, it can be read also, the scan number, the number of subscans done.
In any panel of the monitors showing the signal against time (e.g. the bottom-right window in the previous plot) a vertical red line denotes the start of a subscan, while a green line denotes the end of it. Any problem of those described below that happens between a green and a red line in the signal plot can be ignored, since it happened between subscan, i.e. does not affect the data.This stands for all the monitors

Heterodyne

MAMBO2 Pointing

* MAMBO2 Focus

* MAMBO2 Onoff

Upper left: on-off RA/DEC map of all pixels. The RA/DEC 0/0 denotes the reference pixel for pointing.
Upper right: center pixel (53): before/after skynoise reduction, i.e. correlated signal filter (CSF, red/green)
Lower left:
- A star denotes the result of the last sky dips, i.e. the sky emissivity at the source elevation CHECK
- Output of 3 DC pixels to check for changes in the sky emissivity
  - upper: line of sight (los) opacity (showing elevation effect and others)
  - lower: total power
Lower center:
- noise in the data before/after the CSF (the plot before is/will be overplotted with the noise after the CSF, in this particular case the rms in the data after CSF is visible, the numbers above the plot 49.5/51mJy/beam give the rms values of the high frequency noise component)
- gain 1 (in this particular case)
- col*/nule/sfcz, i.e. pointing and focus offsets
- throw 32", period 520msec, rotator angle 0
Lower right: time series of 4 pixels (51, 52, 53, 54), before and after sky noise subtraction