OCI User Guide

Export Plot configuration: JSON Format

We use matplotlib v3.1.3 for our plot generation. The plot report is configured using JSON. The top level global applies global configuration. It currently supports a limited subset of the rcParams: font_size, font_family, agg_path_chunksize. Future versions will support all rcParams keys. The global["plot_options"] can be used to configure plot options for all series. This is convenient if you want to apply an option to all series without having to define it for each one.

plot_options can also be defined at the plots level, which will apply to each series within a plot, or at the series level, which will apply to a specific series. All plot_options (global, plot, and series) are merged together when plotting each series, with the series plot_options having the highest precedence, then plot, then global. The plot_options at any level supports all matplotlib Line2D properties.

You may define the height_ratio as part of the plot object to control how much vertical space it takes up. Defaults to a value of 1.

Any option may be omitted entirely and a default value will be used.

Below is an example JSON plot config file. Note that pages and plots are JSON arrays which implies the generated pages and plots are ordered accordingly.

{
  "global": {
      "plot_options": {
        "linewidth": 0.3,
        "marker": "d",
        "markersize": 3
      },
      "font_size" : 10,
      "font_family" : "monospace",
      "agg_path_chunksize": 10000
  },
  "pages": [
    {
      "plots": [
        {
          "title": "1st plot on page 1",
          "series": [
              { 
                  "mnemonic": "oci.dau.boxrack.power.PS01.m1curoutp",
                  "plot_options": {"marker": "x"}
              }
          ],
          "plot_options": { "color": "red" },
          "y_min": -5,
          "y_max": 5
        }
      ]
    },
    {
      "plots": [
        {
          "title": "2 plots on page 2",
          "height_ratio": 2,
          "series": [
            {
              "mnemonic": "oci.dau.dauc.Tlm.Red_BdTemp3",
              "plot_options": {
                "color": "r"
              }
            },
            {
              "mnemonic": "oci.dau.dauc.Tlm.Blue_BdTemp3",
              "plot_options": {
                "color": "b"
              }
            }
          ]
        },
        {
          "height_ratio": 1,
          "series": [
            {
              "mnemonic": "oci.dau.ddc.FPGA.CcdOpMode",
              "plot_options": {
                "color": "k"
              }
            }
          ]
        }
      ]
    }
  ]
}

Filtering Data

Filter Expressions

A filter expression is a Boolean Expression. A Boolean Expression can be any of the following:

A Boolean Expression can also be the result of a comparison:

A Numerical Expression can be any of the following:

An Identifier should match the regular expression ([Pp]@)?:?[0-9a-zA-Z_"."]+. That is, it should be some combination of digits, letters, _, and ., optionally preceded by P@/p@ and/or :.

A Number may be in decimal or scientific notation, with a + or - for sign. Valid examples:

Standard order of operations is followed:

  1. Parentheses
  2. Exponent
  3. Multiplication and Division
  4. Addition and Subtraction
  5. Comparison (==, !=, >, <, >=, <=)
  6. NOT
  7. AND
  8. XOR
  9. OR

Future Enhancements

Some of these features might be supported in future updates, if there is demand:

Filters

Mining

Exporting

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

View and download generated reports (aka packages)

Reports that have already been generated can be downloaded using the packages tool.

You can download the report by clicking on the text in the label column.

You can filter the packages using the top search bar. For example, in the below image we've filtered the packages for the FLT_DAU_FPA profile.

You can filter by time range using the Select Time Range box on the left side. By default all packages are displayed.

Export process

The OCI housekeeping export process runs asynchronously on the OCI Run server. Requested data is extracted directly from the original time slice telemetry files using the same application from the realtime data mining process. In order to correctly interpret state across time slice boundaries the process attempts to load the time slice prior to the slice containing the start of the exported data, if one is available, to establish the current value table and filter state files accurately for the data to be exported.

Reprocessing Data

Exporting Data

  1. From the top menu: Tools -> OCI Housekeeping Export
  2. In the top left corner, change to the "OCI Flight Model"

The last used Model is saved between sessions and tools

  1. Select your time range:

The time input uses your machine's timezone (which is likely eastern time for most users). However, the exported data and plots all use UTC.

