Difference between revisions of "FA125 Data Format Sep 8, 2015"
From GlueXWiki
(→Agenda) |
m (Text replacement - "http://argus.phys.uregina.ca/cgi-bin/private" to "https://halldweb.jlab.org/doc-private") |
||
| (6 intermediate revisions by one other user not shown) | |||
| Line 48: | Line 48: | ||
== Useful Info == | == Useful Info == | ||
| − | [[File: FADC125_Format_v6.5.pdf|Latest format spec draft v 6.5]] | + | *[[File: FADC125_Format_v6.5.pdf|Latest format spec draft v 6.5]] |
| − | + | *[https://halldweb.jlab.org/doc-private/DocDB/ShowDocument?docid=2274 fADC125 Data Format Specification Document in DocDB - version 7] | |
* [[CDC_algo|Timing algorithm wiki page]] | * [[CDC_algo|Timing algorithm wiki page]] | ||
* Older documents: | * Older documents: | ||
| − | |||
** [[:File:FADC125_dataformat_250_modes.docx|Data format for 250 modes on fADC125 from Cody, Aug 15 2014]] | ** [[:File:FADC125_dataformat_250_modes.docx|Data format for 250 modes on fADC125 from Cody, Aug 15 2014]] | ||
** [[:File:FADC250_modes_2.docx|FA250 modes 2 from Ed and Hai, Feb 18 2014]] | ** [[:File:FADC250_modes_2.docx|FA250 modes 2 from Ed and Hai, Feb 18 2014]] | ||
| Line 59: | Line 58: | ||
=Minutes= | =Minutes= | ||
| + | Present: Naomi (CMU), Cody, David, Beni, Sergey (JLab) | ||
| + | * Firmware status - Cody has a firmware version which contains all readout modes, he and Naomi have been doing some initial testing with it and identified and fixed some problems. All the changes have been made to bring it up to date with the latest format spec (6.5). Cody has started using a program called smartexplorer to optimize the timing. It tries several different map setups as starting points and optimizes the routing for these, usually around 4 iterations are required and take about an hour, but occasionally 100 iterations are required, which take days. | ||
| + | * Naomi will send Cody test pulses with the fadc output and her C-script comparisons. | ||
| + | * We need to check whether Lubomir needs the extra mode fdc_amp_long. | ||
| + | * Sergey asked for the current firmware to be put onto Roctag1 | ||
| + | * The firmware should be ready for testing in Hall D before long. | ||
Latest revision as of 17:05, 24 February 2017
Location and Time
Room: CC F326 ?
Time: 2pm.
Remote Connection
You can connect using BlueJeans using the meeting number 589 693 655 . (Click "Expand" to the right for more details -->):
(if problems, call phone in conference room: 757-269-6460 might not be the correct number)
- To join via Polycom room system go to the IP Address: 199.48.152.152 (bjn.vc) and enter the meeting ID: 589693655.
- To join via a Web Browser, go to the page [1] https://bluejeans.com/589693655.
- 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
- Previous meeting (Aug 25, 2015)
- FADC125 Firmware status
- Driver library status
- Catch up on format spec changes since last meeting:
- Requested mode names:
- cdc
- fdc
- fdc_amp
- cdc_long
- fdc_long
- and fdc_amp_long if Lubomir decides he needs it. ????
- Requested mode names:
Useful Info
- File:FADC125 Format v6.5.pdf
- fADC125 Data Format Specification Document in DocDB - version 7
- Timing algorithm wiki page
- Older documents:
- For integral examples see FA125_Data_Format_July_7,_2015#Agenda
Minutes
Present: Naomi (CMU), Cody, David, Beni, Sergey (JLab)
- Firmware status - Cody has a firmware version which contains all readout modes, he and Naomi have been doing some initial testing with it and identified and fixed some problems. All the changes have been made to bring it up to date with the latest format spec (6.5). Cody has started using a program called smartexplorer to optimize the timing. It tries several different map setups as starting points and optimizes the routing for these, usually around 4 iterations are required and take about an hour, but occasionally 100 iterations are required, which take days.
- Naomi will send Cody test pulses with the fadc output and her C-script comparisons.
- We need to check whether Lubomir needs the extra mode fdc_amp_long.
- Sergey asked for the current firmware to be put onto Roctag1
- The firmware should be ready for testing in Hall D before long.
