September 19, 2018 online meeting minutes: Difference between revisions
Jump to navigation
Jump to search
Created page with "present: Sergey Boyarinov, Clas On-line Meeting, Wednesday, September 19 at 10am in Room A110 * FADC/MM packing and decoding: * new RF board: * Trigger validation: *..." |
No edit summary |
||
| Line 1: | Line 1: | ||
present: Sergey Boyarinov, | present: Sergey Boyarinov, | ||
* FADC/MM packing and decoding: FADC packing is implemented completely, including offline decoder and monitoring tools; data were taken in verification mode and both packed and unpacked banks are identical; Micromega packing is installed and data were taken, micromega team is checking consistency | |||
* new RF board: MO (Master Oscillator) board was installed in scaler1 crate slot 20, library from Bryan Moffit installed and included into readout list, will take data and check if it works as it suppose to; signals on scope looks much better then from old board, and we can control rescale now; board has 5 outputs so one more idc or fadc channel can be used to record RF information | |||
* new RF board: | |||
* Trigger validation: | * Trigger validation: | ||
* activemq broker: 'standard' configuration lead to memory usage increased up to max=4G during about a week, after that cpu usage came up from 8% to 38% and few second delays were observed in messages delivery; Sergey modified config using advices found in google (G1 garbage collector was activated) and now memory usage have regular fluctuations between 0.5G and 1G with 10-12min period, will run like this and see how it behaved in long term | * activemq broker: 'standard' configuration lead to memory usage increased up to max=4G during about a week, after that cpu usage came up from 8% to 38% and few second delays were observed in messages delivery; Sergey modified config using advices found in google (G1 garbage collector was activated) and now memory usage have regular fluctuations between 0.5G and 1G with 10-12min period, will run like this and see how it behaved in long term | ||
Revision as of 08:38, 19 September 2018
present: Sergey Boyarinov,
- FADC/MM packing and decoding: FADC packing is implemented completely, including offline decoder and monitoring tools; data were taken in verification mode and both packed and unpacked banks are identical; Micromega packing is installed and data were taken, micromega team is checking consistency
- new RF board: MO (Master Oscillator) board was installed in scaler1 crate slot 20, library from Bryan Moffit installed and included into readout list, will take data and check if it works as it suppose to; signals on scope looks much better then from old board, and we can control rescale now; board has 5 outputs so one more idc or fadc channel can be used to record RF information
- Trigger validation:
- activemq broker: 'standard' configuration lead to memory usage increased up to max=4G during about a week, after that cpu usage came up from 8% to 38% and few second delays were observed in messages delivery; Sergey modified config using advices found in google (G1 garbage collector was activated) and now memory usage have regular fluctuations between 0.5G and 1G with 10-12min period, will run like this and see how it behaved in long term