GroundTrackPlot

Lead: Rizwan Qureshi

Developer: Linda O. Jun

Tester: John M. Bez

 

Left to do are:

Explore

Known Bugs

Failing Tests

Other Findings

Requirements

Interface/Functional Spec

Overview

Description

Fields

GUI

Remarks

Examples

Test Procedures

Assumptions

File Naming Conventions

Nominal Tests

Edge/Corner/Miscellaneous Tests

Unique Validation Tests

 

Explore

 

Known Bugs

 

JIRA Bugs:

 

I did a bug search in JIRA by selecting GroundTrackPlot (FRR-42) under components and found following P1 and P2 open bugs/issues for FRR-42 GroundTrackPlot feature:

 

      GMT-418 GroundTrackPlot has 3 minor Ground Station issues and 1 Orbit Track issue.

      GMT-2954 Planet Mercury's half of topographic image is missing both from GroundTrackPlot and DefaultOrbitView

 

Failing Tests

Tests failing in the nightly regression reports related to this feature.

 

GroundTrackPlot_RetrogradeMotion (script)          Now passing after GMT-2989 fixed.

 

GroundTrackPlot_Set_SolverIterations (script)      Now passing after GMT-2989 fixed.

 

 

Other Findings

 

Following issues were found during exploratory testing:

 

Issue 1:   When using planet Mercury in GroundTrackPlot, then I found that half of topographic image for Mercury is missing.

 

Recommendation: Fix (Fix by: R2013a,  Priority: It is P1.

Created a bug GMT-2954  and temporarily assigned it to SPH.

 

Issue 2:   When running GroundTrackPlot_RetrogradeMotion, and GroundTrack_Set_SolverIterations scripts, GMAT crashes suddenly. using planet Mercury in GroundTrackPlot, then I found that half of topographic image for Mercury is missing.

 

Recommendation: Fix (Fix by: R2013a,  Priority: It is P1.

Created a bug GMT-2989. Assigned this bug to Darrel after input from Darrel.

 

Status: Resolved, verified and closed.

Requirements

 

These were finalized by CCB as of 16 Aug 2012 and are here for reference purposes only.  See the SRS for requirements. -SPH

 

 

FRR-42.1.0

The system shall allow the user to choose among the following objects as the central body of a ground track plot:

FRR-42.1.1

1)                Default Celestial Body

FRR-42.1.2

2)               User-defined Body

FRR-42.2

The Ground Track Plot shall draw the longitude and latitude time-history for Spacecraft object.

FRR-42.3.0

The system shall display icons on the ground track to indicate the locations of the following object types:

FRR-42.3.1

1)        Spacecraft

FRR-42.3.2

2)        Groundstation

FRR-42.4.0

The system shall display object labels next to the icons for the following object types:

FRR-42.4.1

1)         Spacecraft

FRR-42.4.2

2)         Groundstation

FRR-42.5.0

The system shall allow the user to define the data plotting options for  a ground track plot:

FRR-42.5.1

1)  The number of integration steps to skip between plot points

FRR-42.5.2

2)  The number of plot points to collect before updating a ground track         plot

FRR-42.5.3

3) The number of plot points to retain and redraw during propagation and animation.

FRR-42.6.0

The system shall allow the user to specify how data is drawn to Ground Track Plots during iterative processes such as differential correction and optimization. The following options shall be available:

FRR-42.6.1

1) Plot all iterations/perturbations

FRR-42.6.2

2) Plot current iteration/perturbation only

FRR-42.6.3

3) Plot solution only

FRR-42.7.0

The system shall allow the user to specify a texture map using the following options

FRR-42.7.1

1) Use default texture map for central body

FRR-42.7.2

2) Use user-defined texture map

FRR-42.8

The system shall optionally display or not display a configured ground track plot

FRR-42.9

The Ground Track Plot shall display the epoch in UTC Gregorian format

FRR-42.10

The system shall allow the user to animate the Ground Track Plot after a run is complete

FRR-42.11

The system shall display latitude and longitude of the cursor position when the cursor is placed over a Ground Track Plot

FRR-42.12

The system shall support the following image file formats:

FRR-42.12.1

JPEG

FRR-42.13

The system shall display longitude/latitude grid line on a Ground Track Plot.

