Filters

Mining

• all filter definitions are passsed to the oci_extract_hk_data, and it generates full/delta, time bin, and marker binned filtered data. The filtered data output files are associated with each filter definition ID
• This filtered data can be used to plot filtered data through the OCI HK tool (full/delta and time binned)
• Generate filtered trend data

Exporting

• Filter definitions can be associated with a profile's filter field. The JSON filter key can use either the filter definition's ID or name. If the filter definitions associated with a profile have mnemonics that overlap, the first filter (by JSON array index) will be applied and others are ignored (a warning message will be output by oci_extract_hk_data).

[
  {
    "filter": "om_visnir_on"
  },
  {
    "filter": "om_uvvis_on"
  },
  {
    "filter": "valid_dauc_tlm"
  }
]

• One off filters can be defined before exporting by inputting the filter condition into the "filter configuration" box. You can also define which HKIDs the filter should be applied to. In the below example, because "hks" is not specified, the filter will be applied to all mnemonics. The ":" prefix in the mnemonic name is there for legacy reasons but may not be required in future versions.

Here is another example that specifies a list of HKIDs to apply the filter to:

[
  {
    "hks": "42314, 42316, 42318, 42319, 42320, 42321, 42322, 42332, 42333",
    "condition": ":oci.mce.rtaham.RotatingSynchronized == 1",
    "name": "MCE_SPINNING"
  }
]