Change how stale data is interpreted

Note: For information on overriding default configuration settings, refer to Modify configuration settings.

It is possible to change the way data quality is interpreted.

• By default, when host-calculated data is sent to AVEVA Measurement Advisor, it marks the data as Invalid if any of the input points to the calculation were stale at any time during the calculation period.

• If the -q option is set, host-calculated data will be sent to AVEVA Measurement Advisor with an Unassigned data quality and AVEVA Measurement Advisor will assign the data quality based on the processing of the data.

To change how data quality is assigned

1. In the %DNADataRoot%\RealTime\config\Settings directory, either create or open the RealTime_monitorGasQualityHost.json file:

   {

   "RealTime": {

   "monitorGasQualityHostCalc": {

   "Debuglevel": 3,

   "CriticalTask": false,

   "QualityIsAlwaysUnassigned": false,

   "CycleTime": "00:01:00",

   "PostHotDelay": "00:00:30"

   }

   }

   }

2. Use the table below as a guide to modifying any key values in the JSON file.

3. Save the file.

4. Restart the RealTime service.

   Key	Description
   QualityIsAlwaysUnassigned	Change the value of QualityIsAlwaysUnassigned from false to true to make the system send host-calculated data to AVEVA Measurement Advisor with a data quality of "Unassigned". AVEVA Measurement Advisor will assign the data quality based on the processing of the data. Note: By default, when the system sends host-calculated data to AVEVA Measurement Advisor, it marks the data as "Invalid" if any of the input points to the calculation were stale at any time during the calculation period.
   CriticalTask	If you want a RealTime failover to occur when monitorMeterHostCalc doesn't check into the RealTime service within its check-in timeout, change the value of CriticalTask from false to true.
   DebugLevel	Modify DebugLevel to adjust the default debug setting for the application. Debug level values range from 0 to 6, with 0 producing the lowest amount of messages (that is, Fatal level). The default level for all processes is usually 3 (DebugLog level). For more information on debug levels, refer to "Enable Logging" in the Advanced Database Editor (ADE) user documentation.
   CycleTime	Modify CycleTime to adjust the frequency of monitorMeterHostCalc calculations. The system makes the check-in timeout three times the value of the CycleTime.
   PostHotDelay	To adjust the waiting period for the start of processing after going Hot, change the value of PostHotDelay.