Explore
Known Bugs
JIRA ID  Summary  Recommendation 
GMT585  Multiple redundant properties/fields for epoch  P3 
GMT1098  Tab key navigation fails  Appears fixed 
GMT1346  Add ability for userdefined parameters  Improvement 
GMT1439  Parameter design for multiple dependency  Improvement 
GMT1483  Ability to Calculate and Output Sun Vector to any point  Improvement 
GMT1899  Beta Angle is Off by about .003 degrees  P1 
GMT1933  Earth Fixed RA changed from 0360 to 180180 measurement  P1 (document) 
GMT2011  Larger angular momentum errors in 09/15 build  P1, assign to Joel 
GMT2318  STM Parameters are wrong when using Coordinate System other than EarthMJ2000Eq  P1, assign to Joel 
GMT2475  Provide a parameter to check convergence status of a VF13 optimizer  Improvement 
GMT2673  User Reported: Parameter Select Dialog Box Silently Changes User's Selected Object  Needs verification 
GMT2755  ParameterCreateDialog does not close properly after adding string parameter on Mac  P2 
Failing Tests
Failing tests listed as of 10/15/2012.
JIRA ID  Test  Summary  Rec. 
TBD  CbParams_Hyperbolic_2Body  Incorrect MA , OrbitPeriod  Investigate 
TBD  CSParams_Uranus1_2Body_UranusFixed  Numeric issues  Investigate 
TBD  CSParams_Saturn1_2Body_SaturnFixed  Numeric issues  Investigate 
TBD  CSParams_Pluto1_2Body_PlutoFixed  Test issues, plus numerics  Investigate 
TBD  CSParams_Neptune1_2Body_NeptuneMJ2000Ec  Test issues, plus many incorrect parameters  Investigate 
TBD  CSParams_Neptune1_2Body_NeptuneFixed  Numeric issues  Investigate 
TBD  CSParams_Hyperbolic_2Body  Numeric issues  Investigate 
TBD  CSParams_GEO_2Body  Numeric issues  Investigate 
Other Findings
JIRA ID  Summary  Rec. 
GMT3164  Inconsistent naming: RadApo/RadPer and VelApoapsis/RadPeriapsis  P3 
GMT3165  ParameterSelectDialog is badly named  P2 
GMT3166  ParameterSelectDialog string consistency issues  P3 
GMT3167  ParameterSelectDialog doesn't remove item from available list once chosen  P2 
GMT3173  Clarification needed on HA output range  P1 
GMT3205  ParameterSelectDialog shouldn't use list box for singleparameter selection  P3 
Requirements
To reviewers: I'm considering removing "or set" and the "(read only)/(read/write)" bits from the requirements. All of the "write" parameters should already be described on the requirement for the parent resource.
ID  Requirements 
FRR38.1.0  The system shall allow the user to request or set the following object properties with respect to any celestial body in FRR16: 
FRR38.1.1.0  1) Spacecraft and orbit parameters 
FRR38.1.1.1  1. Altitude (read only) 
FRR38.1.1.2  2. Beta angle (read only) 
FRR38.1.1.3  3. C3 energy (read only) 
FRR38.1.1.4  4. Eccentric anomaly (read/write) 
FRR38.1.1.5  5. Eccentricity (read/write) 
FRR38.1.1.6  6. Orbit energy (read only) 
FRR38.1.1.7  7. Magnitude of angular momentum (read only) 
FRR38.1.1.8  8. Planetodetic latitude (read only) 
FRR38.1.1.8  9. Longitude (read only) 
FRR38.1.1.10  10. Local sidereal time (read only) 
FRR38.1.1.11  11. Mean anomaly (read/write) 
FRR38.1.1.12  12. Mean hour angle (read only) 
FRR38.1.1.13  13. Mean motion (read only) 
FRR38.1.1.14  14. Orbit period (read only) 
FRR38.1.1.15  15. Radius of apoapsis (read/write) 
FRR38.1.1.16  16. Radius of periapsis (read/write) 
FRR38.1.1.17  17. Magnitude of position vector (read/write) 
FRR38.1.1.18  18. Semilatus rectum (read only) 
FRR38.1.1.19  19. Semimajor axis (read/write) 
FRR38.1.1.20  20. True anomaly (read/write) 
FRR38.1.1.21  21. Velocity at apoapsis (read only) 
FRR38.1.1.22  22. Velocity at periapsis (read only) 
FRR38.1.1.23  23. Hyperbolic anomaly (read/write) 
FRR38.1.1.24  24. Apoapsis crossing indicator (read only) 
FRR38.1.1.25  25. Periapsis crossing indicator (read only) 
FRR38.2.0  The system shall allow the user to request or set the following object properties with respect to any coordinate system in FRR35: 
FRR38.2.1.0  1) Spacecraft and orbit parameters 
FRR38.2.1.1  1. Argument of periapsis (read/write) 
FRR38.2.1.2  2. Azimuth (read/write) 
FRR38.2.1.3  3. B dot T (read only) 
FRR38.2.1.4  4. B dot R (read only) 
FRR38.2.1.5  5. B vector angle (read only) 
FRR38.2.1.6  6. B vector magnitude (read only) 
FRR38.2.1.7  7. Declination (read/write) 
FRR38.2.1.8  8. Declination of velocity (read/write) 
FRR38.2.1.9  9. Flight path angle (read/write) 
(delete)  
FRR38.2.1.11  11. Components of angular momentum (read only) 
FRR38.2.1.12  12. Inclination (read/write) 
FRR38.2.1.13  13. Orbit state transition matrix (read only) 
FRR38.2.1.14  14. 3x3 partitions of Orbit STM (read only) 
FRR38.2.1.15  15. Right ascension (read/write) 
FRR38.2.1.16  16. Right ascension of the ascending node (read/write) 
FRR38.2.1.17  17. Right ascension of velocity (read/write) 
FRR38.2.1.18  18. Magnitude of velocity (read/write) 
FRR38.2.1.19  19. Components of Cartesian velocity (read/write) 
FRR38.2.1.20  20. Components of Cartesian position (read/write) 
FRR38.2.1.21  21. Right ascension of outgoing hyperbolic asymptote (read only) 
FRR38.2.1.22  22. Declination of outgoing hyperbolic asymptote (read only) 
FRR38.2.1.23  23. Equinoctial elements (read/write) 
FRR38.2.1.24  24. Mean longitude (read/write) 
FRR38.3.0  The system shall allow the user to request or set the following object properties: 
FRR38.3.1.0  1) Spacecraft and orbit parameters 
FRR38.3.1.3  3. Components of angular velocity (read/write) 
FRR38.3.1.4  4. Drag coefficient (read/write) 
FRR38.3.1.5  5. Reflectivity coefficient (read/write) 
FRR38.3.1.6  6. Components of attitude direction cosine matrix (read/write) 
FRR38.3.1.7  7. Drag area (read/write) 
FRR38.3.1.8  8. Dry mass (read/write) 
FRR38.3.1.9  9. Elapsed days (read only) 
FRR38.3.1.10  10. Elapsed seconds (read only) 
(delete)  
(delete)  
FRR38.3.1.13  13. Components of attitude quaternion (read only) 
FRR38.3.1.14  14. SRP area (read/write) 
FRR38.3.1.15  15. Epoch in TAI modified Julian (read/write) 
FRR38.3.1.16  16. Epoch in TAI Gregorian (read/write) 
FRR38.3.1.19  19. Epoch in TDB modified Julian (read/write) 
FRR38.3.1.20  20. Epoch in TDB Gregorian (read/write) 
FRR38.3.1.21  21. Epoch in TT modified Julian (read/write) 
FRR38.3.1.22  22. Epoch in TT Gregorian (read/write) 
FRR38.3.1.23  23. Epoch in UTC modified Julian (read/write) 
FRR38.3.1.24  24. Epoch in UTC Gregorian (read/write) 
FRR38.3.1.25  25. Total mass (read only) 
FRR38.3.1.26  26. Modified Rodrigues parameters (read/write) 
FRR38.3.1.27  27. Euler angles (read/write) 
FRR38.3.1.28  28. Euler angle rates (read/write) 
FRR38.3.1.29  29. Epoch in A.1 modified Julian (read/write) 
FRR38.3.1.30  30. Epoch in A.1 Gregorian (read/write) 
FRR38.3.1.31  31. Attitude quaternion (read/write) 
FRR38.3.2.0  2) Impulsive burn parameters 
FRR38.3.2.1  1. Thrust vector element 1 (read/write) 
FRR38.3.2.2  2. Thrust vector element 2 (read/write) 
FRR38.3.2.3  3. Thrust vector element 3 (read/write) 
(delete)  
(delete)  
(delete)  
FRR38.3.3.0  3) Tank parameters 
FRR38.3.3.1  1. Pressure (read/write) 
FRR38.3.3.2  2. Volume (read/write) 
FRR38.3.3.3  3. Fuel density (read/write) 
FRR38.3.3.4  4. Fuel mass (read/write) 
FRR38.3.3.5  5. Temperature (read/write) 
FRR38.3.3.6  6. Reference temperature (read/write) 
FRR38.3.4.0  4) Thruster parameters 
FRR38.3.4.1  1. Duty cycle (read/write) 
FRR38.3.4.2  2. Thrust scale factor (read/write) 
FRR38.3.4.3  3. Gravitational acceleration for thrust equation (read/write) 
FRR38.3.4.4  4. Thrust coefficients (read/write) 
FRR38.3.4.5  5. Isp coefficients (read/write) 
FRR38.3.4.6  6. Components of thrust direction (read/write) 
Interface/Functional Spec
Overview
Data property available for use by commands
Description
Parameters are named resource properties that can be used to obtain data for use by Mission Sequence commands or by output resources. Some parameters, such as the Altitude parameter of Spacecraft, are calculated values that can only be used to retrieve data. They cannot be set directly. Others, such as the Element1 parameter of ImpulsiveBurn, share the same name as a resource field and can be used both to set data and retrieve it. Parameters are distinguished from resource fields by their extra functionality: fields are static resource properties that are usually set in initialization (or in the GUI Resources tree), while parameters can be calculated on the fly and used in plots, reports, and mathematical expressions.
Parameters are classified as one of four types: centralbodydependent parameters, coordinatesystemdependent parameters, attachedhardware parameters, and standalone parameters. Standalone parameters are the simplest type, in that they have no dependencies. The ElapsedSecs parameter of Spacecraft is an example of this; it is simply referenced as Spacecraft.ElapsedSecs
.
Centralbodydependent parameters, as the name suggests, have a value that is dependent on the chosen celestial body. The Altitude parameter of Spacecraft is an example of this. To reference this parameter, you must specify a central body, such as Spacecraft.Mars.Altitude
. Any builtin central body or userdefined Asteroid, Comet, Moon, or Planet is valid as a dependency. If the dependency is omitted, Earth is assumed.
Likewise, coordinatesystemdependent parameters have a value that is dependent on the chosen coordinate system. The DEC parameter of Spacecraft is an example of this. To reference this parameter, you must specify the name of a CoordinateSystem resource, such as Spacecraft.EarthFixed.DEC
. Any default or userdefined CoordinateSystem resource is valid as a dependency. If the dependency is omitted, EarthMJ2000Eq is assumed.
Attachedhardware parameters have no dependencies, but are themselves dependent on being attached to a Spacecraft. FuelTank and Thruster parameters are examples of this. The FuelMass parameter of FuelTank cannot be referenced without first attaching the FuelTank to a Spacecraft. Then, the parameter can be referenced as: Spacecraft.FuelTank.FuelMass
.
The individual parameters are resourcespecific, and are documented along with the their parent resources. The GUI, however, has a parameter selection interface that is common to all parameters. This interface is documented in GUI, below.
See Also: Script Language, FuelTank, ImpulsiveBurn, Spacecraft, Thruster
GUI
Parameters can be used as input in several places throughout GMAT, such as the ReportFile and XYPlot resources and the If/Else, Propagate, and Report commands. In the GUI, all of these use a common interface called the ParameterSelectDialog that allows for interactive parameter selection. A basic ParameterSelectDialog window looks like the following:
The ParameterSelectDialog window is used to build a parameter, along with any dependencies, for use in a command or resource. Some resources and commands have different requirements for the types of parameters that can be used, so the ParameterSelectDialog can take slightly different forms, depending on where it's used. This section will describe the generic interface, then mention any resource or commandspecific exceptions.
General Usage
The first step in choosing a parameter is to select the object (or resource) type from the Object Type list in the upper left. Five types can appear in this list: Spacecraft, ImpulsiveBurn, Variable, Array, and String.
Once you've selected a type, The Object List box is populated with all existing resources of that type. Use this list to choose the specific resource you'd like to reference.
If the Spacecraft type is selected, the Attached Hardware List appears below the Object List. This list displays any hardware (such as FuelTank resources) attached to the selected Spacecraft. If the Array type is selected, Row and Col boxes appear. Use these to specify a row and column to select an individual array element, or check Select Entire Object to choose the entire array.
Once a resource is selected, the Object Properties list is populated with all available parameters provided by that resource. Some resources, such as instances of Variable or Array, are themselves parameters, so this list remains empty.
Parameters with different dependency types are commingled in the Object Properties list. When you select one, the appropriate dependency (if any) appears below the list. For example, after selecting the Spacecraft AOP parameter, a Coordinate System list appears. After selecting the Spacecraft Apoapsis parameter, a Central Body list appears. And after selecting the Spacecraft Cd parameter, no dependency list appears. To select a range of parameters from the Object Properties list, hold down the Shift key while selecting the second endpoint of the range. To select multiple individual parameters, hold down the Ctrl key while making each selection.
To select a parameter, select the appropriate Object Type, the specific resource from the Object List or Attached Hardware List, the desired parameter from the Object Properties list, and the required dependency, and add it to the Selected Value(s) list on the right. There are six buttons available to control this list:
 UP: Move the selected item in the Selected Value(s) list up one position (if allowed).
 DN: Move the selected item in the Selected Value(s) list down one position (if allowed).
 >: Add the selected item in the Object Properties list to the Selected Value(s) list.
 <: Remove the selected item in the Selected Value(s) list.
 =>: Add all items to the Selected Value(s) list.
 <=: Remove all items from the Selected Value(s) list.
