Page Comparison

 09/27/22: Submitted NTR for Contributor Review

 10/11/22: Submitted Updated NTR into e-NTR

 10/24/22: Submitted in SRS, pending Patent Counsel Approval

Update and Submit New Technology Report (NTR) via E-NTR System (https://invention.nasa.gov/)

• DSC: update content section of NTR (start with R2022a Beta NTR) for team review 
• Innovator Review is 10 days (to review/submit comments), then can submit in SW Release System.

Update and Submit SW Release Package via SRS (https://softwarerelease.ndc.nasa.gov/)

• Software Release System (SRS) routes package through multiple reviews: 
  • POC Review
  • Initial SRA Review
  • Technology Transfer Office Review
  • Patent Counsel Office Review
  • IT Security Review
  • Export Control Office Review
  • Section 508 Coordinator Office Review
  • Other Review
  • Final SRA Review
  • 1/24/23:  Open source Apache 2.0 approved

11/20/22:  Biggest missing item are the TLE writer sample scripts.  

BCM Action assigned 9/15/22:  work with team to verify:

(1)  all old sample scripts work.  (Remember trick to run all scripts in a folder.  Need Run_Mode=Testing).  Look at all error and warning messages and make sure they are expected.  Need to do main Samples directory and every folder in the Samples directory.  Label new samples with starting prefix, Ex_R2022a_

• Assigning this to JudeN

(2)  Decide which new R2022a features need sample scripts and add them to the samples directory. 

• 09/22/22: BCM to generate R2022a Sample Script Spreadsheet to track new features and associated Sample Script name.  Sent to Feature POCs to populate spreadsheet.
• 09/26/22: reminded Feature POCs to look at spreadsheet

============================

This includes

-Ask SES if he think any more sample scripts needed.  

-Generic GOES sample scripts.  (Dont use GOES orbit or other data, generic torque recall, etc).

Jairus (Ground station masking, cov prop, IOD, TLE prop, Trk 2-23)

Steve S/Pete C (SAA sample script)

Above work ties in with the Release Notes.  (Review list above again after Release Notes written).  

Needed by App Freeze.

• Write examples that demonstrate new functionality
• Clean up all errors and warnings
• Remove deprecated fields
• Make sure all the old and new sample scripts run correctly.  (Note: There is a way to run all scrips in a folder, must be in Run_Mode=Testing)

Notes/Questions:  

1. The OFI scripts are stored in the OFI repo, not in the GMAT repo. That's because OFI is an externally maintained and managed project.When GMAT is built, e.g. the windows build machine, it copies the OFI sample scripts into latestcompleteversion. That's how those scripts will be part of the release without being in the GMAT repo.
2. The sample script file names be pre-pended with R2022a_
3. Make sure all the API Folder (and associated sub-folder) sample scripts are updated and run correctly.
4. Starting with R2021a:  For Nav, we will be adding python analysis scripts associated with the EKFS GPS point solution tutorial, to the GMAT releases.  Thus, in addition to the usual GMAT sample scripts, we should be making sure that the non-GMAT scripts, such as these python analysis scripts, also still run correctly. 

Needed by App Freeze.

See Writing Release Notes

Needed by Visual Freeze; see details below.

10/04/22: Contacted Katy Comber/279 to update cover page.

11/10/22;  No additional icons needed.  

Needed by Visual Freeze

None needed since not actively updating GUI.  

Needed by Release Day.  Completed 1/26/2023.

See the list of sites. Update this list as well, if necessary.

Needed by Release Day.  Located here.  Completed 1/26/2023.

(aerospace professors, ESA, chief technologists at NASA centers)

11/10/22:  need to test the three bug fixes related to the paths.  SES to test if he can.  Otherwise, Jairus will test.  

11/10/22:  SES and PC to test GMT-7861

After test complete, the test repo is frozen.  All tests must be written by this deadline.

DSC:  

Nav/SES: 

MS: 

PC:  

JE: 

DJC:  

PC: 

PC: 

Run VS analysis tool to identify possible issues.  (Note that the requirement here is just to "run" the tool.  Analysis can come later.)

Tool was run and analysis was done by Peter Candell on 9/20/2022

Windows nearly complete, most work remaining on Mac and Linux

11/10/22:  Ravi and Alex to look at Mac regression test failures.  

11/22/2022:  Steve S to also to take a look at failed Mac regression tests.  

11/28/2022:  For LInux, in addition to the usual Centos7/RHEL7 and Ubuntu test runs, for R2022a, we need additional RHEL8 test runs.  

Update Info.plist (Mac specific) and RunGMAT (shell script on Mac) as needed

Need copyright and release number/name at least - Info_GMAT.plist and RunGMAT

JHE: Updated on 10/21/22

Mac: RM/AC

Linux: DJC

Mac: 

Linux: 

Update for MATLAB version (MatLab R2022) and Python version (Python 3.9) as needed. This refers to the files in the SVN test repo, found under bin/+gmatrunner/

DJC updated linux files on 9/06/22

This should be before the Freezes-move there for the next release.

Pete C. Ran on 9/20/22, need to review results and work fixes

Pete, Tuan, and Jairus each reviewed independently 

JHE: Overall

RM: OFI

JHE: 

RM: 

Update application/License.txt file.  May be nothing to do if license did not change.

JHE: No changes to license.txt needed

RM: OFI has no license changes. Still Apache 2 and all dependencies are the same

Windows: PC, JE, TN

Linux: DJC

Mac: JG, RM/AC

Windows: 

Linux: 

Mac: 

Mostly related to the number of Windows warnings, but a check should be done for each OS.

Reviewed and fixed relevant warnings on Windows.

RM: Updated CMake to hide Mac compile warnings related to external components (e.g. Boost)

CCB

(DSC)

Do this right before code freeze.  Change from R2020a to R2022a.  

Pushed 11/10/22

Change GmatGlobals to use formal release name

Changed by AC on 11/7/22 as part of splash screen upgrade

DJC

JE

DJC: 

JE:  

Note that the requirement here is just to "run" the tool.  Analysis can come later.  
11/23/22:  Run on several components; likely to check more

Note: This involves running the Valgrind tool

DJC

(All)

DJC:  

JHE:  

Note: this must be done after CCB has accepted all final changes and we are ready to create RC1.  It requires coordination with the entire team as almost all source code files will be changed. 

This tool makes adding paragraphs and changing headers simple.  http://sourceforge.net/projects/findandreplace/

DJC:  Done for R2022a.  JHE has 10 files to update

OLD R2020a Notes below:

As of R2020a these directories have files that need updating.

• public\src (hpp, cpp)
• public\plugin (hpp, cpp)
• public/plugin/CInterfacePlugin/matlab
• public\application\matlab\
• internal\code (hpp,cpp)
• Readme file

  Updates for 2011 onwards were needed.  Files that assert copyright outside of the GMAT project were not updated.  Files with no copyright header at all were also not caught (there are at lest some - in the CsaltCWrapper code.  THere is likely more as well.

For R2020a, replace to

// Copyright (c) 2002 - 2018

RM: Updated for OFI

PC

DJC

This needs to be provided once the documentation is complete and built with the release candidate.  Note this cannot be done until all docs are frozen!   (SPH takes Windows RC, edits Help doc in Acrobat.  Sends to Mac/Linux)

Rebuild the OC/API HTML Help

PC 2022a help folder on mesa file and SharePoint. Ask PC for location. 

Old R2020a Notes below:

DJC: Make sure SPHINX for API and OC are included.   DJC added the files to application/docs. 

Note: For future releases, we should consider adding a build step to generate these automatically as part of the install process in CMake, rather than putting the generated files into the repo directly.

Bundle Windows zip

Is there anything to this besides putting the build in a zip? Steps for Mac/Linux here too?

For Windows, see gmat\build\install\windows-nsis\CreateInstall.bat

To be placed on Mesa-files

These are tests on the packaged versions of GMAT:  the zip bundle.  ( Test internal first. )

(Current smoke tests take a long time, about 4 hours.  Maybe later, cut this time down)

DSC/JHE/PC

AC/RM/JG

DJC

JN/PC/EB

JG/MS/AC

DJC/JR/JHE

At a minimum these need to be run individually by hand or run in GUI regression system.  Additionally, they must be run on a system that has no other installations of GMAT.  Past experience has shown that missing files, and configuration issues are not caught by running on machines used for development.

AC/PC/EB

DJC

AC/RM/JG/MS

Windows

Linux, /3/23 Action for DJC

Mac,  1/3/23 Action for AC.  

Old R2020a Notes below: 

Notes: 

(1)  Make sure all API Sample tests (API folder and API/Jupyter sub-folder) run correctly.  

(2)  For 2020a Mac, will not run API sample scripts.  

Definition:  Run scripts in Folder API and API/Jupyter.  

SES

BM/NH

(For final RC only)

On Final RC, this is 2 runs, Windows both internal and external. 

1/12/23:  After SWFO gives the OK on RC3, then OK.  1/19/23:  Got OK from SWFO.  

Have Khashy, RST, others take the RC for a test drive and report issues.  2022a-RC1: Passed to various users 12/12/2022

Save artifacts related to RC testing.  This includes matlab test scripts used and test results.  For an R2020a example, see \\mesa-file\595\GMAT\Builds\windows\VS2017_build_64\R2020a 

For R2022a, folder \\mesa-file\595\GMAT\Builds\windows\VS2017_build_64\R2022a has been created.  

Barb working this also.  

Remaining Steps as of 1/3/23

• Alex/Jairus to get python 3.6 installed on build machine.  (Submit new ticket and/or work with Mike S on old ticket as needed)
• Alex/Ravi/Jairus:  Verify that all internal vs. Public issues are ironed out.
  • Send both versions to DJC for a sanity check.
  • Have Ravi finish review.  
  • Place relevant files into \\mesa-file\595\GMAT\Builds\R2022a_ReleaseCandidates