FADC Data Format January 20, 2015

From GlueXWiki
Jump to: navigation, search

Location and Time

Room: CC F228??

Time: 2pm.

Remote Connection

(if problems, call phone in conference room: 757-269-6460 might not be the correct number)

  1. To join via Polycom room system go to the IP Address: 199.48.152.152 (bjn.vc) and enter the meeting ID: 589693655.
  2. To join via a Web Browser, go to the page [1] https://bluejeans.com/589693655.
  3. To join via phone, use one of the following numbers and the Conference ID: 589693655
    • US or Canada: +1 408 740 7256 or
    • US or Canada: +1 888 240 2560

More information on connecting to bluejeans is here

Specific instructions for connecting via polycom:

  • Turn polycom on if necessary
  • With the polycom, place a call at 199.48.152.152
  • Press # to enable the polycom keypad, then enter the meeting id: 589693655 and #
  • You may have to unmute the microphone: #*4
  • Turn the computer on if needed

Agenda


Useful Links

Minutes

Present: Cody, Simon, David, Beni (JLab), Naomi, Curtis (CMU)

  1. Bad boards - Cody has replaced the problem boards and checked the remaining new module (which was also problematic)
  2. FA250 firmware modifications - the issues to fix are
    1. block mode, Cody has replicated the error that Sergey found with large block sizes, this is fixable
    2. extra headers, the extra sets of headers for every 6 channnels (one set per FPGA chip) are redundant and can be removed, this is straightforward
    3. overall trigger rate, there have been problems with the data buffer getting overwritten if the window size is large, Cody thinks this can be fixed by increasing the front end buffer, he will have to investigate this further and will have a time estimate ready for the next meeting
  3. Next run - there is a loud rumour of beam on Feb 27. The firmware to be used for the run period needs to be handed over to the detector groups at least 2 weeks before the run period starts.
  4. FA125 firmware - Naomi has looked at errors encountered by the timing algorithm when using data from the CDC from the last run period, including the bad fadcs with bits missing from the sample values, and expanded the timing module to deal with these errors. Error conditions include adc value 0, adc value overflow, pedestal high at the start of the event, extreme gradients and negative upsampled values (the last two are sometimes caused by missing bits leading to a huge jump in sample value).
  5. Next meeting - we are going to increase the meeting frequency to weekly for the time being. The next meeting will be on 27 Jan 2015.
Retrieved from "https://halldweb1.jlab.org/wiki/index.php?title=FADC_Data_Format_January_20,_2015&oldid=80643"