When finished, the Selected Value(s) list contains the final selected parameters. Click OK to accept the selection.
The ordering of the Selected Value(s) list is significant in certain circumstances (such as in the Add field of ReportFile), but not in others. See the documentation for each resource or command for details.
Special Considerations
Some resources and commands (such as the Propagate command Parameter argument) only accept a single parameter as input; in this context the ParameterSelectDialog only allows one parameter in the Selected Value(s) list and does not allow use of the UP, DN, and => buttons.
In some instances (such as in the Vary command), only parameters that are also fields (and so can be set in the Mission Sequence) can be used. In this case only the allowed parameters will be shown in the Object Properties list.
In the Propagate command Parameter argument, only parameters of Spacecraft can be used. In this case only Spacecraft will be shown in the Object Type list.
Parameters
To Reviewer: These tables will be merged into the parent reference pages and labeled as "Field" or "Parameter". For existing fields, the description already in the spec will be used instead of the description below. Each section below will be linked to the parent reference page.
To Technical Writer: The "pencil" icon in the following tables is from http://www.famfamfam.com/lab/icons/silk/. They're free to use, but we need to credit them.
User Interface Design Trades for New Parameter Types
This is a temporary design trade study for user interfaces to provide force model and space point parameters. This information will be migrated and formalized once designs are selected.
For each parameter there are ate lease four pieces of information that must be specified.
Force Model Parameters  Space Point Parameters 



