RFP_ATT_C_TRACE_Code_Update_Process.pdf

Attachment C

TRACE CODE UPDATE PROCESS

1. Download current TRACE version and create a separate TRACE_mod version for development. Make applicable code changes.

2. Download current TRACE Automated Testing Framework (ATF) tarball from the ViewCVS section of the Developer's Website to a Test directory. Run Test/config.pl to configure your ATF environment per the ATF README.htm installation instructions.

3. Copy the base code version and the code version of interest to the executable directory created during installation of the ATF (e.g., /Test/Exe).

4. Execute ./runTests.pl [--help] [--force] [--numProcs] [--all] [--noTime] --vers=VERSION LIST_OF_SUITES from the /Test/Regression directory. The purpose of the runTests script is to drive execution of the TRACE verification test set.

5. Execute ./testSummary.pl [--help] [--s|--suite=NAME] [--r|--reverse] [--onlyStats] [--v|--vers|--version=VERSIONS] [--noSigDiff] [--noDiffs] from the /Test/Regression directory. The purpose of the testSummary script is to sweep through all TRACE output files for a given test suite (or suites) for a given pair of code versions) and report: 1) whether the run was successful, 2) a summary of all the run time statistics for all runs, and 3) the differences in output with respect to the previous code version. It creates two directories under the Regression directory: diffs and runStats.

6. Execute ./traceDiff.pl [--help] [--ignoreWhiteSpace] DIR1 DIR2 from the /trace/executables directory. The purpose of the traceDiff script is to compare two versions of the trace build directory structure and generate the necessary patch files to be able to update yet a third version. DIR1 shall be the unmodified base TRACE distribution and DIR2 shall be the modified TRACE distribution directory.

7. Execute ./buildTransmittal.pl [--help] [--force] [--incTests] [--verbose] --name TRANSMITTAL_NAME --diff DIFF_DIR --mods MOD_SRC from the /trace/executables directory. The purpose of the buildTransmittal script is to create a TRACE update package called TRANSMITTAL_NAME in the current directory. It will copy the diff files from DIFF_DIR into Diffs_AsSubmitted and the corresponding modified source files from MOD_SRC into Mod- Src_AsSubmitted. It will also create a template Summary.html file and place it in the Docs subdirectory.

8. Copy the runStats directory from the /Test/Regression directory into the /trace/executables/TRANSMITTAL_NAME directory to be part of the TRACE update package.

Attachment C

9. If as part of the verification testing performed, new test problems were created, then create a new subdir called NewInput and copy inputs to that subdir. The file names shall reflect their purpose, and comments shall be added to the top in the input model that the comments indicate what the test problem is supposed to test, what the expected result should be or should be compared to, and whether the model is a permutation of some other test problem already in the

ATF.

10. If, as part of verification testing, existing test problems were modified in the ATF in order for them to run correctly, create a new directory called ModInput and copy into it both the modified files themselves, as well as the patch/diff files of that test problems that show only what input parameters were changed.

11. Open the Summary.html file in the /TRANSMITTAL_NAME/Docs directory with "Mozilla Web Browser" and use File|Edit Page to edit the Code Change Summary file.

12. Include any documentation changes and test input files in the TRACE update package directory. When modifying any of the Framemaker documents, be sure to first turn on the change bar feature. Add any modified Framemaker documents to the Docs directory. Also include any other pertinent documents/reports/plots that are deemed important for someone else not intimately knowledgeable with the changes in order for them to be able to figure out the changes that were made.

13. Execute ./tar -cvzf TRANSMITTAL_NAME.tgz TRANSMITTAL_NAME from the /trace/executables directory. This will create the TRACE update package tarball.

14. Upload the TRACE update package tarball to the Transmittals section of the Developer's Website. Select File Type "code-update". Click "Upload File!" Done.