Difference between revisions of "Jun 29, 2015 Cal F250"
From GlueXWiki
(→Minutes) |
(→Minutes) |
||
(One intermediate revision by the same user not shown) | |||
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? | ||
+ | # Questions (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) |
Latest revision as of 15:54, 30 June 2015
Contents
Video Conferencing Information
Meeting Time:
- To join via a Web Browser, go to the page [1] https://bluejeans.com/907185247.
- To join via Polycom room system go to the IP Address: 199.48.152.152 (bjn.vc) and enter the meeting ID: 907185247.
- 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
- 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.
- 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
- FA250 modes 2 from Ed and Hai, Feb 18 2014
- FIRMWARE for FADC250 Ver2 ADC FPGA, Sept 2014?
- Format doc version 5.06, 23 June 2015
- Timing algorithm wiki page - updated to include latest revisions
- Data format for 250 modes on fADC125 from Cody, Aug 15 2014
- FDC_pulse_data_format
- CDC readout needs Garfield calcs
References
Tentative Agenda
- Announcements
- Action Items
- Introduction (Elton)
- Priority List (all)
- Any other business
Minutes
Attendees:Naomi, Will (CMU); Matt, Mark, Elton (JLab)
- Announcements
- Action Items
- Introduction (Elton)
- 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
- 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?
- Questions (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
- 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)