Difference between revisions of "How to check the deadtime for the electronics and trigger?"
Jump to navigation
Jump to search
(Created page with "[https://wiki.jlab.org/tegwiki/index.php/Main_Page <B>Back to Tritium-Main</B>] [https://wiki.jlab.org/tegwiki/index.php/How-To_and_Shift_Info <B>Back to How to</B>] [https://...") |
|||
| Line 1: | Line 1: | ||
| − | [https://wiki.jlab.org/tegwiki/index.php/Main_Page <B>Back to Tritium-Main</B>] [https://wiki.jlab.org/tegwiki/index.php/How-To_and_Shift_Info <B>Back to How to</B>] [https://wiki.jlab.org/tegwiki/index.php/Third <B> Back to Third Person] | + | [https://wiki.jlab.org/tegwiki/index.php/Main_Page <B>Back to Tritium-Main</B>] [https://wiki.jlab.org/tegwiki/index.php/How-To_and_Shift_Info <B>Back to How to</B>] [https://wiki.jlab.org/tegwiki/index.php/Third <B> Back to Third Person]</B> |
[[complete guide|Direct link to the entire repository of information.]] | [[complete guide|Direct link to the entire repository of information.]] | ||
| + | |||
| + | |||
| + | <B> 1. Real time deadtime from Datamon</B> | ||
| + | |||
| + | The Datamon provides real time deadtime information. It's generated from trigger supervisor. Its two internal scalers will record clock counts of the runtime and TS busy time. Then provide busy/full time as the deadtime | ||
| + | |||
| + | <B> 2. Trigger deadtime calculation from script</B> | ||
| + | |||
| + | After a run is fully replayed, one can log in aonl machine and: | ||
| + | |||
| + | gotritium | ||
| + | |||
| + | analyzer scripts/deadtimeL(or R).C | ||
| + | |||
| + | Provided run number, the script will return the deadtime by triggers. Note that it will only give reasonable answer if the rootfile countains large amount of events | ||
Latest revision as of 20:19, 8 December 2017
Back to Tritium-Main Back to How to Back to Third Person
Direct link to the entire repository of information.
1. Real time deadtime from Datamon
The Datamon provides real time deadtime information. It's generated from trigger supervisor. Its two internal scalers will record clock counts of the runtime and TS busy time. Then provide busy/full time as the deadtime
2. Trigger deadtime calculation from script
After a run is fully replayed, one can log in aonl machine and:
gotritium
analyzer scripts/deadtimeL(or R).C
Provided run number, the script will return the deadtime by triggers. Note that it will only give reasonable answer if the rootfile countains large amount of events