Here are some design trades: So far, we have three high level approaches, which are identified in the left hand column. We need to identify Pros and Cons from an interface and implementation perspective to help us make a decision.
Design/Interface Description  Script Examples  Pros  Cons 

Object Methods. This approach is entirely new and uses methods on builtin objects to expose data and functionality.  density = myForceModel.GetDensity(Sat) density = mySat.GetDensity(ForceModel) myCoordinateSystem.GetRotationMatrix() 


Builtin math/GMAT functions. This approach provides more math function interfaces to get to lower level data  rho = GetForceModelData(myForce,mySat,'density'); density = GetDensity(myForceModel,mySpaceraft); GetPosition(myLibPoint,'EarthMJ200Eq',epoch) GetVelocity(myLibPoint,EarthFixed,Sat.A1ModJulian) myImpulsiveBurn.EarthFixed.Element1 


New Parameters. This approach extends the existing parameter approach  mySat.myForceModel.density myLibrationPoint.UTCModJulian = 21345 x = myLibrationPoint.EarthMJ2000Eq.X myLibPoint.mySat.EarthMJ2000Eq.X myLibrationPoint.EarthMJ2000Eq.Z(21451) myLibrationPoint.EarthMJ2000Eq.Z(A1ModJulian = 21423) myImplulsiveBurn.EarthMJ2000Eq.Element1 


Create Vector myVector
myVector.Type = Position
MyVector.Center = Earth
MyVector.Point = myLibrationPoint
Parameter Select Dialog Behavior for Different Contexts and Parameters
This section describes the different places the parameter select dialog box is used, and the parameter types that should appear in each context.
Summary of Supported Object Types in PSDB
The table below describes at a high level the objects that have parameters, whether those objects support get, set or both, and provides some simple examples.
Object Type  Get/Set  Description  Examples 

Spacecraft  Get and Set  Spacecraft hardware, orbit, and attitude related information.  MySat.Earth.SMA 
SpacePoint  Get and Set  Ephemeris for space point parameters (except spacecraft).
Epoch parameters are set, Position Parameters are Get.  Sun.EarthMJ2000Eq.X 
ImpulsiveBurn  Get and Set  ImpulsiveBurn related parameters
 MyDeltaV.EarthMJ2000Eq.Element1 
Variable  Get and Set  Variable data type  MyVar 
Array  Get and Set  Array data type  MyArray, MyArray(2,2) 
String  Get and Set  String data type  MyString 
Parameter Attribute Definitions
Attribute Name  Definitions 

Settable  The quantity can be set by the user. An example that is settable is MySat.X = 5; An example that is NOT settable is MySat.OrbitPeriod = 3600. 
Plottable  The quantity is a scalar, numeric value. Examples that are: MySat.X or MyArray(1,1). An example that is NOT Plottable is MySat.Epoch.UTCGregorian. 
Reportable  The quantity can be written to a report. For example, an entire Spacecraft can be selected in some contexts, but is not a reportable type. 
Parameter Select Dialog Behavior by Context
The parameter select dialog behavior is primarily governed by three questions:
 Which Resource types are supported by the Resource or Command context in which the PSDB is being used? Not all contexts support all Resource types. For example, the Vary command LHS does not support the String Resource.
 Is the context getting data or setting data? Many parameters are not settable and when the PSDB is used to select a quantity to set, the available options are fewer than when simply getting a quantity.
 What parameter attributes are supported by by the Resource or Command context in which the PSDB is being used? For example, the Achieve command does not support string parameters. The FiniteBurnCommand requires selecting an entire spacecraft.
In addition, some contexts do now allow dependencies, and some only allow selecting an entire Resource.
The table below describes the required behavior for all contexts where the PSDB is used.
Resource/Command  Reference  Get/Set  Special Limitations 
ReportFile
 Parameter list  Get 

XYPlot
 Selected X
 Get 

XYPlot
 Selected Y  Get 

Propagate
 Stopping condition LHS
 Get 

Propagate
 Stopping condition RHS  Get 

Vary  Variable  Set 

Achieve
 Goal
 Get 

Achieve
 Value
 Get 

Achieve
 Tolerance  Get 

Report  Parameter List  Get 

Call MATLAB Function  Input list  Get 

Call MATLAB Function  Output list  Set 

If  LHS  Get 

If  RHS  Get 

For  Index  Set 

For  Start  Get 

For
 Increment  Get 

For  End  Get 

While  LHS  Get 

While  RHS  Get 

NonlinearConstraint  Constraint  Get 

NonlinearConstraint  Constraint Value  Get 

Minimize  Variable to be minimized  Get 

BeginFiniteBurn
 Spacecraft  Get 

EndFiniteBurn
 Spacecraft  Get 

