Update Config_Detector
@@ -134,7 +134,7 @@ However, detectors that provide multiple values, e.g. area detectors, tend to al
|
||||
 **Default**: 0.0
|
||||
|
||||
**getDataTimeout**::<BR>
|
||||
 Double value that defines the number of seconds to wait for data to be received before moving on to the next scan point. <BR>
|
||||
 Double value that defines the number of seconds to wait for data to be received before moving on to the next scan point. Data that is not received is written as `NaN` in data file.<BR>
|
||||
 **Default**: 0.15
|
||||
|
||||
**details**::<BR>
|
||||
@@ -152,21 +152,10 @@ However, detectors that provide multiple values, e.g. area detectors, tend to al
|
||||
 **Default**: empty string
|
||||
|
||||
**getDataTimeout**::<BR>
|
||||
 Double value that defines the number of seconds to wait for data to be received before moving on to the next scan point. <BR>
|
||||
 Double value that defines the number of seconds to wait for data to be received before moving on to the next scan point. Data that is not received is written as `NaN` in data file.<BR>
|
||||
 **Default**: 0.15
|
||||
|
||||
**details**::<BR>
|
||||
 Integer value that defines the length of the data array (always 1D) that will be returned by an "Epics" detector. Note that Pixelator requires detectors to additionally return a summary of the data array as a single value per scan point.<BR>
|
||||
 Integer value that defines the length of the data array (always 1D) that will be returned by the detector. Note that _Pixelator_ requires detectors to additionally return a summary of the data array as a single value per scan point.<BR>
|
||||
 **Default**: 0
|
||||
|
||||
****::<BR>
|
||||
 Integer value that defines <BR>
|
||||
 **Default**: ?
|
||||
|
||||
****::<BR>
|
||||
 Integer value that defines <BR>
|
||||
 **Default**: ?
|
||||
|
||||
****::<BR>
|
||||
 Integer value that defines <BR>
|
||||
 **Default**: ?
|
||||
Reference in New Issue
Block a user