| Member | Description |
|---|---|
| DualThresholdLegacy | Deprecated. Use the SingleThreshold enum value for all new OMR processing scenarios. Specifies that the Dual Threshold Legacy engine should be used to process the field. |
| SingleThreshold | Specifies that the Single Threshold engine should be used to process the field. |
This enumeration exposes values that allow specification of the recognition engine to be used by the OmrProcessor for OMR analysis of an OMR field.
The OmrProcessor implements two different engines, a Single Threshold based engine and a Dual Threshold Legacy engine (which has been carried forward from previous releases of FormFix). The Dual Threshold Legacy engine is deprecated and should no longer be used.
Use of the Single Threshold engine is recommended and is the default engine used by the OmrProcessor. This engine has been optimized for usability of the Threshold and of the Confidence values that it returns. This engine is as capable as the Dual Threshold Legacy engine, and combined with its improved usability it will generate better results.
Use of the Dual Threshold engine is highly discouraged. The Dual Threshold Legacy engine is implemented in this release only to support reading (see OmrProcessor.ReadFromStream) serialized OmrProcessor streams that were written by previous versions of FormFix. The Dual Threshold Legacy recognition engine was the only engine implemented in these versions and therefore the stream content is specific to this engine.
It is okay to perform OMR (see OmrProcessor.AnalyzeField) with an OmrProcessor that is configured to use the Dual Threhold Legacy engine, but only if it was configured that way only by the OmrProcessor.ReadFromStream method. Also in this case, it is also okay to adjust the threshold properties (OmrProcessor.UnmarkedBubbleThreshold and OmrProcessor.MarkedBubbleThreshold)
System.Object
System.ValueType
System.Enum
Accusoft.FormFixSdk.RecognitionEngine