90 likes | 228 Views
DOM Hub Software. Test DAQ Workshop LBNL, July 24, 2003 David Hays. Topics. Hub Software development goals Dependencies, Position in DAQ DH App Design Overview DH App Status DH App Next Steps DH Driver Status. Development Goals.
E N D
DOM Hub Software Test DAQ Workshop LBNL, July 24, 2003 David Hays
Topics • Hub Software development goals • Dependencies, Position in DAQ • DH App Design Overview • DH App Status • DH App Next Steps • DH Driver Status
Development Goals • Provide data collection over “fast” twisted pair communication using DH Application, DH Driver, DOR Cards, DOM App ASAP • Provide DOM configuration in line with all DOM App supported slow control functions • Provide discovery and management (resource locking) for all DOMs attached to Hub • Provide conduit/proxy for client applications that interact with DOM programs (stfclient, bootclient, etc.)
DH App Design Overview • Remote Interface – currently ten methods accessed via RMI by client applications • DH “Core” singleton objects manage available card and DOM objects • DOM objects extend Thread (1 thread per DOM), start() begins loop of generated data access/ monitor msgs, writing results to SocketChannels • Current “vocabulary” of ~40 DOM App msgs
DH App Status • Testing / debugging – DOM App msg API • Imminent working build • Attention areas • Hw availability • Configuration management • Stability of underlying sw, firmware, hw increasing • Next Steps
DH App Next Steps • Get working DH App out for PSL use • Modifications related to addition of Config Boot • Support for monitor streams as DOM App provides monitor msg support • Changes to remote interface transfer objects • Socket mode – impacts STF Client • Documentation for DH App and DOM App interfaces • Testing with multiple DOMs, DOR cards
DH Driver Status(on behalf of John Jacobsen) • latest documentation available at: ftp://it.johnj.com/pub/icecube/domhub/driver/doc/ • Working on test script for regression testing • Most control functions there, no time calib yet • Incremental improvements / bug fixes • Added is-communicating, revision proc files (thanks) • Debugging rare2 DOM on one pair glitch • Measure 95 kB/sec rate per pair • Need to test with more DOMs, DOR cards • New Linux kernel will require further driver tests
Wrap up • Questions and discussion • Dehays@lbl.gov