Parameter Specifications By Resource
Spacecraft
Parameter  Units  Description  
Acceleration  N  Y  km/s^2  The total acceleration with respect to the inertial system. Data Type: Real Number Dependency: ForceModel. 
AccelerationX  N  Y  km/s^2  The xcomponent of acceleration with respect to the inertial system. Data Type: Real Number Dependency: ForceModel. 
AccelerationY  N  Y  km/s^2  The ycomponent of acceleration with respect to the inertial system. Data Type: Real Number Dependency: ForceModel. 
AccelerationX  N  Y  km/s^2  The zcomponent of acceleration with respect to the inertial system. Data Type: Real Number Dependency: ForceModel. 
AtmosDensity  N  Y  kg/km^3  The atmospheric density at the current spacecraft epoch and location. Data Type: Real Number Dependency: ForceModel. 
ElapsedSecs  N  Y  s  Spacecraft Data Type: Real Number 
ElapsedDays  N  Y  d  Spacecraft Data Type: Real Number 
A1ModJulian  Y  Y  d  Spacecraft orbit epoch in the A.1 system and the Modified Julian format. Data Type: Real Number 
A1Gregorian  Y  N  N/A  Spacecraft orbit epoch in the A.1 system and the Gregorian format. Data Type: String 
TAIModJulian  Y  Y  d  Spacecraft orbit epoch in the TAI system and the Modified Julian format. Data Type: Real Number 
TAIGregorian  Y  N  N/A  The spacecraft orbit epoch in the TAI system and the Gregorian format. Data Type: String 
TTModJulian  Y  Y  d  The spacecraft orbit epoch in the TT system and the Modified Julian format. Data Type: Real Number 
TTGregorian  Y  N  N/A  Spacecraft orbit epoch in the TT system and the Gregorian format. Data Type: String 
TDBModJulian  Y  Y  d  Spacecraft orbit epoch in the TDB system and the Modified Julian format. Data Type: Real Number 
TDBGregorian  Y  N  N/A  Spacecraft orbit epoch in the TDB system and the Gregorian format. Data Type: String 
UTCModJulian  Y  Y  d  Spacecraft orbit epoch in the UTC system and the Modified Julian format. Data Type: Real Number 
UTCGregorian  Y  N  N/A  Spacecraft orbit epoch in the UTC system and the Gregorian format. Data Type: String 
CurrA1MJD  Y  Y  d  Deprecated. Spacecraft orbit epoch in the A.1 system and the Modified Julian format. Data Type: Real Number 
X  Y  Y  km  Cartesian xcomponent of the spacecraft position. Data Type: Real Number 
Y  Y  Y  km  Cartesian ycomponent of the spacecraft position. Data Type: Real Number 
Z  Y  Y  km  Cartesian zcomponent of the spacecraft position. Data Type: Real Number 
VX  Y  Y  km/s  Cartesian xcomponent of the spacecraft velocity. Data Type: Real Number 
VY  Y  Y  km/s  Cartesian ycomponent of the spacecraft velocity. Data Type: Real Number 
VZ  Y  Y  km/s  Cartesian zcomponent of the spacecraft velocity. Data Type: Real Number 
SMA  Y  Y  km  Orbit semimajor axis. Data Type: Real Number 
ECC  Y  Y  N/A  Orbit eccentricity. Data Type: Real Number 
INC  Y  Y  °  Orbit inclination. Data Type: Real Number 
RAAN  Y  Y  °  Orbit right ascension of the ascending node. Data Type: Real Number 
AOP  Y  Y  °  Orbit argument of periapsis. Data Type: Real Number 
TA  Y  Y  °  True anomaly. Data Type: Real Number 
MA  N  Y  °  Mean anomaly. Data Type: Real Number 
EA  N  Y  °  Eccentric anomaly. Data Type: Real Number 
HA  N  Y  °  Hyperbolic anomaly. Data Type: Real Number 
MM  N  Y  rad/s  Mean motion. Data Type: Real Number 
VelApoapsis  N  Y  km/s  Scalar velocity at apoapsis. Data Type: Real Number 
VelPeriapsis  N  Y  km/s  Scalar velocity at periapsis. Data Type: Real Number 
Apoapsis  N  Y  N/A  A parameter that equals zero when the spacecraft is at orbit apoapsis. This parameter can only be used as a stopping condition in the Propagate command. Data Type: Real Number 
Periapsis  N  Y  N/A  A parameter that equals zero when the spacecraft is at orbit periapsis. This parameter can only be used as a stopping condition in the Propagate command. Data Type: Real Number 
OrbitPeriod  N  Y  s  Osculating orbit period. Data Type: Real Number 
RadApo  Y  Y  km  Radius of apoapsis. Data Type: Real Number Dependency: Central Body 
RadPer  Y  Y  km  Radius of periapsis. Data Type: Real Number 
C3Energy  N  Y  MJ/kg (km^{2}/s^{2})  C_{3} (characteristic) energy. Data Type: Real Number 
Energy  N  Y  MJ/kg (km^{2}/s^{2})  Specific orbital energy. Data Type: Real Number 
RMAG  Y  Y  km  Magnitude of the orbital position vector. Data Type: Real Number 
RA  Y  Y  °  Right ascension of the orbital position. Data Type: Real Number 
DEC  Y  Y  °  Declination of the orbital position. Data Type: Real Number 
VMAG  Y  Y  km/s  Magnitude of the orbital velocity vector. Data Type: Real Number 
RAV  Y  Y  °  Right ascension of orbital velocity. Data Type: Real Number 
DECV  Y  Y  °  Declination of orbital velocity. Data Type: Real Number 
AZI  Y  Y  °  Orbital velocity azimuth. Data Type: Real Number 
FPA  Y  Y  °  Orbital flight path angle. Data Type: Real Number 
EquinoctialH  Y  Y  N/A  Equinoctial H element. Data Type: Real Number 
EquinoctialK  Y  Y  N/A  Equinoctial K element. Data Type: Real Number 
EquinoctialP  Y  Y  N/A  Equinoctial P element. Data Type: Real Number 
EquinoctialQ  Y  Y  N/A  Equinoctial Q element. Data Type: Real Number 
MLONG  Y  Y  °  Mean longitude. Data Type: Real Number 
SemilatusRectum  N  Y  km  Semilatus rectum of the osculating orbit. Data Type: Real Number 
HMAG  N  Y  km^{2}/s  Magnitude of the angular momentum vector. Data Type: Real Number 
HX  N  Y  km^{2}/s  X component of the angular momentum vector. Data Type: Real Number 
HY  N  Y  km^{2}/s  Y component of the angular momentum vector. Data Type: Real Number 
HZ  N  Y  km^{2}/s  Z component of the angular momentum vector. Data Type: Real Number 
DLA  N  Y  °  Declination of the outgoing hyperbolic asymptote. Data Type: Real Number 
RLA  N  Y  °  Right ascension of the outgoing hyperbolic asymptote. Data Type: Real Number 
Altitude  N  Y  km  Distance to the plane tangent to the surface of the specified celestial body at the subsatellite point. GMAT assumes the body is an ellipsoid. Data Type: Real Number 
MHA  N  Y  °  Angle between celestial body's bodyfixed and inertial axes. For Earth, this is the Greenwich Hour Angle. Data Type: Real Number 
Longitude  N  Y  °  Planetodetic longitude. Data Type: Real Number 
Latitude  N  Y  °  Planetodetic latitude. Data Type: Real Number 
LST  N  Y  °  Local sidereal time of the spacecraft from the celestial body's inertial xaxis. Data Type: Real Number 
BetaAngle  N  Y  °  Beta angle (or phase angle) between the orbit normal vector and the vector from the celestial body to the sun. Data Type: Real Number 
BdotT  N  Y  km  Bplane B·T magnitude. See the BdotR parameter for notes on this calculation. Data Type: Real Number 
BdotR  N  Y  km  Bplane B·R magnitude. GMAT computes the Bplane coordinates in the coordinate system specified in the dependency. In many implementations, the Bplane coordinates are computed in a pseudorotating coordinate system where the ω×r term is not applied when transforming velocity vectors. GMAT does apply the ω×r term in the velocity transformation. When computing Bplane coordinates in inertial systems, this term is identically zero. For rotating systems such as the SunEarth bodybody rotating system, the effect of including ω×r is small but noticeable when comparing results between systems. When the rotation of the selected coordinate system is "fast", the values may differ significantly. Data Type: Real Number 
BVectorMag  N  Y  km  Bplane B vector magnitude. See the BdotR parameter for notes on this calculation. Data Type: Real Number 
BVectorAngle  N  Y  °  Bplane angle between the B vector and the T unit vector. See the BdotR parameter for notes on this calculation. Data Type: Real Number 
DCM11  Y  Y  (None)  Element (1,1) of the attitude direction cosine matrix. Data Type: Real Number 
DCM12  Y  Y  (None)  Element (1,2) of the attitude direction cosine matrix. Data Type: Real Number 
DCM13  Y  Y  (None)  Element (1,3) of the attitude direction cosine matrix. Data Type: Real Number 
DCM21  Y  Y  (None)  Element (2,1) of the attitude direction cosine matrix. Data Type: Real Number 
DCM22  Y  Y  (None)  Element (2,2) of the attitude direction cosine matrix. Data Type: Real Number 
DCM23  Y  Y  (None)  Element (2,3) of the attitude direction cosine matrix. Data Type: Real Number 
DCM31  Y  Y  (None)  Element (3,1) of the attitude direction cosine matrix. Data Type: Real Number 
DCM32  Y  Y  (None)  Element (3,2) of the attitude direction cosine matrix. Data Type: Real Number 
DCM33  Y  Y  (None)  Element (3,3) of the attitude direction cosine matrix. Data Type: Real Number 
EulerAngle1  Y  Y  °  Attitude Euler angle 1. Data Type: Real Number 
EulerAngle2  Y  Y  °  Attitude Euler angle 2. Data Type: Real Number 
EulerAngle3  Y  Y  °  Attitude Euler angle 3. Data Type: Real Number 
MRP1  Y  Y  (None)  Attitude modified Rodrigues parameter 1. Data Type: Real Number 
MRP2  Y  Y  (None)  Attitude modified Rodrigues parameter 2. Data Type: Real Number 
MRP3  Y  Y  (None)  Attitude modified Rodrigues parameter 3. Data Type: Real Number 
Q1  N  Y  (None)  Attitude quaternion element 1 (a). Data Type: Real Number 
Q2  N  Y  (None)  Attitude quaternion element 2 (b). Data Type: Real Number 
Q3  N  Y  (None)  Attitude quaternion element 3 (c). Data Type: Real Number 
Q4  N  Y  (None)  Attitude quaternion element 4 (d). Data Type: Real Number 
Quaternion  Y  N  (None)  Attitude quaternion. Data Type: Array (1×4) 
AngularVelocityX  Y  Y  °/s  X component of the attitude angular velocity vector. Data Type: Real Number 
AngularVelocityY  Y  Y  °/s  Y component of the attitude angular velocity vector. Data Type: Real Number 
AngularVelocityZ  Y  Y  °/s  Z component of the attitude angular velocity vector. Data Type: Real Number 
EulerAngleRate1  Y  Y  °/s  Rate of attitude Euler angle 1. Data Type: Real Number 
EulerAngleRate2  Y  Y  °/s  Rate of attitude Euler angle 2. Data Type: Real Number 
EulerAngleRate3  Y  Y  °/s  Rate of attitude Euler angle 3. Data Type: Real Number 
DryMass  Y  Y  kg  Dry mass (without propellant). Data Type: Real Number 
Cd  Y  Y  (None)  Coefficient of drag. Data Type: Real Number 
Cr  Y  Y  (None)  Coefficient of reflectivity. Data Type: Real Number 
DragArea  Y  Y  m^{2}  Area used to compute acceleration due to atmospheric drag. Data Type: Real Number 
SRPArea  Y  Y  m^{2}  Area used to compute acceleration due to solar radiation pressure. Data Type: Real Number 
TotalMass  N  Y  kg  Total mass, including fuel mass from attached Fuel Tank resources. Data Type: Real Number 
OrbitSTM  N  N  (None)  State transition matrix. Data Type: Array (6×6) 
OrbitSTMA  N  N  (None)  Upperleft quadrant of the state transition matrix. Data Type: Array (3×3) 
OrbitSTMB  N  N  (None)  Upperright quadrant of the state transition matrix. Data Type: Array (3×3) 
OrbitSTMC  N  N  (None)  Lowerleft quadrant of the state transition matrix. Data Type: Array (3×3) 
OrbitSTMD  N  N  (None)  Lowerright quadrant of the state transition matrix. Data Type: Array (3×3) 
FuelTank
Parameter  Units  Description  
FuelMass  Y  Y  kg  Mass of fuel in the tank. Data Type: Real Number 
Volume  Y  Y  m^{3}  Volume of the tank. GMAT checks to ensure that the input volume of the tank is larger than the calculated volume of fuel loaded in the tank and throws an exception in the case that the calculated fuel volume is larger than the input tank volume. Data Type: Real Number 
FuelDensity  Y  Y  kg/m^{3}  Density of the fuel. Data Type: Real Number 
Pressure  Y  Y  kPa  Pressure in the tank. Data Type: Real Number 
Temperature  Y  Y  °C  Temperature of the fuel and ullage in the tank. GMAT currently assumes ullage and fuel are always at the same temperature. Data Type: Real Number 
RefTemperature  Y  Y  °C  The temperature of the tank when fuel was loaded. Data Type: Real Number 
Thruster
Parameter  Units  Description  
DutyCycle  Y  Y  (None)  Fraction of time that the thrusters are on during a maneuver. The thrust applied to the spacecraft is scaled by this amount. Note that this scale factor also affects mass flow rate. Data Type: Real Number 
ThrustScaleFactor  Y  Y  (None)  Scale factor that is multiplied by the thrust vector, for a given thruster, before the thrust vector is added into the total acceleration. Note that the value of this scale factor does not affect the mass flow rate. Data Type: Real Number 
GravitationalAccel  Y  Y  m/s^{2}  Value of the gravitational acceleration used for the FuelTank/Thruster calculations. Data Type: Real Number 
C1  Y  Y  N  Thrust coefficient C_{1}. Data Type: Real Number 
C2  Y  Y  N/kPa  Thrust coefficient C_{2}. Data Type: Real Number 
C3  Y  Y  N  Thrust coefficient C_{3}. Data Type: Real Number 
C4  Y  Y  N/kPa  Thrust coefficient C_{4}. Data Type: Real Number 
C5  Y  Y  N/kPa^{2}  Thrust coefficient C_{5}. Data Type: Real Number 
C6  Y  Y  N/kPa^{C7}  Thrust coefficient C_{6}. Data Type: Real Number 
C7  Y  Y  (None)  Thrust coefficient C_{7}. Data Type: Real Number 
C8  Y  Y  N/kPa^{C9}  Thrust coefficient C_{8}. Data Type: Real Number 
C9  Y  Y  (None)  Thrust coefficient C_{9}. Data Type: Real Number 
C10  Y  Y  N/kPa^{C11}  Thrust coefficient C_{10}. Data Type: Real Number 
C11  Y  Y  (None)  Thrust coefficient C_{11}. Data Type: Real Number 
C12  Y  Y  N  Thrust coefficient C_{12}. Data Type: Real Number 
C13  Y  Y  (None)  Thrust coefficient C_{13}. Data Type: Real Number 
C14  Y  Y  1/kPa  Thrust coefficient C_{14}. Data Type: Real Number 
C15  Y  Y  (None)  Thrust coefficient C_{15}. Data Type: Real Number 
C16  Y  Y  1/kPa  Thrust coefficient C_{16}. Data Type: Real Number 
K1  Y  Y  s  I_{sp} coefficient K_{1}. Data Type: Real Number 
K2  Y  Y  s/kPa  I_{sp} coefficient K_{2}. Data Type: Real Number 
K3  Y  Y  s  I_{sp} coefficient K_{3}. Data Type: Real Number 
K4  Y  Y  s/kPa  I_{sp} coefficient K_{4}. Data Type: Real Number 
K5  Y  Y  s/kPa^{2}  I_{sp} coefficient K_{5}. Data Type: Real Number 
K6  Y  Y  s/kPa^{C7}  I_{sp} coefficient K_{6}. Data Type: Real Number 
K7  Y  Y  (None)  I_{sp} coefficient K_{7}. Data Type: Real Number 
K8  Y  Y  s/kPa^{C9}  I_{sp} coefficient K_{8}. Data Type: Real Number 
K9  Y  Y  (None)  I_{sp} coefficient K_{9}. Data Type: Real Number 
K10  Y  Y  s/kPa^{C11}  I_{sp} coefficient K_{10}. Data Type: Real Number 
K11  Y  Y  (None)  I_{sp} coefficient K_{11}. Data Type: Real Number 
K12  Y  Y  s  I_{sp} coefficient K_{12}. Data Type: Real Number 
K13  Y  Y  (None)  I_{sp} coefficient K_{13}. Data Type: Real Number 
K14  Y  Y  1/kPa  I_{sp} coefficient K_{14}. Data Type: Real Number 
K15  Y  Y  (None)  I_{sp} coefficient K_{15}. Data Type: Real Number 
K16  Y  Y  1/kPa  I_{sp} coefficient K_{16}. Data Type: Real Number 
ThrustDirection1  Y  Y  (None)  ThrustDirection1, divided by the RSS of the three direction components, forms the x component of the spacecraft thrust vector direction. Data Type: Real Number 
ThrustDirection2  Y  Y  (None)  ThrustDirection2, divided by the RSS of the three direction components, forms the y component of the spacecraft thrust vector direction. Data Type: Real Number 
ThrustDirection3  Y  Y  (None)  ThrustDirection3, divided by the RSS of the three direction components, forms the z component of the spacecraft thrust vector direction. Data Type: Real Number 
ImpulsiveBurn
To compute ImpulsiveBurn parameters, GMAT requires that an ImpulsiveBurn has been executed using a Maneuver command like this
Manevuer myImpulsiveBurn(mySat)
In the case that an ImpulsiveBurn has not been applied, GMAT will output zeros for the maneuver components and issue a warning. We recommended that you evaluate maneuver parameters immediately after maneuvers are applied using the Maneuver command like this
Manevuer myImpulsiveBurn(mySat)
myVar = mySat.MyCoordinateSystem.Element1
This avoids issues that may occur if the manuever coordinate system is time varying, and the maneuver parameters are requested after further manipulation of the participants using other commands (such as Propagate). In that case, it is possible that the participants are no longer at the epoch of the maneuver, and unexpected results can occur due to epoch mismatches.
Parameter  Units  Description  
Element1  Y  Y  (None)  Xcomponent of the applied impulsive burn (deltaV). Data Type: Real Number 
Element2  Y  Y  (None)  Ycomponent of the applied impulsive burn (deltaV). Data Type: Real Number 
Element3  Y  Y  (None)  Zcomponent of the applied impulsive burn (deltaV). Data Type: Real Number 
V  Y  Y  (None)  Deprecated. Xcomponent of the applied impulsive burn (deltaV). If the Axes of the ImpulsiveBurn is not VNB, this parameter returns the xcomponent of the burn, not the velocity component. Data Type: Real Number 
N  Y  Y  (None)  Deprecated. Ycomponent of the applied impulsive burn (deltaV). If the Axes of the ImpulsiveBurn is not VNB, this parameter returns the ycomponent of the burn, not the normal component. Data Type: Real Number 
B  Y  Y  (None)  Deprecated. Zcomponent of the applied impulsive burn (deltaV). If the Axes of the ImpulsiveBurn is not VNB, this parameter returns the zcomponent of the burn, not the binormal component. Data Type: Real Number 
Array, String, Variable
Array, String, and Variable resources are themselves parameters, and can be used as any other parameter would. All of these are writable parameters, though only Variable resources and individual elements of Array resources can be plotted.
Examples
Using parameters in the Mission Sequence:
Create Spacecraft aSat Create Propagator aProp Create ReportFile aReport BeginMissionSequence % propagate for 100 steps For i=1:100 Propagate aProp(aSat) % write four parameters (one standalone, three coordinatesystemdependent) to a file Report aReport aSat.TAIGregorian aSat.EarthFixed.X aSat.EarthFixed.Y aSat.EarthFixed.Z EndFor
Using parameters as plot data:
Create Spacecraft aSat Create Propagator aProp Create XYPlot aPlot aPlot.XVariable = aSat.TAIModJulian aPlot.YVariables = {aSat.Earth.Altitude, aSat.Earth.ECC} BeginMissionSequence % propagate for 100 steps For i=1:100 Propagate aProp(aSat) EndFor
Using parameters as stopping conditions:
Create Spacecraft aSat aSat.SMA = 6678 Create ForceModel anFM anFM.Drag.AtmosphereModel = MSISE90 Create Propagator aProp aProp.FM = anFM BeginMissionSequence Propagate aProp(aSat) {aSat.Earth.Altitude = 100, aSat.ElapsedDays = 365}
Math Spec
Calculation Objects
Simple Parameters
MHA
Description: MHA is the mean hour angle of the xaxis of the selected central body's inertial equatorial frame, measured from the body's prime meridian.
Dependency:
Given:
Find:
Test Procedures
I generated truth data using STK 9 through the STK Object Model. These scripts are located in extern\Resources\FRR38_CalculationParameters\stk
. I matched data between the two tools as follows:
 Centralbody physical properties (mu, radii) are configured in the STK .cb files in the scenario directory, based on default GMAT data.
 I used EOP data for GMAT and STK from 20121030. I had to replace the default applicationwide data for each tool.
 Some mu values are hardcoded in the GMAT and STK scripts. These are all set to the GMAT default mu values.
