DAQ Meeting/20180727

Back to Main Page >> DAQ Documentation Portal >> DAQ Meetings

previous meeting << >> following meeting

Logistic information

BlueJeans calling instructions:
Toll-Free Number (U.S.& Canada): 888-240-2560
International toll number:     408-740-7256
Bluejeans CODE:         475 839 391
Bluejeans link: https://bluejeans.com/475839391

Agenda

• Bob : Resolve a question about the Injector DAQ having a bad logic modules
• Bob : Make sure the full Prex configuration with TS control still works
• Bob : Teach Cameron and Chandan how to test ADC channels and look at data read into CODA

Minutes

• Morning - 10AM - Bob, Cameron, Chandan, Paul King: Resolve a question about the Injector DAQ having a bad logic modules (see July 31 testing notes, the issue is likely the NIM crate's -6V being -4.2 wrongly)
  • Bob had previously moved all elements from a logic module to other neighboring boards because it was generating spurious signals
  • Paul King removed the module in question
    • There was some broken part where it connected with the crate
    • Replacing the unit still gave spurious signals, so it is likely the crate's problem (power supply for the NIM bin likely has issues)
    • We need to get a volt-meter and test the power supply itself before proceeding
• Afternoon - 3PM - Bob, Cameron, Chandan: Make sure the full Prex configuration with TS control still works
  • The counting house ROC needed to be rebooted to restore the TSROC process (the ROC instance had died on this computer after several weeks at idle - this may need to be incorporated as a standard check)
    • Testing whether or not the ROC process is still running can be done by logging into the computer and either running top (in unix) or issuing the "i" command from the telnet command line to see if it is running
    • If it is not running then check that the Non-Volatile RAM (NVRAM) is still pointing to the correct boot script (where the ROC instance is called to be run)
    • The NVRAM information is stored in the vmeram.doc file in the apar@adaq3:~/doc/ folder
  • The Left HRS ROC lost its NVRAM due to a power shutdown in the last weeks and the fact that the ROC does not have a good battery to keep the NVRAM alive during power-off
    • A new battery should be obtained and replaced for all ROCs, but for the LHRS ROC in particular
    • Cameron and Chandan became more fluent in telnet commands and running CODA to test for functioning ROCs
  • After restoring the TSROC process to the Counting House ROC and restoring the NVRAM to the LHRS ROC everything worked and we restored the Prex_ts.crl functionality from May 30th (see network map)
• Afternoon - 5PM - Bob, Cameron, Chandan: Teach Cameron and Chandan how to test ADC channels and look at data read into CODA
  • Bob obtained new custom made cables which connect the biased HAPPEX ADC inputs to the HAPPEX timing board Digital to Analog (DAC) 12 or 16 bit output
  • Bob taught Cameron and Chandan (again) how to use various software scripts to set the DAC output and read/plot the data files generated by the ADC channel being looked at
    • ~/adc18_ana/newrun Run_N N_events ROC_N VME_Slot_N script analyzes a run and provides a root file (in /dev/null/)with data that can be checked for HAPPEX 18 bit ADCs
  • PAN can be used for QWeak and HAPPEX ADCs
    • ~/bpan18 and ~/bpan18/pan and their READMEs are up to date and work
    • runpan Run_N prints a root output file (to ./ROOTfiles)
    • Plot_adc.C script looks at the root output (.x Plot_adc("adcx2",0))
    • Names are set in the control.db file (which maps the data structure from CODA into ROOT readable format)
  • Cameron and Chandan should jump off from this and individually check the dynamic range and functionality of every single ADC channel
  • They should note any problems and request to correct any bad resistances to put the 5V DAC maximum signal at around the 75% mark for each channel (Max 18 bit ADC channel = 2^18 = 262,144; Max DAC=5V in ADC readout goal = Max ADC*.75 = 196,608)
  • To simplify life and make their work last longer they should:
    • Write down all of these steps more precisely so that others can reproduce these steps
    • Update the READMEs and scripts themselves to behave more nicely and document their locations, uses, and inputs and outputs
    • Develop some new bash scripts for chaining test steps together in a more automated fashion
    • Develop some new VXworks usable script for use in controlling the sequence of DAC output more elaborately (and interfacing with other automated scripts)
    • Develop some new, more sophisticated ROOT scripts that will give graphical output as well as characterize the ADC channel's dynamic range and the pedestals and crosstalk in its neighbors and store this information for later
    • Map out the channels, modules, and crates logically, graphically, and with the prior obtained characterized data connected as well

Testing

Today's testing