Skip to content

Add derivation defintions and values to OpenMCT plugin #501

@nttoole

Description

@nttoole

Issue: OpenMCT plugin only sends a packet's fields, but not its derivations.

Fix: Update OpenMct to include derivations in both

  1. the telemetry dictionary definition
  2. a packet instance

More details:


  1. Update the section that converts to the telemetry dictionary into an OpenMCT JSON structure
    def format_tlmdict_for_openmct(ait_tlm_dict):

I suspect there is enough commonality between fields and derivation objects (name, units, type) that you could just add another loop that iterates over a packet-def’s derivationmap, almost a parallel of what it does for fieldmap:

ait_pkt_fieldmap = ait_pkt_def.fieldmap


  1. Update the section that converts a telemetry packet
    ait_pkt_fieldmap = ait_pkt_def.fieldmap

Similar to part 1, add a second loop the parallels fieldmap but for derivationmap.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions