1 of 12

ADAPTIVE Overview (1 of 2)

Atmospheric Data And mission Planning Tool in an Interactive Visualization Environment

Purpose: Create a user-friendly, interactive application driven by a data flow, node-based software architecture to tackle the organization, utilization, and visualization of the science payloads’ data

The Team!

Rebecca Bishop: PI

Tad Gielow: Lead Developer

(former Disney/Sony Computer Animator)

Highlighted ADAPTIVE Features for GDC Mission

Expandability: Following created documentation, any member of the GDC team may create a specific node associated with their data.

Flexibility of data type ingestion and output: while an initial set of common input and output file format nodes will be identified and created, future format nodes can be added as needed.

Portability: ADAPTIVE will be converted to a container form so that it can be used on a variety of platforms from a hosted server to a users’ local machine.

Accessibility: Tool will be designed for use by the science community as well as the public. It will consist of a standard GUI interface with buttons and fields, a touch screen interface option (currently developed), and a node connection programming environment.

1

2 of 12

ADAPTIVE Overview (2 of 2)

ADAPTIVE is a visualization tool that will:

    • Enable mission visualization to support requirements development/verification, ConOps planning, Calibration/Validation planning
    • Produce public-ready images and movies of various aspects of the GDC mission and science data sets,
    • Provide a quick-look at the data over the entire constellation at any given time or location,
    • Extract subsets of the mission observational data and other supplemental data source for further analysis and study

Priority Capabilities:

    • Read a variety of data formats (GDC instruments, ground sensors, model output)
    • Produce 2-D and 3-D animated data maps
    • Extract user-selected data to files for further analysis
    • Provide publicly engaging visuals of mission data

Availability:

    • Hosted on Aerospace github account during Phase A-D with an open-source license
    • At Phase D, will be submitted/hosted by NASA Open-Source Software (OSS) (NASA github)

Example of a GUI using current capability (prior to IDS initiation)

2

3 of 12

ADAPTIVE Architecture

