Difference between revisions of "Scalers"
From HallCWiki
| (2 intermediate revisions by one other user not shown) | |||
| Line 1: | Line 1: | ||
| + | === Read scalers using xscaler GUI === | ||
| + | |||
| + | *Login as cdaq to cdaql1 | ||
| + | **To see HMS scalers type: <tt>go_xscaler_hms</tt> | ||
| + | **To see SHMS scalers type: <tt>go_xscaler_shms</tt> | ||
| + | *The file scaler.map, located in <tt>~/SCALERS</tt>, is used to map the names to the scaler crate, slot and chan. | ||
| + | |||
== Hardware Configuration == | == Hardware Configuration == | ||
*HMS scalers are a VME crate. The cpu is hcvme05. | *HMS scalers are a VME crate. The cpu is hcvme05. | ||
| Line 8: | Line 15: | ||
*To directly read the scalers | *To directly read the scalers | ||
** login is as cdaq on cdaql1 | ** login is as cdaq on cdaql1 | ||
| − | * | + | *** execute: <tt>getscalers hcvme05</tt> for HMS |
| − | ** execute: | + | *** execute: <tt>getscalers hcvme08</tt> for SHMS |
| − | ** execute: | + | ** There is an option to clear the scalers, put please do '''not''' do this in the middle of the run! |
| − | ** There is an option to clear the scalers, put please do not do this in the middle of the run! | + | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
== Analysis Software == | == Analysis Software == | ||
Latest revision as of 18:17, 23 August 2018
Contents
Read scalers using xscaler GUI
- Login as cdaq to cdaql1
- To see HMS scalers type: go_xscaler_hms
- To see SHMS scalers type: go_xscaler_shms
- The file scaler.map, located in ~/SCALERS, is used to map the names to the scaler crate, slot and chan.
Hardware Configuration
- HMS scalers are a VME crate. The cpu is hcvme05.
- SHMS scalers are a VME crate. The cpu is hcvme08.
Scaler Software
Scaler Server
- To directly read the scalers
- login is as cdaq on cdaql1
- execute: getscalers hcvme05 for HMS
- execute: getscalers hcvme08 for SHMS
- There is an option to clear the scalers, put please do not do this in the middle of the run!
- login is as cdaq on cdaql1
