3. ct command

ct performs an individual count and writes the result to the console. To learn about performing counts as part of a sequence, trajectory, or script, go to Sequences, the Trajectory Guide, or Scripts.

The counter can be set to count against time, monitor, or a region of interest (ROI) on a detector OR any combination of these criteria.

For example, to count against time for 10 seconds, use the -t flag,

To count against monitor, use the -m flag. In the following example,

the count will continue until the monitor has detected 10,000 neutrons.

Counting against ROI requires you to use the -r flag in conjunction with the -d flag. -r specifies the number of neutrons at which counting should terminate, while -d specifies the name of the logical detector whose region of interest should be used.

In the below example,

The system will count until 5 seconds pass OR the accumulated region of interest sum across the area detector exceeds 20,000 neutrons.

NOTE: To use the ROI option you must set an appropriate ROI mask on the detector you are interested in. The ROI mask represents a per pixel weight across an entire logical detector. This can be set by moving the mask directly through a script to an arbitrary configuration or by using a convenience command at the console to set it to a common shape.

Here is an example of counting against time, monitor, and ROI:

The above count will continue until 5 seconds have passed, the monitor reaches 10,000 counts, or the accumulated ROI sum across the area detector exceeds 20,000 counts.

IMPORTANT: When counting against time or monitor, the system will never undercount or overcount. This is guaranteed because the counter hardware uses electronic gating in its data collection.

When counting against multiple criteria, the count will end when ANY of the criteria is met, NOT when all criteria are met. When counting against multiple criteria and/or ROI, the system may overcount. For example, you ask the system to collect counts for 20 seconds or until you reach 10,000 monitor counts (ct -t 20 -m 10000); however, the count ends at 18.2 seconds having recorded 10,027 monitor counts. These additional 27 counts get recorded because of a time lag in the software communicating to the hardware that it should stop counting.