CSCTF Tasks

Hardware and Commissioning Work

  1. Fiber work [DW, GP]:
    1. Install new longer DDU-SP link fibers (stored in back of rack)
    2. Re-routing of trigger fibers so that single SPs can be removed more easily
    3. Increase in number of Velcro support points and attention to stress reduction for most loaded fibers in bundles (advice fiber guys)
  2. Monitor problems on online (csc-tf.cms) machine
    1.  Create an online log of all problems and include post-mortem checks of log files from all crashes and unexplained behavior. (/var/log/messages, dmesg etc..)
  3. Synchronization of orbit counter (OC0) [DW, LU, GR]
    1.  –TTCci config change for CSC, suggest put in configure (or possibly resynch) sequence.
  4. CSCTF-DTTF data exchange commissioning [DW, GP]
    1. Fine timing of DT stubs in CSCTF
    2. Remap of exchange quality values (new TMB format); work with Janos.
    3. F and Fb exchange mapping; work with Janos.
    4. Worry about fine details of MB data; 2nd bx flag, cal, and examine how the BXN lsb reset themselves over all the links. (Should be then masked in to synch FMMs.
  5. ME1/a trigger mask
    1. Solution should be @ TMB level, remind Greg & Jay.
    2. We can possibly make a mask in the LUTs for coincidence tracks (otherwise potentially a switch in SP firmware.)
  6. Complete setup of 904 Test stand [DW, GP]
    1. Get TTC crate running properly including full TTC control s/w
    2. Move ‘real’ spare TF crate in to 904.
    3. Hassle Russian guys who were assembling the rest of the test stand bits (p-crate, chamber…)
    4. Keep online (google doc) of equipment manifest up to date.
  7. Synch of BXN
    1. Check & offset BXN as needed; GT, SP, peripheral crates
  8. Fine delay scan of TTC-rx
    1. Fine tuning of trigger links to be centered in phase.
  9. Web based tool for easy translation & creation of config keys

 

 

 

Firmware Tests and Studies

  1. Test of firmware with halo muon trigger delay and CSC stub delay [DW, GP]
  2. Systematic accounting of link errors [DW, GP, LU]
    1.  listing, frequency, improvement with cleaning? Improvement with re-sync?), and procedures to mitigate 
    2. Mask back in to FMM response, after resolving any issues that make this problematic at the DAQ side
  3. Firmware development and test for new SP mezzanine card  [LU, AM]
  4. SP flash tests

 

 

Online Software

  1. Monitorables/Conditions [DW]
    1. Storage into online DB of monitorables
    2. tools to retrieve info (possibly offline with O2O tool)
    3. Standard auto production of plots & validation summary (à-la TF DQM)
  2. Error reporting from online monitoring (conditions and TF-DQM) to shifters and ultimately to any centralized error reporting mechanism [DW, GP]
    1. Using Sentinel reporting system?
  3. Web-based GUI of rates (collision tracks and halo) and errors (porting of existing Root-based code into TS framework) [DW, GP]
  4. Systematic review of all histos in local and central DQM for suggested changes, additions, or removal of plots and addition of appropriate documentation [KK, JG, DA]
  5. Diagnostics from data unpacking added to central DQM (data format errors) [JG, KK]
  6. Link errors and other info from local DQM inserted into central DQM [JG]
  7. Conversion of local DQM to run as XDAQ app and thus be served events online rather than read local files [JG,KK]
  8. Validate CSCTF emulator in central DQM [JG, KK, RICE]
    1. Ensure SP emulation is correct (requires propagation of config settings)
    2. Ensure Muon Sorter emulation works vs. SP and GMT readout  (winner bits, phi, eta, quality PT ) [RICE]
  9. MPCàSP optical link checks from event data (in DQM?) [RICE]
  10. O2O tools to propagate online configuration to offline DB (Event Setup work) [KK?]
  11. SPàMSàGMT validation with data [RICE]
    1. Although CSCTF (MS & SP) injection code exists, no real stress test completed.
    2. Check out MS sorting algorithm & LUT & SP winner bit return.
  12. Changes to data fields for unpacked digis (BC0 à BXN) [KK]
  13. Add collection of DT stubs (and CSC stubs) from CSCTF unpacker [KK, LR]

 

 

 

 

