Difference between revisions of "MainPage:Nuclear:NPS:PWO:CODA"
Jump to navigation
Jump to search
| (4 intermediate revisions by one other user not shown) | |||
| Line 6: | Line 6: | ||
== Introduction == | == Introduction == | ||
| − | The Data Acquisition (DAQ) setup at CUA utilizes "CODA" which is a software and hardware that enables data taking in | + | The Data Acquisition (DAQ) setup at CUA utilizes "CODA" which is a software and hardware that enables data taking in nuclear physics experiments. We use CODA for many experiments at CUA (light yield, PMT testing, etc.). You can read more about it [https://coda.jlab.org/drupal/content/welcome here.] |
== How to use CODA == | == How to use CODA == | ||
| − | === Starting coda === | + | === Starting/Restarting coda === |
| + | #Restart the DAQ computer if you are having problems. | ||
# On the DAQ computer, type < cd coda > in a terminal to go to the directory where coda is located. | # On the DAQ computer, type < cd coda > in a terminal to go to the directory where coda is located. | ||
| − | # In the same terminal, type < sudo | + | # In the same terminal, type < sudo ./coda_user_setup_databases >; you will be prompted to type in the password (bolded)- it is: '''linux!''' ... some windows will pop up- wait 10 seconds. |
| − | # Select the configuration name " | + | # Then type < sudo ./coda_user_setup_codamaster > in the same terminal. |
| + | # Several windows will pop up, one of interest is the "working config" window which asks you to select a configuration name. Select the configuration name '''vme_camac''' | ||
| + | #Click on '''Config''' on the top left of the window that popped up with "vme1 and EB1, kill, etc", and select "Enable Buttons". | ||
| + | #Click on '''Event builder''' and '''Run Control''' buttons. | ||
| + | #On the run control GUI, click '''Platform''' and then '''Connect''' on the top left side of the window. | ||
| + | # It should say "connecting" you can now click the configure button right below "platform". Should say '''configuring''', and then '''configured''' on the status bar. You can now start the run. | ||
| + | If there is a successful '''VME1''' and '''EB1''' connection, the messages will say that the connection is successful. If there are warning signs or there is a consistent "configuring" or "activating" on the status bar, then there is a problem. Go to the Troubleshoot section below. | ||
| + | |||
=== Killing coda === | === Killing coda === | ||
| − | + | #Just restart the computer if "ctrl+c" or closing out of all the windows doesn't work. | |
== Troubleshoot == | == Troubleshoot == | ||
| + | #If warning signs of VME1 and EB1 connection and the status saying "configuring" or "activating" are persistent, then there is a problem and we have to reboot coda. If the problem persists for another time, close out of coda again/restart the computer. We have to reboot '''minicom'''. | ||
| + | #Rebooting minicom: go to a new terminal and to the home DAQ directory. Type: < sudo minicom > and then < reboot >. This will relay a lot of messages on the terminal, one of them including "VX WORKS" which (hopefully) ensures that minicom is rebooted. | ||
| + | #Now you can start coda: type < cd coda > in a new directory. | ||
| + | # And now type < sudo ./coda_user_setup_codamaster > and follow the same instructions '''after''' #'''4''' in the above section '''Starting/Restarting CODA'''. | ||
# Possible [http://hallaweb.jlab.org/equipment/daq/coda_hints.html website] that may help. | # Possible [http://hallaweb.jlab.org/equipment/daq/coda_hints.html website] that may help. | ||
| Line 23: | Line 35: | ||
== FAQ == | == FAQ == | ||
# Why does coda sometimes crash? | # Why does coda sometimes crash? | ||
| + | #* There could be several reasons: so far we have experienced a corrupted connection between VME1 and EB1. | ||
| + | #What is VME1 and EB1? | ||
| + | #* VME1 is the connection between the DAQ setup and the computer, and EB1 is the "event builder" which is the interface used to take events (idk?). | ||
# Who can help us if there is a bigger internal issue? | # Who can help us if there is a bigger internal issue? | ||
#* Steve Wood: email - saw@jlab.org | #* Steve Wood: email - saw@jlab.org | ||
| + | |||
| + | |||
| + | = Using CAEN QDC = | ||
| + | |||
| + | The CAEN QDC (Charge to Digital Conversion) System can be used in parallel with CODA (As long as they are running in different computers). These modules are connected to the ''Control Computer'' via USB. | ||
| + | |||
| + | # Restart the ''Control Computer'' selecting the Windows option in the Grub Loader | ||
| + | # Make sure your signal is into your gate (using the Oscilloscope) and plug the gate and the signal cables into the CAN QDC module | ||
| + | # There is a shortcut in the desktop called ''Run ADC_DAQ'' check the messages in the screen (all of them should be showing Ok at the end of the line) | ||
| + | # Take note of the ''MAPC'' option you will be able to see the name of the file in which the data is going to be stored. | ||
| + | # Press the "s" key to start recording data, you will be able to see a histogram filling up as the data is being taken. | ||
| + | # To stop the data acquisition process press ENTER twice on the ''Run ADC_DAQ'' Window. | ||
| + | # Your data is stored in HEX format (You can find them clicking on the ''DataFiles - Shortcut'' located at the Desktop | ||
| + | # You can convert your data using this script[https://gist.githubusercontent.com/anonymous/a953191a554af1d03b1d0af40b6787ec/raw/2bcaa19303283682df18b394b6a6a8fdae33381f/HEX2root_NewADC.C] | ||
Latest revision as of 18:20, 20 December 2016
| ⇐ Back to Neutral Particle Spectrometer |
| ⇐ Back to the Main_Page |
Introduction
The Data Acquisition (DAQ) setup at CUA utilizes "CODA" which is a software and hardware that enables data taking in nuclear physics experiments. We use CODA for many experiments at CUA (light yield, PMT testing, etc.). You can read more about it here.
How to use CODA
Starting/Restarting coda
- Restart the DAQ computer if you are having problems.
- On the DAQ computer, type < cd coda > in a terminal to go to the directory where coda is located.
- In the same terminal, type < sudo ./coda_user_setup_databases >; you will be prompted to type in the password (bolded)- it is: linux! ... some windows will pop up- wait 10 seconds.
- Then type < sudo ./coda_user_setup_codamaster > in the same terminal.
- Several windows will pop up, one of interest is the "working config" window which asks you to select a configuration name. Select the configuration name vme_camac
- Click on Config on the top left of the window that popped up with "vme1 and EB1, kill, etc", and select "Enable Buttons".
- Click on Event builder and Run Control buttons.
- On the run control GUI, click Platform and then Connect on the top left side of the window.
- It should say "connecting" you can now click the configure button right below "platform". Should say configuring, and then configured on the status bar. You can now start the run.
If there is a successful VME1 and EB1 connection, the messages will say that the connection is successful. If there are warning signs or there is a consistent "configuring" or "activating" on the status bar, then there is a problem. Go to the Troubleshoot section below.
Killing coda
- Just restart the computer if "ctrl+c" or closing out of all the windows doesn't work.
Troubleshoot
- If warning signs of VME1 and EB1 connection and the status saying "configuring" or "activating" are persistent, then there is a problem and we have to reboot coda. If the problem persists for another time, close out of coda again/restart the computer. We have to reboot minicom.
- Rebooting minicom: go to a new terminal and to the home DAQ directory. Type: < sudo minicom > and then < reboot >. This will relay a lot of messages on the terminal, one of them including "VX WORKS" which (hopefully) ensures that minicom is rebooted.
- Now you can start coda: type < cd coda > in a new directory.
- And now type < sudo ./coda_user_setup_codamaster > and follow the same instructions after #4 in the above section Starting/Restarting CODA.
- Possible website that may help.
FAQ
- Why does coda sometimes crash?
- There could be several reasons: so far we have experienced a corrupted connection between VME1 and EB1.
- What is VME1 and EB1?
- VME1 is the connection between the DAQ setup and the computer, and EB1 is the "event builder" which is the interface used to take events (idk?).
- Who can help us if there is a bigger internal issue?
- Steve Wood: email - saw@jlab.org
Using CAEN QDC
The CAEN QDC (Charge to Digital Conversion) System can be used in parallel with CODA (As long as they are running in different computers). These modules are connected to the Control Computer via USB.
- Restart the Control Computer selecting the Windows option in the Grub Loader
- Make sure your signal is into your gate (using the Oscilloscope) and plug the gate and the signal cables into the CAN QDC module
- There is a shortcut in the desktop called Run ADC_DAQ check the messages in the screen (all of them should be showing Ok at the end of the line)
- Take note of the MAPC option you will be able to see the name of the file in which the data is going to be stored.
- Press the "s" key to start recording data, you will be able to see a histogram filling up as the data is being taken.
- To stop the data acquisition process press ENTER twice on the Run ADC_DAQ Window.
- Your data is stored in HEX format (You can find them clicking on the DataFiles - Shortcut located at the Desktop
- You can convert your data using this script[1]