Difference between revisions of "Jun 29, 2015 Cal F250"

From GlueXWiki
Jump to: navigation, search
(→‎Minutes)
(→‎Minutes)
Line 56: Line 56:
 
#* Need 14 bits for peak value (0-4095 + underflow + overflow)
 
#* Need 14 bits for peak value (0-4095 + underflow + overflow)
 
#* Need >~16 bits for sum value (sum/peak ~ 15 for BCAL) + quality factor bits
 
#* Need >~16 bits for sum value (sum/peak ~ 15 for BCAL) + quality factor bits
−
#* Need  
+
#* Need >~15 for the FADC time (#samples x 64 > 400? x 64 = 25k).
 +
#* Pedestal requirements? (depends strongly on algorithm)
 +
#* Quality factors?
 
# Priority List (all)
 
# Priority List (all)
 +
## What is the impact of additional calorimeter data words on the GlueX rate capability? (David might be able to help with this).
 +
## Pedestals: what is the best/optimal(?) method for pedestal determination and eventual subtraction from signal
 +
##* consider a rolling average in the hardware for all pedestals? (compute pedestal of each channel every trigger to make pedestal determination independent of rate in that channel)
 +
##* Do we need to use multiple events to determine the pedestal?
 +
##* How does integer division affect the pedestal determination?
 +
##* Use a single word for pedestal information, which would easily allow dropping in data stream at high rates?
 +
## Signal
 +
##* Are there advantages to variable length integration window? (if so, need to store number of summed samples, or subtract pedestal on the fly)
 +
##* Peak vs sum (or integral). Save both?
 +
##* Consider integration of a few samples around the peak to give a more precise "peak" value?
 +
## Abnormal conditions
 +
##* What to do with pulses that extend beyond the end of the readout window? (reject?)
 
# Any other business
 
# Any other business
 
# Next meeting:  
 
# Next meeting:  
 
#* We are considering meeting on Tuesday at 1:30 pm, opposite to the F125 firmware meeting time. However, Matt has a conflict in two weeks.
 
#* We are considering meeting on Tuesday at 1:30 pm, opposite to the F125 firmware meeting time. However, Matt has a conflict in two weeks.
 
#* Next meeting: 9 am Tue Jul 14 (not a regular time)
 
#* Next meeting: 9 am Tue Jul 14 (not a regular time)

Revision as of 13:27, 30 June 2015

Video Conferencing Information

Meeting Time:

  1. To join via a Web Browser, go to the page [1] https://bluejeans.com/907185247.
  2. To join via Polycom room system go to the IP Address: 199.48.152.152 (bjn.vc) and enter the meeting ID: 907185247.
  3. To join via phone, use one of the following numbers and the Conference ID: 907185247.
    • US or Canada: +1 408 740 7256 or
    • US or Canada: +1 888 240 2560
  4. Upon connection all microphones are automatically muted. To unmute your mike on a Polycom or equivalent unit, enter *4. Unmuting on a computer is trivial as there is a microphone button than can be clicked.
  5. More information on connecting to bluejeans is available.

Participant Direct Lines

  • JLab Phone: in CC F326 is 757-269-6460 (usual room)
  • JLab Phone in CC L207 is 757-269-7084
  • Phone in the Regina Video-conference Suite is 306-585-4204
  • Athens Phone: in Christina's office is 011-30-210-727-6947

Action Items

FA125's Useful Links


References

Tentative Agenda

  1. Announcements
  2. Action Items
  3. Introduction (Elton)
  4. Priority List (all)
  5. Any other business

Minutes

Attendees:Naomi, Will (CMU); Matt, Mark, Elton (JLab)

  1. Announcements
  2. Action Items
  3. Introduction (Elton)
  4. Comments (Naomi)
    • Note differences between data modes and data types. A readout mode often enables several data types.
    • Example: Mode 7 outputs data types 7, 8 and 10; Mode 8 outputs data types 4, 8,10
  5. Comments (Elton)
    • Need 9 bits for channel id (slot 5 bits (0-31), channel 4 bits (0-15).
    • Need 14 bits for peak value (0-4095 + underflow + overflow)
    • Need >~16 bits for sum value (sum/peak ~ 15 for BCAL) + quality factor bits
    • Need >~15 for the FADC time (#samples x 64 > 400? x 64 = 25k).
    • Pedestal requirements? (depends strongly on algorithm)
    • Quality factors?
  6. Priority List (all)
    1. What is the impact of additional calorimeter data words on the GlueX rate capability? (David might be able to help with this).
    2. Pedestals: what is the best/optimal(?) method for pedestal determination and eventual subtraction from signal
      • consider a rolling average in the hardware for all pedestals? (compute pedestal of each channel every trigger to make pedestal determination independent of rate in that channel)
      • Do we need to use multiple events to determine the pedestal?
      • How does integer division affect the pedestal determination?
      • Use a single word for pedestal information, which would easily allow dropping in data stream at high rates?
    3. Signal
      • Are there advantages to variable length integration window? (if so, need to store number of summed samples, or subtract pedestal on the fly)
      • Peak vs sum (or integral). Save both?
      • Consider integration of a few samples around the peak to give a more precise "peak" value?
    4. Abnormal conditions
      • What to do with pulses that extend beyond the end of the readout window? (reject?)
  7. Any other business
  8. Next meeting:
    • We are considering meeting on Tuesday at 1:30 pm, opposite to the F125 firmware meeting time. However, Matt has a conflict in two weeks.
    • Next meeting: 9 am Tue Jul 14 (not a regular time)
Retrieved from "https://halldweb1.jlab.org/wiki/index.php?title=Jun_29,_2015_Cal_F250&oldid=68341"