areaDetector Plugin NDPluginCircularBuff

Contents

• Overview
• Configuration
• Screen shots
• Restrictions

Overview

NDPluginCircularBuff is a triggering plugin. It receives NDArrays from a plugin or driver and checks whether a user-defined trigger condition has been met. The trigger condition is based on the values of up to two NDAttributes attached to the NDArray. The attribute values are used in a general calculation expression that defines the trigger condition. Once the trigger condition is detected the plugin outputs the triggering NDArray, along with a configurable number of pre- and post-trigger NDArrays. Triggering can also be performed using a soft trigger, controlled from the "Trigger" database record.

Acquisition is started by setting the "NDCircBuffControl" parameter to non-zero (via the "Capture" record in the associated database). The plugin then copies all received NDArrays to its ring buffer, wrapping once the specified pre-count is reached.

Once the trigger is detected, the plugin will immediately output all the NDArrays stored in the ring buffer in order from oldest to newest (by calling doCallbacksGenericPointer). After the trigger is set, new NDArrays will then be output as soon as they arrive, until the post-count is reached. The plugin will then stop buffering or outputting NDArrays until it is restarted via NDCircBuffControl. The plugin will also automatically restart if the following condition is true:

     (PresetTriggerCount == 0) || ((PresetTriggerCount > 0) && (ActualTriggerCount < PresetTriggerCount)))
    

NDPluginCircularBuff inherits from NDPluginDriver. The NDPluginCircularBuff class documentation describes this class in detail.

NDPluginCircularBuff defines the following parameters. It also implements all of the standard plugin parameters from NDPluginDriver . The EPICS database NDCircularBuff.template provides access to these parameters, listed in the following table.

Triggering using NDArray attributes is quite powerful. Two NDArray attributes can be used for triggering. The names of these attributes are defined with the TriggerA and TriggerB records. The values of these attributes must be numeric, not string. The TriggerCalc record defines a calculation expression that uses that same syntax as the EPICS calc record. If the expression evaluates to a non-zero value then the plugin will be triggered. The variables in the expression are defined as follows:

• A The current value of the NDAttribute defined by TriggerA.
• B The current value of the NDAttribute defined by TriggerB.
• C The value of the PreCount record
• D The value of the PostCount record
• E The value of the CurrentQty_RBV record
• F The value of the PostTriggerQty_RBV record
• G The value of the Trigger_RBV record

The following are some example expressions. They assume that the NDPluginCircularBuff plugin is getting its data from the NDPluginStats plugin and that the NDPluginStats plugin is using an attributes XML file containing the following lines:

   <attribute name="MaxValue"  type="PARAM" source="MAX_VALUE"       datatype="DOUBLE" description="Maximum value" />
   <attribute name="CentroidX" type="PARAM" source="CENTROIDX_VALUE" datatype="DOUBLE" description="Centroid X position" />
  

Assume that TriggerA is set to MaxValue and TriggerB is set to CentroidX.

The following are examples of some expressions that can then be used for triggering:

If the TriggerA or TriggerB attrbutes do not exist, or if they are non-numeric datatype then the TriggerAVal or TriggerBVal is set to NaN (Not a Number). If that value is used in the calculation expression then in some cases the TriggerCalcVal will also be NaN (for example A+B will be NaN). If TriggerCalcVal is NaN or Infinity then the expression is treated as 0 and the trigger will not occur. However, some expressions involving NaN arguments do not result in a NaN result and could result in false triggers. For example (A&&B) evaluates as 1 when both A and B are NaN. To avoid this problem the isnan() and isinf() functions can be used in the expression.

It is possible to continuously output individual NDArrays that match the trigger condition. To do this set PreCount=0, PostCount=1, and PresetTriggerCount=0.

Screen shots

The following is the MEDM screen that provides access to the parameters in NDPluginDriver.h and NDPluginCircularBuff.h through records in NDPluginBase.template and NDCircularBuff.template.

Configuration

The NDPluginCircularBuff plugin is created with the NDCircularBuffConfigure command, either from C/C++ or from the EPICS IOC shell.

NDCircularBuffConfigure(const char *portName, int queueSize, int blockingCallbacks,
                        const char *NDArrayPort, int NDArrayAddr,
                        int maxBuffers, size_t maxMemory)
  

For details on the meaning of the parameters to this function refer to the detailed documentation on the NDCircularBuffConfigure function in the NDPluginCircularBuff.cpp documentation and in the documentation for the constructor for the NDPluginCircularBuff class.

In particular, note that maxBuffers constrains the size of the ring buffer - the plugin will discard any changes to the pre- or post count if this would result in (pre-count + post-count) exceeding maxBuffers.