Online Software Consolidation

  1. Synchronize CVS repository and what we have on online machines
    1. CVS tags, continued /nfshome0/csctfts backup on uftrig03
  2. Clean up and minor redesign of core libraries;
    1. Scan-ease interface; Holger era, horrid inherited low level package.
    2. SPObject*

                                                               i.      over complicated unused inheritance tree.

                                                             ii.      I think maybe we should consider dealing in auto_ptrs or at least count refs in TFCrateContainer.

    1. Firmware loading; Holger legacy, lots of nasty things, should be cleaned & options for things like parasitic dumps of current load added.
    2. CAEN block transfer mode for standard register (e.g. LUT writes)
  1. Clean up of SPFunctions library
    1. Want most of basic code in there, classes have become badly designed, inconsistent (over time!).  Due for a (very simple) layout reshuffle.
  2. Clean up /test executables;
    1. Get rid of the old ones we don’t use,
    2. clean up those written in a hurry & turn in to proper user code rather than expert developer code. (e.g. rather than commenting in/out a line to turn on injections on single/repeated injections, write a proper user interface..)
  3. SPValidations, SPStandAlones, SPLUTSAndFirmware, (&localConditions)
    1. Mostly fine, we should finish them properly.
  4. SPReadout & rootUnpackSPDAQ we should decide what to keep, make it user friendly and and kill the rest.
  5. Ts cell; (really DW’s domain now.) 
    1. I think a final touch to the multithreading part would be a P-ID recall mechanism to kill and report timed out threads.  (we never saw any problems with thread recall but we should proof for it).  Right now you just wait for the last thread to terminate and then report the status.
    2. A more global time out mechanism for the whole process.
  6. Error handling;
    1. I see right now we have a few different exceptions strategies across the packages, we should homogenise to one and write some of the handling code with framework rather than stand-alone executable running in mind.
    2. I think it would be useful to introduce more throw lists than we have and expect the framework to have dealt with he consequences rather than trying to deal with properly unknown exceptions ourselves.
    3. We should build in some verbosity levels for our output.

 

 

 

Offline Studies and Software

  1. Verify BXA working for halo trigger [DW]
  2. Synchronization studies using beam data (halo, splash events) [DW]
  3. Halo trigger tuning (Delta Eta window, delta phi window, use of accel mu bits) [JG]
  4. Halo muon HLT release validation package and checks [JG]
  5. Halo muon HLT DQM plots [JG]
  6. Loose dimuon trigger (optimize J/Psi and Upsilon efficiency) [JG]
  7. Study of DT phi vs. CSC phi from data, derive proper conversions and LUTs  [RICE]
  8. Study of DT synchronization, DT stub quality from data [DW,LR]
  9. Validation and tuning of SR LUTs  [GP, Dubna]
    1. Compare assigned eta/phi coordinates to offline muon reconstruction
    2. Fix ME1 F-flip problem
  10. Study/validate introduction of disk alignment offsets [GP,NK]
    1. Check/repair/introduce propagation of offsets into CSCTF LUTs
    2. Understand sensitivity of trigger efficiency & Pt resolution vs (non incorporated) miss-alignment. (mode by mode, plane by plane)
  11. ‘Standard’ offline CSCTF data analysis package [KK,LR]
    1. Lives in CVS as an example, unpacks Global DAQ data and spits out root tree of plots [decide on area]
    2. Start with some of basic TF DQM style plots, eta/phi, rate by mode etc.
    3. Include ratio of CSC trigs and efficiency @ HLT by mode
    4. DT overlap rate by sector etc etc..
  12. Benchmarking of efficiencies standard physics channels + background rates vs CSCTF configs
    1. Basic (e.g. dilepton physics) but also some basic but rare valuable channels (Higgs).
    2. Vs DAT_ETA cuts mode by mode
  13. PT LUT tuning
    1. MC-based parameterizations [JG, RA]
    2. Tracker-based parameterizations from data [GP]
    3. L2 standalone muon reco fit to SP data, MC-based [GP]
    4. L2 standalone muon reco fit to SP data, Tracker-based [GP]
    5. Valid charge bit tuning [?]
    6. Miscellanea (singles and halo codes) [?]
    7. Validate rate reduction against minbias
    8. Validate efficiency important channels (Tev muons, low momentum muons)
  14. Improvements to SP core logic (new mezzanine card)
    1. PT assignment optimization with 4 stations (TeV mu recover) [AM, RW]

b.      Use of ME1 angle (TMB pattern à fB ) to improve PT assignment [GP]

c.       Improvement of extrapolation units (more combinations, use of accel muon bit, use of TMB qualities, …) [?]

d.      Refined halo muon trigger using ME1 [AM, JG]

e.       Improved ghost cancellation including eta ghost-busting in ME2-ME3 [AM,DA]

  1. LUT table dumping (overlaps with the misalignment job)
    1. Incorporate correct DT-phi conversion
    2. Pattern replace by mode code (à-la deprecated DAT_FTR function)

1.      exists as a post-dump converting executable for now

  1. Emulator Updates
    1. Do we correctly simulate Halo, singles, coincidences, mode-replace code, phi conversions, halo delays etc etc.. ?

 

Documentation

  1. CSCTF Installation note [DH]
  2. CSCTF Commissioning note [DH]
  3. A full user/new developer manual for online software, it is just too big a package with too many funny external implications not to do this properly. [DH!]
  4. Update/refinement to CSCTF shift manual.