Project

General

Profile

Detector Sync » History » Version 11

« Previous - Version 11/17 (diff) - Next » - Current version
Mathew Muether, 05/12/2011 09:53 AM


How to Issue a Detector Sync

Issue a synch:

Use the TDU Control Interface to issue a Detector Sync ONLY if autosyncsc fail.

Did it work?

Look for continuous tracks in the Event Display.

or

You can see whether the synch plausibly worked in watchSync.sh command.

If it worked, the "dcm-usl tcks:" value at the very end of the line should be O(10000) for all DCMs. (Beware of numbers so big they
wrap around the screen!)

root@dcm-06= nova: Thu Dec 30 05:13:37.357166 UTC 2010
unix: Thu Dec 30 05:13:37.355697 UTC 2010   dcm-unix usecs: 1469  dcm-usl tcks: 7440
root@dcm-08= nova: Thu Dec 30 05:13:36.181094 UTC 2010
unix: Thu Dec 30 05:13:36.213537 UTC 2010   dcm-unix usecs: -32443  dcm-usl tcks: 6072
root@dcm-09= nova: Thu Dec 30 05:13:38.599521 UTC 2010
unix: Thu Dec 30 05:13:38.504806 UTC 2010   dcm-unix usecs: 94715  dcm-usl tcks: 7808
root@dcm-11= nova: Thu Dec 30 05:13:36.889279 UTC 2010
unix: Thu Dec 30 05:13:36.883937 UTC 2010   dcm-unix usecs: 5342  dcm-usl tcks: 8276
root@dcm-12= nova: Thu Dec 30 05:13:37.649395 UTC 2010
unix: Thu Dec 30 05:13:37.612058 UTC 2010   dcm-unix usecs: 37337  dcm-usl tcks: 6116
root@dcm-13= nova: Thu Dec 30 05:13:36.005681 UTC 2010
unix: Thu Dec 30 05:13:36.245796 UTC 2010   dcm-unix usecs: -240115  dcm-usl tcks: 5240