FRR-42.14

The system shall display longitude/latitude grid line values (in degrees) on a Ground Track Plot.

 

 

Interface/Functional Spec

Overview

 

GroundTrackPlot is a user-defined resource that draws longitude and latitude time-history of a spacecraft

 

 

 

 

 

Description

 

The GroundTrackPlot resource allows you to draw spacecraft’s longitude and latitude time-history onto the texture map of a user-selected central body. GMAT allows you to draw ground track plots of any number of spacecraft onto a single texture map. You can also create multiple GroundTrackPlots by using either the GUI or script interface of GMAT. GMAT also provides the option of when to plot and stop plotting ground track to a GroundTrackPlot through the Toggle On/Off command. See the Remarks section below for detailed discussion of the interaction between GroundTrackPlot object and the Toggle command. GroundTrackPlot resource also allows you to display any number of user-defined ground stations onto the texture map of the central body.

 

See Also : Toggle command, GroundStation resource

 

 

Fields

 

See the User Interface Spec spreadsheet for reference information for fields. 

 

GUI

 

The figure below shows the default settings for the GroundTrackPlot resource:

 

                    

  Figure: Default Name and Settings for the GroundTrackPlot Object Dialog Box

 

 

Remarks

 

Behavior when using GroundTrackPlot Resource & Toggle Command

 

The GroundTrackPlot resource draws the longitude and latitude time-history of a spacecraft at each propagation step of the entire mission duration. If you want to report data to a GroundTrackPlot at specific points in your mission, then a Toggle On/Off command can be inserted into the mission sequence to control when the GroundTrackPlot is to draw data. When Toggle Off command is issued for a GroundTrackPlot, no ground track data is drawn until a Toggle On command is issued. Similarly when a Toggle On command is used, ground track data is drawn at each integration step until a Toggle Off command is used.

 

Below is an example script snippet that shows how to use Toggle Off and Toggle On command while using the GroundTrackPlot resource. GroundTrackPlot is turned off for the first 2 days of the propagation:

Create Spacecraft aSat;

Create Propagator aProp;

 

Create GroundTrackPlot aGroundTrackPlot;

GMAT aGroundTrackPlot.Add = {aSat};

 

BeginMissionSequence;

 

Toggle aGroundTrackPlot Off;

Propagate aProp(aSat) {aSat.ElapsedDays = 2};

Toggle aGroundTrackPlot On;

Propagate aProp(aSat) {aSat.ElapsedDays = 4};

 

 

 

 

Behavior when plotting data in Iterative Processes

 

GMAT allows you to specify how data is plotted onto a plot during iterative processes such as differential correction or optimization. The SolverIterations field of GroundTrackPlot resource supports 3 options which are described in the table below:

SolverIterations options

Description

Current

Shows only current iteration/perturbation in an iterative process and draws current iteration to a GroundTrackPlot

All

Shows all iterations/perturbations in an iterative process and draws all iterations/perturbations to a GroundTrackPlot

None

Shows only the final solution after the end of an iterative process and draws only final solution to GroundTrackPlot

Behavior when plotting longitude and latitude time-history of a Spacecraft

 

GMAT’s GroundTrackPlot resource allows you to draw longitude and latitude time-history of a spacecraft. You can choose to draw ground track plot of multiple spacecrafts onto a single texture map of a central body.

 

Caution:  The longitude and latitude of a spacecraft is drawn as an approximation that includes straight line segments and longitude/latitude data does not takes into account central body shape or its oblateness.

 

 

 

 

Examples

 

This example shows how to use GroundTrackPlot resource. A single spacecraft and a Ground Station is added to the GroundTrackPlot. Spacecraft’s ground track is plotted for one day of propagation:

Create Spacecraft aSat;

Create Propagator aProp;

 

Create GroundStation aGroundStation;

 

Create GroundTrackPlot aGroundTrackPlot;

GMAT aGroundTrackPlot.Add = {aSat, aGroundStation};

 

BeginMissionSequence;

 

Propagate aProp(aSat) {aSat.ElapsedDays = 1};

 

 

 

 

Propagate a spacecraft for two days around a non-default central body. Spacecraft’s ground track is plotted on planet Mars

Create Spacecraft aSat;

