[Halld-online] Minutes of Online meeting

David Lawrence davidl at jlab.org
Wed May 18 17:18:26 EDT 2016


Minutes from today’s online meeting can be found on the following wiki page and copied below

https://halldweb.jlab.org/wiki/index.php/OWG_Meeting_18-May-2016

Regards,
-David

Minutes[edit]

Attendees: David L. (chair), Curtis M., Sergey F., Carl T., Beni Z., Vardan G., Naomi J., Sean D., Dave A., Alex S.
Announcements
Regarding new farm nodes: Dave A. noted that these will be very new CPUs and may not be fully supported by RHEL6. We may need to run RHEL7 on them. We'll address that once they arrive and the CC can explain the issues to us.
Compiler upgrade (gcc 4.9.2)
No significant discussion here since Hovanes was not present. Sergey suggested we could consider specifying some computers as having the "controls" environment by default. This would have gcc 4.4.7 be the default compiler. All other computers could then default to a different compiler.
JinFlux slides
Vardan presented some slides on the JinFlux package he authored which provides a Java interface to an Influx DB
The Influx DB is useful for information that has a limited shelf life before becoming obsolete
The Grafana package provides a way to build graphical displays of the data contained in the DB
Vardan has both the DB server and the Grafana server running on claraweb.
We could write values into it from our DAQ system and then build a dashboard that could display it offsite
He showed a working example at http://claraweb.jlab.org:3000
Reboot Notifications
David has implemented a system to send e-mail notification to him whenever a node reboots
This may help identify which nodes are problematic and how often spontaneous reboots are occurring
It was noticed that some nodes seem to reboot at the same time every day or every couple of days
No one else expressed interest in getting these e-mails (??)
DAQ
Several new firmware versions are now (or very soon will be) available
These include fADC125, fADC250, CTP, SSP, F1TDC
Cody and Ben were going to do a single crate test using the BUSY mechanism and Sergey will help with a test that includes the TS
Alex S. will be installing and testing the other firmware over the summer starting sometime in June
He will start with the new fADC250 firmware which has many new features and provides data in a new format
Alex will provide David with an example file and a format specification once the initial testing is done and they become available
Playback features in the new firmware will allow tuning of the trigger parameters
Different holdoffs may be programmed for different triggers allowing the first few triggers to have a smaller holdoff than the last which needs a longer holdoff
Up to now, we have used only a single holdoff for all triggers. Alex will do some measurments this summer to tune these in order to maximize rate/livetime
CODA 3.06 is nearly ready for release. Dave A. expects to deploy it by the end of next week
Sergey noted that once we get past the current bottleneck due to the holdoff time then we may quickly encounter another bottleneck due to the DMA setup/transfer time
The argument was that there is a 4MB limit on a single DMA transfer. This limits the number of events that can fit inside a block when each fADC125 has full occupancy
There was some discussion on this but details would need to be hashed out offline
Sergey noted that there is also a potential bottleneck looming from the tagger crate due to it reading out 60-70MB/s on a 1Gb interface
Dave A. said he has a couple of 10Gb cards we could test
Alex S. noted that the tagger readout window is quite large and could be reduced which would have a significant impact
L3 Status
Meeting tomorrow at 3pm
ROL status (SYNC events)
Some data has been implemented and Alex has plans to include more diagnostics information
Documentation doesn't yet exist, but he will supply code or a document once things are more final
Sync events in Spring data are currently ignored by the sim-recon parser

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.jlab.org/pipermail/halld-online/attachments/20160518/bcbf95af/attachment.html>


More information about the Halld-online mailing list