Written in C++ with Python bindings

  • Laboratory to Explore, Analyze, Visualize, Experiment and Simulate (LEAVES)
    • Foundational library for ADAPTIVE
  • GDC Incoming Data Overlay Mapping (GIDOM)
    • Focusses on GDC payload data
  • Visualization of Ionospheric Structures using Tomographic Analysis (VISTA)
    • Produce 3-D tomographic ionosphere images from ground and space GNSS data
  • Other Science Data Overlay Mapping (OSDOM)
    • Expandable node groupings (e.g. ISR, FPI, citizen science projects, etc.

ADAPTIVE Application

LEAVES

GIDOM

OSDOM (1)

OSDOM (2)

OSDOM (…)

OSDOM (3)

VISTA

Binding Code

Binding Code

Binding Code

Binding Code

Binding Code

Binding Code

3

4 of 12

Data Management Plan

  • The Aerospace Corporation has a dedicated github account (github.aero) that will be the primary distribution point of ADAPTIVE
    • Open-source permissive license
    • internal github server will be utilized for day-to-day development with complete updates for public use uploaded to the github.aero account at least quarterly but a higher cadence is expected during specific planning phases of the mission.
  • Initial release of ADAPTIVE will include currently created LEAVES nodes
  • The software will utilize a container architecture that will enable it to be run on Windows, Mac, and LINUX systems
  • Prior to the end of Phase D, we will work with the NASA GDC project manager/scientist in order to sponsor the submission of the final version of ADAPTIVE created under this project to the NASA Open-Source Software (OSS)
    • NASA OSS provides public software access through a NASA github account

4

5 of 12

Backup

5

[Low Sensitivity /Approved for selected release by Program/Project Manager]

[Low Sensitivity /Approved for selected release by Program/Project Manager]

6 of 12

LEAVES Node Group Overview

Input Data Interface

Filters & Operations

Output Data Interface

GeoJSON

KML

KMZ

TLE

Network Data Servers

Total Nodes Completed: 70

RINEX*

NetCDF*

Watch Area

Satellite Filter

ffmpeg

csv

png

NetCDF*

svg

Mapview

Antenna Filter

Error Estimate

Total Nodes Completed: 16

Total Nodes Completed: 7

LEAVES Nodal Structure

FFT*

STK

csv*

traffic

bline

timemd

D3

RINEX*

HDF5*

HDF5*

6

7 of 12

ADAPTIVE Tasks

Task

Description

ADAPTIVE

2-D Bindings

Code to integrate the WAVES library into ADAPTIVE GUI to produce 2-D images

2-D Touchscreen GUI Control

Code to integrate WAVES 2-D touchscreen capabilities into overall application

3-D Bindings

Code to integrate the WAVES library into ADAPTIVE Application to produce 3-D images

3-D Touchscreen GUI Control

Code to integrate WAVES 3-D touchscreen capabilities into overall application

GUI Stylization

Development of ADAPTIVE GUI

VISTA Bindings Code

Additional specialized code to utilize both the VISTA and WAVES library to produce images and extract data from GUI

GDC  Bindings Code

Additional specialized code to utilize both the VISTA and WAVES library to produce images and extract data from GUI

Extended User Testing

While internal testing will occur at all stages, this particular period will test the near final version of the GUI with both independent internal and IDS users. Activities include modifications and corrections that may be required.

Containerization

Perform containerization of ADAPTIVE. Engage with NASA GDC program manager to submit containerized version to OSS.

7

8 of 12

LEAVES Tasks

Task

Description

LEAVES

Baseline Functionality

This includes additional input data formats and data sources.

2-D Mission Visualization

Development of nodes and widgets required to display animated 2-D satellite orbits, ground tracks, day/night terminator, additional touch screen movements, etc.

3-D Mission Visualization

Development of nodes and widgets required to display animated 3-D satellite orbits, ground tracks, day/night terminator, additional touch screen movements, etc.

Sparse Data & Image Overlay

Determine optimal data storage and access to produce images in terms of performance vs. memory usage (i.e., layered images vs. voxel space). Develop related nodes to translate incoming data formats into formats/arrays required to create images and overlay data.

Misc. Nodes

Additional nodes or capabilities determined by the science team and within scope of ADAPTIVE resources.

2-D Science Visualization

Additional development of nodes unique to the expected type of science data from GDC, models, and tomographic ionosphere data.

3-D Science Visualization

Additional development of nodes unique to the expected type of science data from GDC, models, and tomographic ionosphere data.

Extended User Testing

While internal testing will occur at all stages, this particular period will test the near final version of all WAVES capabilities integrated into the GUI with both independent internal and IDS users. Activities include modifications and corrections that may be required.

8

9 of 12

GIDOM Tasks

* Requires early definition and input

Task

Description

GIDOM

Sensor Data Ingestion*

Develop specific input data format nodes as agreed upon by science and instrument team. Develop and required nodes to translate incoming format to common format for WAVES library.

GDC Specific Nodes*

Includes development of general nodes required to complete the proposed visualization of processed GDC payload data, and technical support to integrate any instrument/science team nodes into the baseline ADAPTIVE.

Sensor Data Extraction

Develop nodes to extract subset of GDC science data as a function of GDC payload(s), number of satellites, time/latitude/longitude. Modify GUI as needed

End-to-End Testing

While internal testing will occur at all stages, this particular period will test the near final version of all VISTA capabilities integrated into the GUI with both independent internal and IDS users. Activities include modifications and corrections that may be required. Will utilize simulated payload data as available.

9

10 of 12

VISTA Node Group Overview

Purpose: Provide a background ionosphere image that can be used during the mission refinement and post launch to overlay science observations to aid in IDS investigations.

  • Produced by a combination of ground and space-based TEC observations.
  • Utilize tomographic inversion technique to provide 3-D structure
    • An EOF-based algorithm previously developed by Endawoke will be utilized.

Comparison of the ionospheric EOF tomographic output from ground-based GPS receivers to IRI model output (Courtesy of Dr. Yizengaw, private conversation).

Example of conjugate structures in the global ionosphere from global GPS dTEC maps (Adapted from Figure 3 of Zhang et al., 2021)

10

11 of 12

VISTA Tasks

Task

Description

VISTA

Tomographic Implementation

Conversion of python EOF based tomographic algorithm into compatible node or development of a general python conversion node. Development of data handling nodes to produce images, change tomographic resolution.

Ground-based Data Ingestion

Develop nodes to pull data from the openMadrigal data site and transition to an internal format for use with the WAVES library and GUI.

Ionosphere Visualization

Any specialized nodes required for 2-D and 3-D visualization such as converting between 2-D and 3-D without regeneration.

Space-based Data Ingestion

Develop nodes to pull data from the UCAR COSMIC-2 data site and transition to an internal format for use with the WAVES library and GUI.

Data Extraction

Develop nodes to extract subset of tomographic data including metadata indicating datasets used and tomographic algorithm version. Integrate into GUI capability

End-to-End Testing

While internal testing will occur at all stages, this particular period will test the near final version of all VISTA capabilities integrated into the GUI with both independent internal and IDS users. Activities include modifications and corrections that may be required.

11

12 of 12

Examples

12