DAQ Meeting/20180731

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 : Get Bank data structure incorporated in old Prex_ts.crl functionality
  • See also the compton polarimeter DAQ's fadcTest.crl
• Cameron : Look into merging Injector.crl and Prex_ts.crl into one .crl
  • See if it is possible to either merge the Injector.crl into Prex_ts.crl or to add the RampTest.crl HAPPEX Timing Board and rampdac16 features into it so we can test QWeak ADCs easily and add a HAPPEX Timing Board to do so permanantly
  • See if there are any good features in Injector.crl that we may need to use in other applications
  • Simplify life by just having a single .crl for the entire experiment

Minutes

• Morning - 11AM - Bob, Cameron : Look at compton example and begin working on including Bank data structures in Prex_ts.crl -> Prex_ts_banks.crl is the new file
  • Make a new config called something like Prex_banks.crl
  • Add in bank structures (like in the compton DAQ fadcTest.crl - "[compton@compton ~/crl]$ grep FADC_ACCUM fadcTest.crl")

const FADC_ACCUM = 0x0211
open bank FADC_ACCUM of BT_UI4
%%
c code 
%%
close bank

• • Make separate banks for scalers, TI and FLEXIOs, HAPPEX ADC (16 and 18 bit), QWeak ADC block, HAPPEX Timing Board, miscelaneous
    • xcefdump will automatically see the new data dump structure
    • We will have to add the new data dump structure into PAN/new analyzers

• • Working on it seems to bump into complications
    • Incorporating TS Control appears to be difficult to do as a usrstrutils.c kind of feature, since that gets used during Download, but "ts control" has to be set before download...
    • The StartOfBank variable is failing to initialize in the "makelist Prex_ts_banks.crl ppc" process
    • There are some headers whose purpose is not entirely clear
    • Littered the file with lots of FIXMEs and clearly labelled what lines of code are additions and what they used to be with //#CAM and //#/CAM braces around work
    • Work on these tomorrow

Testing

Today's testing