GMAT aSat.CoordinateSystem = MarsJ2000Eq;

GMAT aSat.SMA = 8000;

GMAT aSat.ECC = 0.0003;

 

Create ForceModel aFM;

GMAT aFM.CentralBody = Mars;

GMAT aFM.PointMasses = {Mars};

 

Create Propagator aProp;

GMAT aProp.FM = aFM

 

Create CoordinateSystem MarsJ2000Eq;

GMAT MarsJ2000Eq.Origin = Mars;

GMAT MarsJ2000Eq.Axes = MJ2000Eq;

 

Create GroundTrackPlot aGroundTrackPlot;

GMAT aGroundTrackPlot.Add = {aSat};

GMAT aGroundTrackPlot.CentralBody = Mars;

 

BeginMissionSequence;

 

Propagate aProp(aSat) {aSat.ElapsedDays = 2};

 

 

 

 

 

 

 

Test Procedures

Assumptions

 

      All tests use non-default values

 

File Naming Conventions

The goal of the naming convention is to allow people to intuitively understand the purpose of the test by the name of the test file. The file naming conventions in this section are guidelines to be used when they “make sense” and are to be modified when they don’t “make sense”. They’re not strict rules.

GroundTrackPlot uses the following format for nominal tests:

GroundTrackPlot_ <description of test>

Use the following format for validation tests:

GroundTrackPlot_Validation_<Field>_ <description of test>

 

Nominal Tests

Priority

Status

Summary

P1

Done

RHQ

Test whether the system allows the user to choose objects like Default Celestial Body and user-defined Body  as the central body of a ground track plot

P1

Done

RHQ

Test whether the Ground Track Plot allows the drawing of the longitude and latitude time-history for objects like Spacecraft and GroundStation

P1

Done

RHQ

Test whether the system allows displaying of icons on the ground track to indicate locations of objects like Spacecraft and GroundStation

P1

Done

RHQ

Test whether the system displays object labels next to the icons for objects like Spacecraft and GroundStation

P1

Done

RHQ

Test whether the system allows the user to define the data plotting options like setting of the number of integration steps to skip between plot points

P1

Done

RHQ

Test whether the system allows the user to define the data plotting options like setting of the number of plot points to collect before updating a ground track plot

 

PI

Done

RHQ

Test whether the system allows the user to define the data plotting options like setting of the number of plot points to retain and redraw during propagation and animation

P1

Done

RHQ

Test whether the system allows the user to specify how data is written to GroundTrackPlot during iterative process such as Differential Correction. Testing includes employing all available options for SolverIterations.

P1

Done

RHQ

Test whether the system allows the user to specify how data is written to GroundTrackPlot during iterative process such as optimization. Testing includes employing all available options for SolverIterations.

P1

Done

RHQ

Test whether the system allows the user to specify a texture map using the default texture map for central body

P1

Done

RHQ

Test whether the system allows the user to specify a texture map using a user-defined texture map.

P1

Done

RHQ

Test whether the system allows to optionally display or not display a configured ground track plot

P1

Done

RHQ

Test whether the Ground Track Plot displays the epoch in UTC Gregorian format

P1

Done

RHQ

Test whether the system allows the user to animate the Ground Track Plot after a run is complete

P1

Done

RHQ

Test whether the system displays the latitude and longitude values when the cursor is placed over a GroundTrackPlot.

 

 

 

Edge/Corner/Miscellaneous Tests

 

I cannot think of any as of yet.

Priority

Status

Summary

 

 

 

 

 

 

 

 

 

 

 

 

Unique Validation Tests

These are unique validation tests that are required for special field or object couplings for this GroundTrackPlot feature.

Priority

Status

Summary

P1

SPH

Done

Test range constraints on SolverIterations field

P1

SPH

Done

Test range constraints on DataCollectFrequency field

P1

SPH

Done

Test range constraints on Add field

 

P1

SPH

Done

Test range constraints on CentralBody field

 

 

 

 

Unique Mode Tests

 

I cannot think of any unique mode tests for this object.

Priority

Status

Summary

 

 

 

 

 

 

 

 

 

 

 

precious

 

Unique GUI Tests

 

These are tests that are unique to the GUI interface for this feature that are not covered by the standard GUI test template and procedures.

Priority

Status

Summary