February 26, 2020 online meeting minutes: Difference between revisions
Jump to navigation
Jump to search
Created page with "present: Sergey Boyarinov, Stepan, Nathan, Valery, Ben 1. RG-F run status * DAQ event rate is only few kHz, data rate significantly below 100MB/s because of gas target, wi..." |
No edit summary |
||
| Line 11: | Line 11: | ||
* beam current unlikely to be increased, so we will stay with current settings for entire run | * beam current unlikely to be increased, so we will stay with current settings for entire run | ||
* event rate/data rate were added to DAQ/Trigger EPICS GUIs | |||
* MPOD power supply has some issues - Nathan | |||
* logbook GUI insertion policy may be reconsidered - too many GUIs in logbook | |||
* some network switches keeps dying, replacement installed already on FC, moving wires there; port 48 is set to 10MBit/fullduplex for etherlite32 | |||
Revision as of 10:25, 26 February 2020
present: Sergey Boyarinov, Stepan, Nathan, Valery, Ben
1. RG-F run status
- DAQ event rate is only few kHz, data rate significantly below 100MB/s because of gas target, with beam current 250nA
- trigger is electron with drift chamber roads and 300MeV EC threshold, seems sufficient for production running
- big dead time produced by RTPC readout, cannot run faster then about 1.5kHz if desired lifetime is above 90%
- beam current unlikely to be increased, so we will stay with current settings for entire run
- event rate/data rate were added to DAQ/Trigger EPICS GUIs
- MPOD power supply has some issues - Nathan
- logbook GUI insertion policy may be reconsidered - too many GUIs in logbook
- some network switches keeps dying, replacement installed already on FC, moving wires there; port 48 is set to 10MBit/fullduplex for etherlite32
2. Streaming DAQ progress
- still need to fix VTP TCP/IP issues (Ben)
- reconstruction algorithms to be considered for online data processing: offline code, level1 code, ...; can be tested as 'level3' in current DAQ