CODA: Difference between revisions
Jump to navigation
Jump to search
| Line 10: | Line 10: | ||
* call 'ROL1::__end()' routine; it disables triggers and calls 'blocksLeft = tiBReady()' until nothing left, or until timeout | * call 'ROL1::__end()' routine; it disables triggers and calls 'blocksLeft = tiBReady()' until nothing left, or until timeout | ||
* call 'codaUpdateStatus("ending")' | |||
* sets 'tcpState = rocp->state = DA_ENDING' and 'rocp->active = 2' | * sets 'tcpState = rocp->state = DA_ENDING' and 'rocp->active = 2' | ||
Revision as of 13:13, 2 May 2019
CODA is DAQ software designed and supported by JLAB CODA group. This section contains some information related to the use of CODA in Hall B.
End transition
Executed in the order opposite to 'Go' transition: TS ROC first, then all remaining ROCs, then EB.
First coda_roc::codaEnd() called, it does following:
- call 'ROL1::__end()' routine; it disables triggers and calls 'blocksLeft = tiBReady()' until nothing left, or until timeout
- call 'codaUpdateStatus("ending")'
- sets 'tcpState = rocp->state = DA_ENDING' and 'rocp->active = 2'
VME Controllers: Intel-based FANUC under RHEL OS
CODA group install RHEL OS into flash memory, so it boot after power recycle. Auto mount and some other stuff must be adjusted for clon cluster: