Difference between revisions of "Data Acquisition System"
Line 19: | Line 19: | ||
= How to run CODA = | = How to run CODA = | ||
− | + | CODA crl files are in: idaq@opsmdaq0: /opt/idaq/crl | |
− | + | CODA scripts files are in: idaq@opsmdaq0: /opt/idaq/scripts | |
* From an accelerator machine: '''ssh -X idaq@opsmdaq0''' (Note: '''idaq''' is the injector DAQ account and uses ssh authorized_keys for login - no need to enter password) and open few '''xterm &''' windows. | * From an accelerator machine: '''ssh -X idaq@opsmdaq0''' (Note: '''idaq''' is the injector DAQ account and uses ssh authorized_keys for login - no need to enter password) and open few '''xterm &''' windows. |
Revision as of 09:19, 28 June 2013
DAQ Hardware
- Electronic Map of Mott Crates (January 29, 2013):
Media:ElectronicsMap_20130129.pdf
Media:ElectronicsMap_20130129.ppt
- Cabling of FADC, Scalers, and TDC (January 29, 2013):
- DAQ Timing (January 29, 2013):
Media:DAQ_Timing_20130129.pptx
How to run CODA
CODA crl files are in: idaq@opsmdaq0: /opt/idaq/crl
CODA scripts files are in: idaq@opsmdaq0: /opt/idaq/scripts
* From an accelerator machine: ssh -X idaq@opsmdaq0 (Note: idaq is the injector DAQ account and uses ssh authorized_keys for login - no need to enter password) and open few xterm & windows.
xterm 1: telnet iocmdaq1
xterm 2: msqld (the CODA msqld database is usually running unless opsmdaq0 was rebooted)
xterm 3: platform
xterm 4: codamaster
Choose the configuration: Mott_Sample
When the CODA MASTER panel appears, select Config => Enable Buttons.
Select ET System, Event Builder, Event Recorder and Run Control. After doing that if you will click on Get Status you will find status of ER1, EB1 and ROC1. All buttons must be green.
Select Run Control and the main CODA panel will appear.
Start and Stop a Run
From Run Control panel, select in the following order:
- Sessions => inj
- Configurations => Cool => Mott_Sample
- Platform => Connect
- Configure
- Download
- Prestart
- Start
At the end:
- Stop
and if you want to apply a change or you need a new configuration:
- Reset
and start from number 5.
Mott DAQ iocmdaq1
- There are two ways to access the Mott DAQ ioc:
- From an accelerator machine: telnet iocmdaq1
- From an accelerator machine: ioc_concole iocmdaq1. Here you need to enter a password to this cannot be done with the idaq account.
The startup file is: /cs/op/iocs/iocmdaq1/startup
The CODA boot file: /opt/coda/boot/mott_roc1.boot
Online Monitoring
Scalers: xscaler
"xscaler" is a graphical display of the scalers from the Mott DAQ.
If you login to opsmdaq0 as the "idaq" user, and type "xscaler", it will tell you exactly what to do. And that is:
cd /opt/idaq/xscaler ; ./xscaler
Dead Time: datamon
There is a display to monitor the DAQ dead time. To run it use the idaq user on opsmdaq0. Type: datamon
Scaler Data written to EPICS
The scaler data which appears in xscaler (see above for xscaler) is also written to EPICS. The data are rates in Hz.
The EPICS channels are of the form "Inj_ScalerN_ChM" where N = 1,2,3 and M = 1,2,3,4,...32. See xscaler for channels assignments.
To retrieve data from EPICS you can, for example, do this:
caget Inj_Scaler1_Ch24
Inj_Scaler1_Ch24 484195
The number here means 484195 Hz.
Online Histogram Display
Log on opsmdaq0 using idaq user and from the idaq home directory and type: peppoOnline.
Two windows open, the smaller one have buttons to control the plot to see, the biggest one shows the plot to monitor.
Analysis
Macros for the Analysis
There are several macros to be used for the analysis. All are in opsmdaq0 in the directory:
/work/idaq/Analysis/macrofiles/
The macroes are:
- Pedestal_Int.cpp => Pedestal_Int.cpp provides a gaussian fit of the pedestals. ONLY for the integral method. It generates the file:
/work/idaq/Analysis/pedestalfiles/Pedestal_Int_Fit_(runnumber).dat
To run it:
root .L Pedestal_int.cpp main() insert filename when asked with no extensions (.root)
Issues and FAQ
- RunNumber: if the in the msql is different from the one in cool database, coda doesn't work. To solve it open dbedit => localhost => sessions and change the RunNumber
- If VME is completly stuck, to do hard reboot remotely :
login on opsmdaq0 type : sudo killall minicom and : sudo minicom If nothing appear, type in : CAEN choose crate control hit O to turn off and O again to turn back on
If some numbers already display the menu is already activated then hit O to turn off and O to turn back on