Alfa temps, voltages, and currents

march,2002

where does the data come from

The alfa receiver has temperature, voltage, and current sensors that are sampled every 5 minutes. They are plotted below by year and for the last 5 and 30 days (updated each night).
The various plots are:

Temperatures: 16k (top), 70K (bottom).

The colors measure the 4 temperature sensors: K1=black,K2=red,K3=green,K4=blue.

Drain Voltages: top plot is pola, bottom plot is polB.The 3 pages are stage 1,2,3.

The colors are beams 0--6:w

Drain Currents: top plot is polA, bottom plot is polB.The 3 pages are stage 1,2,3.
Gate Voltages: top plot is polA, bottom plot is polB.The 3 pages are stage 1,2,3.

Data when the amps are turned off has not been included. This will create straight lines from the last good data point to the next valid point skipping over the missing data.

The data has been smoothed to:

last 5 days: no smoothing. 5 minute resolution
last 30 days: smoothed to 25 minute resolution.
yearToDate: smoothed to 1 hour resolution.

The smoothing uses adjacent samples which may not be adjacent in time if the amps have been turned off.

See using idl to plot the alfa temps and voltages for routines that allow you to plot this data interactively.

plots of temperatures,Voltages, and Currents verus time
Date	Temperatures 16K,70K	DrainV stage1,2,3	DrainI stage1,2,3	GateV stage1,2,3
2020	temps_2020(.ps) (.pdf)	drainV_2020(.ps) (.pdf)	drainI_2020(.ps) (.pdf)	gateV_2020(.ps) (.pdf)
2019	temps_2019(.ps) (.pdf)	drainV_2019(.ps) (.pdf)	drainI_2019(.ps) (.pdf)	gateV_2019(.ps) (.pdf)
2018	temps_2018(.ps) (.pdf)	drainV_2018(.ps) (.pdf)	drainI_2018(.ps) (.pdf)	gateV_2018(.ps) (.pdf)
2017	temps_2017(.ps) (.pdf)	drainV_2017(.ps) (.pdf)	drainI_2017(.ps) (.pdf)	gateV_2017(.ps) (.pdf)
2016	temps_2016(.ps) (.pdf)	drainV_2016(.ps) (.pdf)	drainI_2016(.ps) (.pdf)	gateV_2016(.ps) (.pdf)
2015	temps_2015(.ps) (.pdf)	drainV_2015(.ps) (.pdf)	drainI_2015(.ps) (.pdf)	gateV_2015(.ps) (.pdf)
2014	temps_2014(.ps) (.pdf)	drainV_2014(.ps) (.pdf)	drainI_2014(.ps) (.pdf)	gateV_2014(.ps) (.pdf)
2013	temps_2013(.ps) (.pdf)	drainV_2013(.ps) (.pdf)	drainI_2013(.ps) (.pdf)	gateV_2013(.ps) (.pdf)
2012	temps_2012(.ps) (.pdf)	drainV_2012(.ps) (.pdf)	drainI_2012(.ps) (.pdf)	gateV_2012(.ps) (.pdf)
2011	temps_2011(.ps) (.pdf)	drainV_2011(.ps) (.pdf)	drainI_2011(.ps) (.pdf)	gateV_2011(.ps) (.pdf)
2010	temps_2010(.ps) (.pdf)	drainV_2010(.ps) (.pdf)	drainI_2010(.ps) (.pdf)	gateV_2010(.ps) (.pdf)
2009	temps_2009(.ps) (.pdf)	drainV_2009(.ps) (.pdf)	drainI_2009(.ps) (.pdf)	gateV_2009(.ps) (.pdf)

Notes:

09dec10: 2.5Mhz oscillation in beam 5 bias card quenched.

Where does the data come from.

The alfa rcvr bias monitoring is read via an rs232 link into the aeroncpu (jan20).
The program alfa_mon.c does the reading (/home/cima/Wapp/Software/Svnwork/Sources/Utilities/alfa_mon.c).

It then broadcasts the data on a multicast group.

The logging of the data is done by:

/home/cima/Software/Stable/Sources/ALFA/alfa_logger.tcl
This is started by alfa_logger (in Sources dir)
The online routines for these two progs are actually in /home/cima/Progs/

Start/alfalogger
Display/alfa_logger.tcl

Starting the progs

opcon computer starts these program when opusr logs into the 4k display
The startup script is in

~opusr/bin/4k-monitor.sh
The line in the startup script that starts the alfamonwin and alfalogger is
/home/cima/bin/alfa_operators &>/dev/null &
This ends up calling /home/cima/Software/Stable/Progs/Start/alfa_operators

echo "Launching the ALFA monitor window ..."
$program_path/alfamonwin &

echo "Launching the ALFA logger ..."
$program_path/alfa_logger

I noticed any older versions of alfamonwin are not killed.
alfa_logger checks to see if it is already running.. if so it will eventually exit
I found it cleaner to :

ps -ef |grep alfa
and then kill alfamonwin, alfa_instrument_control.tcl, and alfa_logger.tcl