Instead of manually inputting a "From" and "To" time, you can also select a marker's time range. Click on the "down arrow" to expand the "Search Markers" panel. You can then click on the label to use the time range. To refresh the marker list for new markers, click the "Now" button, which will adjust the search "To" time to the current time.

  1. Filter by the profile you want to export, for example: FLT_DAU_FPA.

  1. Click on the profile name to select the profile

  2. Click the Export button to start the export process

  1. You can track the status of the export by clicking on the "Notifcations" button in the top right corner. This will open up a side bar that shows your export tasks.

  1. When the export is finished, you can click on the filename to download it to your computer.

OCI HK Merge Utility

Usage:

java -jar oci_hk_merge.jar
  "<path to legacy export>"
  "<path to fm db.txt>"
  "<path to dau db.txt>"
  "<output file path base>"
  ["<path to force-active db.txt>"]
  
java -jar xina_import.jar -d output_dir/

If a force-active db file is provided, all fields which are active in that file will be active in the final merged output.

Note that "<output file path base>" is the base name for output files (so C:/out would generate C:/out.tsv, C:/out.json, etc).

Add users to daily reports

These instructions describe how to enable daily reports and add new users. Users will receive a daily email containing links to download the reports they are subscribed to.

  1. Open a tab to https://oci.xina.io/users. You will use this page to find users' NASA AUIDs, which is what we use to identify and email a user.
  2. Open a new tab to https://oci.xina.io/tool/oci-hk-export. In the "Profiles" section, find the profile you want to configure and click the expand button to immediately modify a profile. Make sure to click "Save Changes" after editing each field.
  3. Under "Fields", set "daily" to "True". This enables automated daily reports for this profile.
  4. Under "Fields", add the "ops_pace" model to the "model" field (if it doesn't already exist). This ensures the automated report is only created for this model instead of all of them.
  5. Under "Fields", add new users to the "users" field. This is where you will need to use the tab from step 1 to find the user's NASA AUID. Navigate to that tab. Find a user by searching for their name under the "Users" section. Select them. The "User Info" section will display their NASA AUID in parentheses. Use this value when adding new users.
  6. To enable daily trend reports, follow similar steps on this page https://oci.xina.io/tool/oci-hk-trend-export but do it for the "Trend Profiles" section. For the "models" field, you will need to input a JSON array where each entry is a model. For Example:
[
  "ops_pace"
]

Configure Export Plots

  1. Find the profile you want to configure and click the expand button to pop up the profile's configuration

  1. Under the "Fields" section, find and click on "plot". This will pop up the plot configuration.

  1. If no plot configuration exists, you can click "Add Default Pages" which will put each mnemonic on its own page and plot. It may take a moment to auto generate a default configuration.

  2. Configure as needed. At the moment, configuration is fairly limited.

  1. Scroll to the bottom and click "Save Changes".

  2. Exit the modal by clicking outside of it or hitting Esc.

  3. Reselect the profile to make sure your recent changes are loaded.

Configure Trend Reports

  1. Navigate to the Trend Export Tool: https://oci.xina.io/tool/oci-hk-trend-export
  2. If you want to edit an existing Trend Report, click on the profile under the "Trend Profiles" section which will populate the "New Trend" section. Otherwise, you can start modifying the fields under the "New Trend" section.
  3. Click on a Profile under the "Profiles" section to add the profile to the Trend Profile.
  4. The Bin Size selection chooses which binned data is used and the Bin Count is the multiplier. The trended data points are (Bin Size * Bin Count). For example, a Bin Size of 10 and a Bin Count of 10 will produce a trend where each data point is 100 minutes.
  5. If "Disable Filters" is checked, it will disable any filters that are defined on the Profile.
  6. If "Enable Time Conditions" is checked, it will enable trending by time ranges. The time ranges are defined as an array of JSON objects:
[
  {
    "start": "2024-04-09T18:00:00Z",
    "end": "2030-01-01T00:00:00Z"
  }
]
  1. If "Enable Interval Conditions" is checked, it will enable trending by intervals/markers.
  2. By default, the Profile's plot configuration will be used when generating the Trend Report. You can override this by selecting "Enable Custom Plot Configuration" and providing your own JSON Plot Configuration.
  3. Click "Save Trend Profile" to save your changes. This will create a new Trend Profile if none already exists with the name, otherwise it will overwrite the existing one.
  4. Click "Export Current Configuration" to export the Trend Profile. You can also export the Trend Profile without saving.