DAQ Meeting/20180602

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

• Chandan : We want to learn how to read out GEMs with a simple CODA controller and ROC system (we have a portable VME crate setup we want to use at SBU)
  • We Fixed our networking problems with Bryan Moffit at JLab on Thursday (see DAQ_Networking for more)
  • We need to plug in a GEM connected MPD v4.0 to a TI module and read out data with our ROC

Minutes

• Morning - 10AM - Chandan, Cameron, Danning Di : Chandan and Cameron visited Danning Di at UVA to get experience with their GEMs and CODA setup
  • We compile and load the MPD v4.0 libraries into the CODA running laptop host (orion), connected by a router controlled local network
  • We plug in GEMs to an MPD and use the TI board to trigger the MPD and take data on the Linux ROC (not using SSP zero suppression technique that the UVA group normally uses - requires editing the readout lists to turn off SSP variables from extern to NULL)
  • We needed to make and install the jvme, mpd4.0, and TI libraries
    • The TI needs to have its firmware updated to the most recent version for it to be able to read the MPD data with CODA
    • This update procedure requires special attention, or a special connector for it to work, and so will have to wait until Dustin McNulty visits SBU
  • (Whenever the ./coda_roc_rc3 command complains about missing libraries be sure to source the ~/coda_user_setup file that sets all of the necessary environment variables for CODA operation)

• To see raw data from the MPD (even with no TI trigger just looking at pedestals) we should:
  • Use /coda/2.6.2/linuxvme/mpd4.0/libsrc4.0/test_danning/mpdLibTest (compile with make, then pass arguments 'NameOutFile ModeOfRunning NEvents')
    • The three modes of operation (number via hex bit) are 1=event, 2=sample, and 4=histogram
    • Using histogram prints out the register's contents to the standard output stream and allows the user to monitor the data as it is produced by the MPD
  • The apv_config.txt file should be configured, the APVs connected, and the firmware version should be up to date for these things to work, and the output on the standard stream should agree with the configuration set ("invalid data code" means the firmware version is outdated)
  • A histo read/write test should succeed, unless there is a write permission or connectivity problem that needs to be resolved
  • We should see the APV show up as expected and the histo data should read out every 25ns (40MHz), where the trigger signal should be 35X larger than the pedestal and be 35 samples separated from each other
  • Danning will send Chandan some sample data, information on the firmware update, an example decoder from his github (www.github.com/danningdi), and some sample analyzer