Data Taking Procedure

Minimum steps to ensure good data quality.

DAQ Frequently Asked Questions

What happens during run state changes


  1. Critical Servers Running? Ensure critical servers are running by clicking on Process Manager/ Servers tab on main GUI.
  2. Event Chain Running? Make sure Tower1 and Veto Crate processes are selected. If not, select them and click on Start Nodes button.
  3. Monitoring Chain Running? Make sure Monitoring State is in Run state. If not, Start Monitoring, change its state to config and then run. Each state must be followed by clicking on the Start Monitoring button to its left.
  4. Experiment Mode Select appropriate Experiment Mode
  5. Run Configuration Bring up the Run Configuration GUI from the Tools menu. It should display current FEB and RTF settings files being used and also LED flashing parameters. Usually you don't change any of these or need to do anything else on this GUI. However, if you want to load a different FEB or RTF settings (with different parameters) file, load it by clicking on the corresponding detector field. Finally, click on the Configure Now button
  6. Configure Experiment Click on Config. It takes about a couple of minutes to completely conifgure the whole system. Now, you must watch for any error messages in bold red appearing on the GUI. This can be GPIB errors, CAEN high voltage errors or any other possible errors. A comprensive list will be put up here.
  7. Start Run Click on Run button to start the run. This will bring up dialog box where you need to enter short begin-run comments. Make them precise and useful. If the run starts properly, you will see event numbers increasing. First 200 events in a data series are Random Triggered events and these events should proceed fast (10 Hz). If it is a calibration run, make sure you are on intercom with someone in the RF room so that the source is not in when the random triggers are taken. After getting to 200 events, the source can be inserted.
  8. Is The System Healthy? Now is the critical step to make sure there are no obvious oddities in the system. Frequency response of a system is like EKG report, it tells a lot of about the health of the system. Bring up the Noise Viewer and click on Recent Data. Study the frequency response of the system. Compare with a good noise data set. An example of something obviously wrong in the system can be seen from a recent noise plot. This shows that the Z4 Ph B is super conducting and Z4 Ph C is normal. Also, interesting to look at the noise plot of a recent run where the Z1 Ph D was accidentally unplugged from the digitizer. Notice the difference between an unplugged phonon channel response vs the response when the phonon sensor was normal. Make sure that the phonon sensors are balanced, have a flat frequency response in the interesting domain, no huge noise peaks, etc.
  9. Is Data Reasonable? Bring up the Online Display and watch the pulses on all the detectors. Make sure you see reasonable pulses on all channels of a detector when that detector triggers.
  10. Monitor The Run Bring up the Monitoring GUIs (Scalar, Veto) and watch various parameters such as trigger rates, phonon offsets, veto rates, etc to make sure nothing odd is happening. Monitoring alarms are implemented which will send error messages, visible on the RC GUI, when such things go out of tolerance.
  11. Fridge Status Keep an eye on the fridge, both on the intellution web page as well as the Fridge Historical GUI. Another useful thing to do is to watch for variations on the Fridge Monitor GUI.
  12. Watch the GUI Keep an eye on the main Run Control GUI to see if any error conditions develop and take appropriate actions (list will be added) when something does go wrong.
  13. Stopping the Run Normally, the runs will be automatically stopped and restarted, driven by the cryo transfers. If you need to stop the run otherwise, click on Stop button, enter a useful end of run comment. Data taking will be stopped.
  14. Data Archival and Processing Ensure that data is copied to tape in the mine and also copied upstairs so that Dark Pipe can analyze the data. Dark Pipe should produce RQs and RRQs. Make sure these are produced after a reasonable time.
  15. More Later