The following table lists all available parameters and where each is tested (if at all). Calculation tests are tests that perform some calculation that affects the parameter. Read tests check that the parameter can be read in a script. Write tests check that the parameter can be assigned to in the Mission Sequence.
If a script name appears in a column, the parameter is tested as a part of the Calculation Parameters tests (specifically in the named script). If another requirement appears, then the parameter is being tested as a part of the test suite for that requirement. If (N/A) appears, that test type does not apply to the parameter. A () indicates that the parameter is not currently being tested, and that it should be tested as a part of the Calculation Parameters tests unless another requirement is listed afterwards.
There is an assumption being made that the ability to plot plottable parameters is being tested as part of XYPlot QA.
Even if a parameter has a test name listed, it needs work until the following are true:
 centralbody parameters are tested using:
 central body of the Spacecraft CoordinateSystem
 another planet (Venus or Earth)
 Luna (or another planet)
 userdefined body (UserMars or UserSaturn)
 coordinatesystem parameters are tested using:
 Spacecraft CoordinateSystem
 EarthMJ2000Eq (or Venus)
 EarthFixed
 usercreated bodyfixed (central body of the Spacecraft CoordinateSystem or Saturn)
All tests that need work by any of the above criteria are highlighted red in the table. Finished tests are highlighted green.
Parameter  Calculation Tests  Read Tests  Write Tests 
ElapsedSecs  SpacecraftElapsedTimeParams  SpacecraftElapsedTimeParams  (N/A) 
ElapsedDays  SpacecraftElapsedTimeParams  SpacecraftElapsedTimeParams  (N/A) 
A1ModJulian  FRR2  FRR2  FRR2 
A1Gregorian  FRR2  FRR2  FRR2 
TAIModJulian  FRR2  FRR2  FRR2 
TAIGregorian  FRR2  FRR2  FRR2 
TTModJulian  FRR2  FRR2  FRR2 
TTGregorian  FRR2  FRR2  FRR2 
TDBModJulian  FRR2  FRR2  FRR2 
TDBGregorian  FRR2  FRR2  FRR2 
UTCModJulian  FRR2  FRR2  FRR2 
UTCGregorian  FRR2  FRR2  FRR2 
CurrA1MJD  FRR2  FRR2  FRR2 
X  FRR1  FRR1  FRR1 
Y  FRR1  FRR1  FRR1 
Z  FRR1  FRR1  FRR1 
VX  FRR1  FRR1  FRR1 
VY  FRR1  FRR1  FRR1 
VZ  FRR1  FRR1  FRR1 
SMA  FRR1  FRR1  FRR1 
ECC  FRR1  FRR1  FRR1 
INC  FRR1  FRR1  FRR1 
RAAN  FRR1  FRR1  FRR1 
AOP  FRR1  FRR1  FRR1 
TA  FRR1  FRR1  FRR1 
MA  CbParams_*_2Body_*  CbParams_*_2Body_* CbParams_GEO_*  (N/A) 
EA  CbParams_*_2Body_* CbParams_GEO_* CBParams_Earth_EA  CbParams_*_2Body_*  (N/A) 
HA  CbParams_*_2Body_*  CbParams_*_2Body_*  (N/A) 
MM  CBParams_Earth_MM CbParams_*_2Body_* CbParams_GEO_*  CBParams_Earth_MM CbParams_*_2Body_* CbParams_GEO_*  (N/A) 
VelApoapsis  CbParams_*_2Body_*  CbParams_*_2Body_*  (N/A) 
VelPeriapsis  CbParams_*_2Body_*  CbParams_*_2Body_*  (N/A) 
Apoapsis  FRC10  FRC10  (N/A) 
Periapsis  FRC10  FRC10  (N/A) 
OrbitPeriod  CbParams_*_2Body_* CbParams_GEO_*  CbParams_*_2Body_* CbParams_GEO_*  (N/A) 
RadApo  FRR1  FRR1  FRR1 
RadPer  FRR1  FRR1  FRR1 
C3Energy  CbParams_*_2Body_* CbParams_GEO_*  CbParams_*_2Body_* CbParams_GEO_*  (N/A) 
Energy  CBParams_Earth_OrbitEnergy  CBParams_Earth_OrbitEnergy CbParams_*_2Body_*  (N/A) 
RMAG  FRR1  FRR1  FRR1 
RA  FRR1  FRR1  FRR1 
DEC  FRR1  FRR1  FRR1 
VMAG  FRR1  FRR1  FRR1 
RAV  FRR1  FRR1  FRR1 
DECV  FRR1  FRR1  FRR1 
AZI  FRR1  FRR1  FRR1 
FPA  FRR1  FRR1  FRR1 
EquinoctialH  FRR1  FRR1  FRR1 
EquinoctialK  FRR1  FRR1  FRR1 
EquinoctialP  FRR1  FRR1  FRR1 
EquinoctialQ  FRR1  FRR1  FRR1 
MLONG  FRR1  FRR1  FRR1 
SemilatusRectum  CbParams_*_2Body_*  CbParams_*_2Body_*  (N/A) 
HMAG  CbParams_*_2Body_*  CbParams_*_2Body_* CbParams_GEO_*  (N/A) 
HX  CSParams_*_2Body CSParams_*_2Body_*  CSParams_*_2Body CSParams_*_2Body_*  (N/A) 
HY  CSParams_*_2Body CSParams_*_2Body_*  CSParams_*_2Body CSParams_*_2Body_*  (N/A) 
HZ  CSParams_*_2Body CSParams_*_2Body_*  CSParams_*_2Body CSParams_*_2Body_*  (N/A) 
DLA  SelectedHyperbolicParams_*  SelectedHyperbolicParams_*  (N/A) 
RLA  SelectedHyperbolicParams_*  SelectedHyperbolicParams_*  (N/A) 
Altitude  CbParams_*_2Body_* CbParams_GEO_*  CbParams_*_2Body_* CbParams_GEO_*  (N/A) 
MHA  CbParams_*_2Body_*  CbParams_*_2Body_*  (N/A) 
Longitude  CbParams_*_2Body_* CbParams_GEO_*  CbParams_*_2Body_* CbParams_GEO_*  (N/A) 
Latitude  CbParams_*_2Body_* CbParams_GEO_*  CbParams_*_2Body_* CbParams_GEO_*  (N/A) 
LST  CbParams_*_2Body_*  CbParams_*_2Body_*  (N/A) 
BetaAngle  CbParams_*_2Body_* CbParams_GEO_*  CbParams_*_2Body_* CbParams_GEO_*  (N/A) 
BdotT  SelectedHyperbolicParams_*  SelectedHyperbolicParams_*  (N/A) 
BdotR  SelectedHyperbolicParams_*  SelectedHyperbolicParams_*  (N/A) 
BVectorMag  SelectedHyperbolicParams_*  SelectedHyperbolicParams_*  (N/A) 
BVectorAngle  SelectedHyperbolicParams_*  SelectedHyperbolicParams_*  (N/A) 
DCM11  FRR3  FRR3  (FRR3) 
DCM12  FRR3  FRR3  (FRR3) 
DCM13  FRR3  FRR3  (FRR3) 
DCM21  FRR3  FRR3  (FRR3) 
DCM22  FRR3  FRR3  (FRR3) 
DCM23  FRR3  FRR3  (FRR3) 
DCM31  FRR3  FRR3  (FRR3) 
DCM32  FRR3  FRR3  (FRR3) 
DCM33  FRR3  FRR3  (FRR3) 
EulerAngle1  FRR3  FRR3  (FRR3) 
EulerAngle2  FRR3  FRR3  (FRR3) 
EulerAngle3  FRR3  FRR3  (FRR3) 
MRP1  FRR3  FRR3  (FRR3) 
MRP2  FRR3  FRR3  (FRR3) 
MRP3  FRR3  FRR3  (FRR3) 
Q1  FRR3  FRR3  (N/A) 
Q2  FRR3  FRR3  (N/A) 
Q3  FRR3  FRR3  (N/A) 
Q4  FRR3  FRR3  (N/A) 
Quaternion  (FRR3)  (FRR3)  (FRR3) 
AngularVelocityX  FRR3  FRR3  (FRR3) 
AngularVelocityY  FRR3  FRR3  (FRR3) 
AngularVelocityZ  FRR3  FRR3  (FRR3) 
EulerAngleRate1  FRR3  FRR3  (FRR3) 
EulerAngleRate2  FRR3  FRR3  (FRR3) 
EulerAngleRate3  FRR3  FRR3  (FRR3) 
DryMass  (N/A)  SpacecraftPhysicalParams  SpacecraftPhysicalParams 
Cd  (N/A)  SpacecraftPhysicalParams  SpacecraftPhysicalParams 
Cr  (N/A)  SpacecraftPhysicalParams  SpacecraftPhysicalParams 
DragArea  (N/A)  SpacecraftPhysicalParams  SpacecraftPhysicalParams 
SRPArea  (N/A)  SpacecraftPhysicalParams  SpacecraftPhysicalParams 
TotalMass  FRR11 FRR9  FRR11 FRR9  (N/A) 
OrbitSTM  FRR13  FRR13  (N/A) 
OrbitSTMA  Params_STMSubsets_*  Params_STMSubsets_*  (N/A) 
OrbitSTMB  Params_STMSubsets_*  Params_STMSubsets_*  (N/A) 
OrbitSTMC  Params_STMSubsets_*  Params_STMSubsets_*  (N/A) 
OrbitSTMD  Params_STMSubsets_*  Params_STMSubsets_*  (N/A) 
FuelTank.FuelMass  FRR11 FRR9  TankParams  ReportSatHardware 
FuelTank.Volume  (FRR8)  TankParams  ReportSatHardware 
FuelTank.FuelDensity  (N/A)  TankParams  ReportSatHardware 
FuelTank.Pressure  (FRR8)  TankParams  ReportSatHardware 
FuelTank.Temperature  (N/A)  TankParams  ReportSatHardware 
FuelTank.RefTemperature  (N/A)  TankParams  ReportSatHardware 
Thruster.DutyCycle  (N/A)  ReportSatHardware  ReportSatHardware 
Thruster.ThrustScaleFactor  (N/A)  ReportSatHardware  ReportSatHardware 
Thruster.GravitationalAccel  (N/A)  ReportSatHardware  ReportSatHardware 
Thruster.C1  (N/A)  ReportSatHardware  ReportSatHardware 
Thruster.C2  (N/A)  ReportSatHardware  ReportSatHardware 
Thruster.C3  (N/A)  ReportSatHardware  ReportSatHardware 
Thruster.C4  (N/A)  ReportSatHardware  ReportSatHardware 
Thruster.C5  (N/A)  ReportSatHardware  ReportSatHardware 
Thruster.C6  (N/A)  ReportSatHardware  ReportSatHardware 
Thruster.C7  (N/A)  ReportSatHardware  ReportSatHardware 
Thruster.C8  (N/A)  ReportSatHardware  ReportSatHardware 
Thruster.C9  (N/A)  ReportSatHardware  ReportSatHardware 
Thruster.C10  (N/A)  ReportSatHardware  ReportSatHardware 
Thruster.C11  (N/A)  ReportSatHardware  ReportSatHardware 
Thruster.C12  (N/A)  ReportSatHardware  ReportSatHardware 
Thruster.C13  (N/A)  ReportSatHardware  ReportSatHardware 
Thruster.C14  (N/A)  ReportSatHardware  ReportSatHardware 
Thruster.C15  (N/A)  ReportSatHardware  ReportSatHardware 
Thruster.C16  (N/A)  ReportSatHardware  ReportSatHardware 
Thruster.K1  (N/A)  ReportSatHardware  ReportSatHardware 
Thruster.K2  (N/A)  ReportSatHardware  ReportSatHardware 
Thruster.K3  (N/A)  ReportSatHardware  ReportSatHardware 
Thruster.K4  (N/A)  ReportSatHardware  ReportSatHardware 
Thruster.K5  (N/A)  ReportSatHardware  ReportSatHardware 
Thruster.K6  (N/A)  ReportSatHardware  ReportSatHardware 
Thruster.K7  (N/A)  ReportSatHardware  ReportSatHardware 
Thruster.K8  (N/A)  ReportSatHardware  ReportSatHardware 
Thruster.K9  (N/A)  ReportSatHardware  ReportSatHardware 
Thruster.K10  (N/A)  ReportSatHardware  ReportSatHardware 
Thruster.K11  (N/A)  ReportSatHardware  ReportSatHardware 
Thruster.K12  (N/A)  ReportSatHardware  ReportSatHardware 
Thruster.K13  (N/A)  ReportSatHardware  ReportSatHardware 
Thruster.K14  (N/A)  ReportSatHardware  ReportSatHardware 
Thruster.K15  (N/A)  ReportSatHardware  ReportSatHardware 
Thruster.K16  (N/A)  ReportSatHardware  ReportSatHardware 
Thruster.ThrustDirection1  (N/A)  ReportSatHardware  ReportSatHardware 
Thruster.ThrustDirection2  (N/A)  ReportSatHardware  ReportSatHardware 
Thruster.ThrustDirection3  (N/A)  ReportSatHardware  ReportSatHardware 
ImpulsiveBurn.Element1  (N/A)  ImpulsiveBurnParams_VNB_Elements  ImpulsiveBurnParams_VNB_Elements 
ImpulsiveBurn.Element2  (N/A)  ImpulsiveBurnParams_VNB_Elements  ImpulsiveBurnParams_VNB_Elements 
ImpulsiveBurn.Element3  (N/A)  ImpulsiveBurnParams_VNB_Elements  ImpulsiveBurnParams_VNB_Elements 
ImpulsiveBurn.V  (N/A)  ImpulsiveBurnParams_VNB_VNBComponents  ImpulsiveBurnParams_VNB_VNBComponents 
ImpulsiveBurn.N  (N/A)  ImpulsiveBurnParams_VNB_VNBComponents  ImpulsiveBurnParams_VNB_VNBComponents 
ImpulsiveBurn.B  (N/A)  ImpulsiveBurnParams_VNB_VNBComponents  ImpulsiveBurnParams_VNB_VNBComponents 
Edge/Corner/Stress
Priority  Status  Summary 
Test parameters after setting epoch manually, instead of through propagation.  
Unique Validation
Priority  Status  Summary 
Set nonsettable params  
Set param w/ dependency  
Read w/ incorrect dependency type  
Set w/ incorrect data type  
Set/get w/ incorrect parent (attached hardware)  
Set/get w/ incorrect resource type  
Plot nonplottable params 
Unique Mode Tests
Priority  Status  Summary 
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 
Space Point Parameter Test Procedures.
This list documents test written for Spacepoint parameters for epoch and cartesian state parameters of Barycenter, LibrationPoint, etc.
 System Tests
 Input Tests
 Done: Try setting nondefault epoch in all supported formats and test output on a nonspacecrafttype space point (i.e. Libration Point or Barycenter
 Output Tests
 Test all parameters on all space point types (Spacecraft is already done)
 Done: Position parameters
 Done: (Bug 3973) Time Parameters
 Test Multiple Coordinate systems for for a mixture of space point types. (EarthFixed, Moon Ecliptic, etc. for LibrationPoint, Barycenter, CelestialBody)
 Done: Test default dependency (EarthMJ2000Eq) on a few space point types
 Test all parameters on all space point types (Spacecraft is already done)
 Input Tests
 Validation
 Done: Test invalid dependency is caught
 Done: Test invalid parameter that works for spacecraft is caught
Forcem Model Parameter Test Procedures.
 System Tests
 Input Tests
 Try all force types in the force model
 Harmonic gravity
 FMParams_GMAT_ISS_EarthSunLuna_EGM96_MSISE90_SRP
 FMParams_GMAT_GEO_EarthSunLuna_EGM96_MSISE90_SRP_SolidAndPoleTide
 Point masses
 FMParams_GMAT_ISS_EarthSunLuna_EGM96_MSISE90_SRP
 Drag
 FMParams_GMAT_ISS_EarthSunLuna_EGM96_MSISE90_SRP
 SRP
 FMParams_GMAT_ISS_EarthSunLuna_EGM96_MSISE90_SRP
 Relativity
 FMParams_GMAT_ISS_Earth_Relativity
 Thrust
 Thruster_FullPoly_EarthSat_EarthProp_3EarthThrusters_3CS_2
 Harmonic gravity
 Try different central bodies in the force model
 FMParams_GMAT_ISS_EarthSunLuna_EGM96_MSISE90_SRP
 FM_Params_GMAT_Mars1_AllPlanets_0_0_0_Short
 Try one case with Spacecraft about one body and force model about another
 Try all force types in the force model
 Output Tests
 Test all three acceleration parameters
 Tested in all scripts
 Test total acceleration parameter
 FMParams_GMAT_Mars1_AllPlanets_0_0_0_Short_TotalAccel
 Test all three acceleration parameters
 Input Tests
 Validation
 Test invalid dependency is caught
28 Comments
Joel Parker
Is this true? PSD shows Variable and Array also.
Anonymous
For the phrase "system shall allow the user to calculate or set", it should be "system shall calculate or allow the user to set"
(Boy, this is awkward commenting all the way down here)
Joel Parker
This is resolved. I replaced "calculate" with "request".
Anonymous
TGG: I like the "(read only)/(read/write)" bits. Though perhaps it should be (Calculated/Generated/UserSettable)
Anonymous
TGG: In the requirements for Impulsive burn parameters, Element1, etc are completely nondescriptive and awful as requirements. We might as well say the user can set thingys
Joel Parker
Good point. I changed them to "Thrust vector element #" to make it more clear.
Anonymous
TGG: GUI, general usage: The first step in choosing a parameter is to select the object (or resource) type from the Object Type list in the upper right (UPPER LEFT)
Joel Parker
Oh, the OTHER right!
Anonymous
TGG: GUI, general usage, you state:
However, what is the POINT of the ordering? That is not detailed anywhere.
Joel Parker
This is really dependent on each individual resource/command that's using the ParameterSelectDialog, so I'm not sure what I could put here. Do you think we should say essentially that, or just make sure we document it on each client resource/command?
Anonymous
TGG: Maybe just put what you said:
The significance of the ordering of the selected values is dependent on each individual resource/command that's using the ParameterSelectDialog. For some resources such as XXX, the ordering doesn't matter. However, for other resources such as YYY, the ordering is significant as it controls the BLAH BLAH. Please see the individual resource/command document for more information on the significance of the ordering.
Joel Parker
Ok, I added a couple sentences explaining this.
Anonymous
TGG: GUI enhancement
ParameterSelectDialog only allows one parameter in theSelected Value(s)
For such parameters, displaying a list box is VERY misleading. We should only display an edit box, a label, or maybe even nothing (let the highlighting of the parameter should which one is selected)
Joel Parker
Yeah, agreed. I'll add it to the Other Findings list and check in a ticket.
Anonymous
TGG: is the pencil meant to be "Write" property and the Chart is "Read" property?
Joel Parker
It's actually:
writable
plottable (like with XYPlot)
All are assumed to be readable. I don't think I'm using these icons in the final doc, actually, but I'll explain if I do.
Anonymous
TGG: One thing I wasn't sure from the text. If something is both calculated and usersettable, is it possible for the user to "unset" his/her value?
Joel Parker
Take
Spacecraft.X
for example. You can setSpacecraft.X
, and you can calculateSpacecraft.MarsFixed.X
.But if you set
Spacecraft.X = 5000
, there's no way to "undo" that back to the previous value (or the default value).Anonymous
LOJ:
FRR38.3.2.46 are deprecated.
In Description part, you may want to describe about default dependency. For example aSat.X has the default coordinate system of EarthMJ2000Eq and aSat.Altitude has default celestial origin of Earth.
Joel Parker
I deleted the deprecated requirements and added the default dependency stuff to Description.
Linda Jun
> Do you want to describe one other parameter type? There is spacecraft attached hardware parameters, such as thruster and tank parameters.
Joel Parker
Ok, I added the attachedhardware parameter type.
Linda Jun
> Do you want to describe how to select multiple object properties? (Select object properties while holding down Ctrl)
Joel Parker
I added a section to the paragraph above the one you quoted.
Linda Jun
Units of INC, RAAN, etc are °, do you want say "deg" instead?
Parameters with no units specified as N/A or (None). We need to consistent with other spec doc.
Joel Parker
Good points; I'll fix these when I move them to their respective final documents, based on whatever style we decide.
Anonymous
Worried that ImpulsiveBurn.V should be deprecated. What happens if the coordinate system is not VNB and the user asks for ImpulsiveBurn.V. I suspect the answer will be wrong.... need to verify and determine how to proceed.
Joel Parker
GMT3230 captures this.