Lunar Reconnaissance Orbiter
Cosmic Ray Telescope for the Effects of Radiation
CRaTER Science Operations Center
Test Plan
Document 32–01212
Revision A
October 24, 2007
Prepared by
Peter G. Ford
MIT Kavli Institute
Cambridge, MA 02139, USA
Lunar Reconnaissance Orbiter
CRaTER SOC Test Plan 32-01212 Rev.A
ii
Lunar Reconnaissance Orbiter
CRaTER SOC Test Plan 32-01212 Rev.A
Lunar Reconnaissance Orbiter
Cosmic Ray Telescope for the Effects of Radiation
CRaTER Science Operations Center
Test Plan
Release A
October 24, 2007
Approved:
Harlan Spence
CRaTER Principal Investigator
Date
Stan Scott
LRO Data Engineer
Date
iii
Lunar Reconnaissance Orbiter
CRaTER SOC Test Plan 32-01212 Rev.A
iv
Lunar Reconnaissance Orbiter
CRaTER SOC Test Plan 32-01212 Rev.A
Table of Contents
1
1.1
1.2
1.3
1.4
Preface ................................................................................................................................... 1
Distribution list .................................................................................................................1
Document change log .......................................................................................................1
TBD items .........................................................................................................................1
Applicable Documents ......................................................................................................2
2
2.1
2.2
2.3
2.4
2.5
Introduction .......................................................................................................................... 3
Scope .................................................................................................................................3
Components ......................................................................................................................3
Testing Approach ..............................................................................................................4
Testing Schedule ...............................................................................................................6
Testing Team Members and their Roles ...........................................................................6
3
3.1
3.2
3.3
Process for Testing SOC Requirements ............................................................................ 7
Materials ...........................................................................................................................7
External Data Requirements .............................................................................................7
Test Scenarios ...................................................................................................................7
4
4.1
4.2
4.3
Process for Testing the MOC Interface........................................................................... 11
Materials .........................................................................................................................11
Data Requirements ..........................................................................................................11
Test Activities .................................................................................................................11
5
5.1
5.2
5.3
5.4
Process for Testing the PDS Interface ............................................................................. 14
Materials .........................................................................................................................14
Data Requirements ..........................................................................................................14
Test Scenario ...................................................................................................................14
Additional Data validation ..............................................................................................15
List of Figures
Figure 1. The CRaTER SOC Hardware Layout........................................................................ 3
v
Lunar Reconnaissance Orbiter
CRaTER SOC Test Plan 32-01212 Rev.A
List of Tables
Table 1: Distribution list ................................................................................................................. 1
Table 2: Document change log ....................................................................................................... 1
Table 3: List of TBD items ............................................................................................................. 1
Table 4: SOC Testing Schedule ...................................................................................................... 6
Table 5: SOC Testing Team ........................................................................................................... 6
Table 6: Pipeline Test ..................................................................................................................... 7
Table 7: Online Resources Test ...................................................................................................... 8
Table 8: Backup Test ...................................................................................................................... 8
Table 9: Documentation Inspection Test ........................................................................................ 9
Table 10: Account Security Test..................................................................................................... 9
Table 11: Science Analysis Test ................................................................................................... 10
Table 12: MOC Command Test .................................................................................................... 11
Table 13: MOC Realtime Test ...................................................................................................... 11
Table 14: MOC Data Test ............................................................................................................. 12
Table 15: CRaTER Data Set Types and Contents ........................................................................ 14
Table 16: PDS Archive Test ......................................................................................................... 14
Table 17: Abbreviations and their meaning .................................................................................. 19
vi
Lunar Reconnaissance Orbiter
CRaTER SOC Test Plan 32-01212 Rev.A
1 Preface
This document describes the testing to be performed on the software, hardware, and documentation
that comprise the Science Operations Center (SOC) that supports the LRO CRaTER instrument
(Lunar Reconnaissance Orbiter Cosmic Ray Telescope for the Effects of Radiation).
1.1 Distribution list
Table 1: Distribution list
Name
Arlin Bartels
David Bradford
Tony Case
Rick Foster
Robert Goeke
Nicholas Gross
Steve Joy
Justin Kasper
William Mayer
Jeff Sanborn
Richard Saylor
Stanley R. Scott
Mark Sharlow
Harlan Spence
Erik Wilson
Organization
Email
GSFC/LRO
BU/Astronomy
BU/Astronomy/CSP
MIT/MKI
MIT/MKI
BU/CSP
UCLA/PDS/PPI
Harvard CFA/SAO
MIT/MKI
BU/Astronomy
GSFC/LRO
GSFC/LRO
UCLA/PDS/PPI
BU/Astronomy/CSP
BU/CSP
Arlin.Bartels@nasa.gov
bradford@bu.edu
tonycase@gmail.com
rickf@space.mit.edu
goeke@space.mit.edu
gross@bu.edu
sjoy@igpp.ucla.edu
jkasper@cfa.harvard.edu
wfm@space.mit.edu
jsanborn@bu.edu
Richard.Saylor@gsfc.nasa.gov
Stanley.R.Scott@nasa.gov
msharlow@igpp.ucla.edu
spence@bu.edu
wilsone@bu.edu
1.2 Document change log
Table 2: Document change log
Change
Date
Affected portion
Initial draft
Release A
07/31/07
10/24/07
All
Fig.1, Tables 1,2,4,5
1.3 TBD items
Table 3 lists items that are not yet finalized.
Table 3: List of TBD items
Item
Section(s)
Page(s)
MOT–SOC Operations Agreement
§1.4
2
1
Lunar Reconnaissance Orbiter
CRaTER SOC Test Plan 32-01212 Rev.A
1.4 Applicable Documents
CRaTER Science Operation Center Requirements Document, 32–01209, Revision B, October 25,
2006.
Spacecraft to CRaTER Data Interface Control Document, 431-ICD-000104, Revision B, March
30, 2007.
CRaTER Instrument Team Data Management and Archive Plan, 32–01210, Revision A, October
25, 2006.
External Systems ICD for the LRO Ground System, 431–ICD–000049, Revision A.
LRO MOC Secure Filecopy Implementation Brief, Paul Swenson, September 28, 2006.
Operations Agreement between the LRO MOT and the CRaTER SOC, TBD.
CRaTER Science Team and the PDS PPI Node ICD, 32–02080, Revision B, November 21, 2006.
CRaTER Information Technology Security and Contingency Plan, 32–01208, Revision A, July 1,
2007.
CRaTER Standard Product Data Record and Archive Volume Software Interface Specification,
32–01211, Revision B, August 1, 2007.
CRaTER Functional Instrument Description and Performance Verification Plan, 32-05002, Rev.
01, June 20, 2006.
PDS End-to-End Tests, Susie Slavney, PDS Geosciences Node, October 15, 2007.
2
Lunar Reconnaissance Orbiter
CRaTER SOC Test Plan 32-01212 Rev.A
2 Introduction
2.1 Scope
The purpose and scope of this document is to define the CRaTER Science Operations Center
(SOC) Test Plan to be used for verification of all the components that comprise the SOC. This
Test Plan document supports the following objectives:

Identify the CRaTER science operations components to be tested.

Describe the testing strategies to be employed.

List the deliverable elements and schedule of the test project.
2.2 Components
The CRaTER SOC comprises a rack of hardware components (see Figure 1), an internet
connection, and a staff. The hardware comes in two flavors: very secure (the SOC-A and its
backup, SOC-B) processors and the “Logger”, and not so secure (Crater-A and backup, CraterB). All data transmission between the SOC and the LRO MOC is made from/to the secure
processors, which are also responsible for all pipeline processing and data distribution.
The less secure hosts, Crater-A and -B, maintain copies of the pipeline data products and of the
real-time housekeeping data stream. They provide platforms into which CRaTER team members
can log in to work on scientific and engineering analysis. They also maintain web servers that
can be accessed (securely) by the science team.
Figure 1. The CRaTER SOC Hardware Layout
In addition to these local functions, several interfaces are defined. SOC-A and -B receive realtime ITOS telemetry from the MOC and return CRaTER command files to the MOC. They also
relay real-time telemetry and data products to Crater-A and -B. They are also accessible from the
3
Lunar Reconnaissance Orbiter
CRaTER SOC Test Plan 32-01212 Rev.A
“Logger”, a secure processor dedicated to security tasks, and via secure shell (ssh) login from
Crater-A and -B.
Crater-A and -B receive real-time telemetry and copies of pipeline products from SOC-A and -B.
They run data servers that distribute real-time telemetry to team members and they are
responsible for creating and validating the archive products that are sent to the Planetary Data
System. They also maintain HTTPS (secure web) servers to distribute CRaTER products and
information.
The SOC requirements to be tested are defined in the CRaTER Science Operation Center
Requirements Document (32–01209) and will be related to specific tests via the traceability
matrix in Appendix A, below. The functions that are local to the various SOC machines are
described in the Data Management and Archive Plan (32–01210). Security aspects are further
described in the IT Security and Contingency Plan (32–01208). The interface to the MOC is
described in the External Systems ICD for the LRO Ground System (431–ICD–000049) and
further elaborated in the Secure Filecopy Implementation Brief and in the Operations Agreement
between the LRO MOT and the CRaTER SOC. Refer to §1.4 for references to these documents.
2.3 Testing Approach
The SOC’s methodology breaks the task of testing down into three steps. In the first, the
requirements are segregated according to the following categories:
Functional
Requirements that define the fundamental actions that must take place in
accepting and processing the inputs and in processing and generating the
outputs.
Performance
Requirements placed on the software or on human interaction with the
software as a whole
Constraint of
Design
Specifying design constraints that can be imposed by other standards,
hardware limitations, etc.
Security
Specifying the factors that protect the system from accidental or malicious
access, use, modification, destruction, or disclosure.
In the second step, each requirement is further classified by the way or ways in which it is
proposed to test that the requirement has been correctly implemented:
Analysis
Analysis is a verification method utilizing techniques and tools such as
analytical assessments, simulations, models, or prior test data.
Inspection
Inspection is a method of verifying physical characteristics without the use
of special laboratory or test equipment, procedures, test support items, or
services. Standard methods such as visual gauges, etc. are used to verify
compliance with the requirements. Inspection also includes the review of
design documentation, material lists, code, plans, etc.
4
Lunar Reconnaissance Orbiter
CRaTER SOC Test Plan 32-01212 Rev.A
Test
Test is a quantitative method of verification wherein performance
requirements are verified by measurement during and after the controlled
application of functional and environmental stimuli. These measurements
usually require the use of special test equipment, recorded data, procedures,
laboratory equipment, or services.
Demonstration
A direct demonstration of capability as in showing a computer display, GUI,
or an instance of how the system appears/responds.
Finally, tests belonging to the same classification are grouped into test procedures. Each
procedure will be described in the current document by the following properties:
Test Title:
Name of the test
Test Objectives:
Identifies the functional capabilities being exercised.
Test Configuration:
Provides a block diagram showing the major processing elements, data
flows, and data communication mechanisms; includes details, as
necessary, of how the major processing elements are configured for
this test.
Participants & Support
Requirements:
Identifies the participating organizations and equipment, laboratory
circuits, and personnel support provided.
Test Data:
Describes and identifies by file name, script name, or other designation
required for test data sets; provides the source and physical locations of
the data. [Description of the test data should include volumes and
errors or insertion of anomalous conditions associated with the data.]
Test Case Descriptions:
Supplies a brief narrative description of the test case along with the
high-level success criteria.
Requirements List:
Provides a list of requirements to be verified by this test case; included
in each test procedure package is a requirements matrix.
Test Procedures:
Provides major event-level procedures covering the test set-up, test
execution, test result evaluation, and test termination.
Each SOC test is contained in an command-line executable script located in the ~soc/test
directory on a Crater-A/B processor and mirrored on SOC-A/B. Each script generates a report in
the ~/soc/test_report directory. For example, ~soc/test/pipeline_01.sh generates a report named
~soc/test_report/pipeline_01_001.txt, where “001” indicates that this is the first time that this
particular script has been run. All reports are text files in human-readable ASCII format.
Whenever a particular requirement has been tested, the report will contain a line of the form
Result: testid version requirement {PASS,FAIL}
For instance, if ~soc/test/backup_01.sh (see Table 8) determines that there is sufficient off-line
backup capacity to satisfy FN_060, a report, e.g., ~soc/test_report/backup_01_001.txt will
contain a line
5
Lunar Reconnaissance Orbiter
CRaTER SOC Test Plan 32-01212 Rev.A
Result: FN_060 backup_01 1 PASS
In this way, the current status of all SOC tests can be displayed by executing the command
grep ^Result: ~soc/test_report/*.txt
2.4 Testing Schedule
Table 4: SOC Testing Schedule
2007
J
Standard Products SIS*
Publish Test Plan*
Write Test Procedures
PDS SIS Peer Review
Special Products SIS*
Special Products Software
Local Testing
SOC–PDS Testing
SOC–MOC Testing
Publish Test Report*
Acceptance Testing
A
S
O
1
•
2
2008
N
D
J
F
M
A
M
J
•
•
•
J
A
S
O
N
D
2
•
•
•
1
2
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
1
2
•
•
•
•
* 1 = draft, 2 = final version
2.5 Testing Team Members and their Roles
Table 5: SOC Testing Team
Name
Function
Address
Phone
Michael Golightly
Deputy Project
Scientist & SOC
Lead (from 2008)
Peter Ford
SOC Lead (to 2008)
David Bradford
Systems Manager
Jeff Sanborn
Assoc. Systems Mgr
Tony Case
Graduate student
Erik Wilson
Software Engineer
Write test
report, conduct
PDS & MOC
tests.
Write test plan,
some procedures
Hardware and
systems testing
Systems testing
and security
Test the science
algorithms
Software testing
BU CAS Room 406
725 Commonwealth Ave.
Boston MA 02215
+001 617
358 4864
MIT 37-571, 70 Vassar St +001 617
Cambridge MA 02139
253 6485
BU CAS Room 511
+001 617
353 4884
Email
mgolight@bu.edu
pgf@space.mit.edu
bradford@bu.edu
jsanborn@bu.edu
BU CAS Room 406
BU CAS Room 416
6
+001 617
353 xxxx
+001 617
358 4423
tonycase@gmail.com
wilsone@bu.edu
Lunar Reconnaissance Orbiter
CRaTER SOC Test Plan 32-01212 Rev.A
3 Process for Testing SOC Requirements
3.1 Materials

Functioning SOC hardware (see Figure 1) and software, and SOC documentation.
3.2 External Data Requirements

CRaTER raw data files covering at least 24 hours of a calibration run, containing known
abnormalities, e.g., data gaps, corrupted packet headers, etc.

SPICE kernels covering the same period as the raw files describing a body in lunar orbit,
with a suitable CRaTER instrument frame kernel.

Housekeeping calibration coefficients that refer to the serial number of the instrument
that generated the raw data files.
3.3 Test Scenarios
Table 6: Pipeline Test
Test Title:
PIPELINE_01
Test Objectives:
The SOC can process measurement data to produce CRaTER
standard data products, and can update those products as
required. The data products shall include: a) a time-ordered
listing of event amplitude in each detector; b) linear energy
transfer for each processed event; c) a time-ordered listing of
secondary science data; d) a time-ordered listing of
housekeeping data.
Test Configuration:
Run on either the Crater–A or Crater–B processor, and then
repeated on either SOC–A or SOC–B (see Figure 1).
Participants & Support
Requirements:
To be performed by the SOC software test engineer.
Test Data:
Raw CRaTER calibration data spanning more than 24 hours
Dummy SPICE kernels spanning more than 24 hours
Housekeeping coefficients compatible with the raw data
Test Case Descriptions:
1. The script begins by running the ccat command with the “–
r” option and with input from a raw CRaTER calibration
data file. The output is compared with that of the rtlm.pl
command with the same input, to verify that the CRaTER
object library produces the same output as the rtlm script.
2. The next step is to run the Crater_Pipeline command and
generate a set of Level 0, 1, and 2 data products. Their PDS
labels and format files are verified by means of the Javabased Vtool command supplied by the PDS.
3. Finally, the script examines the Level 0, 1, and 2 data
7
Lunar Reconnaissance Orbiter
CRaTER SOC Test Plan 32-01212 Rev.A
products in detail to verify that the individual data fields are
within specified limits, that time fields are in ascending
order, and that the delimiters in the ASCII files (commas,
quotes, carriage returns, and newlines) are in their expected
locations.
Requirements List:
SOC: FN_010, FN_020, FN_030, FN_090.
Test Procedures:
~soc/test/pipeline_01.sh
Table 7: Online Resources Test
Test Title:
RESOURCE_01
Test Objectives:
To verify that there are sufficient on-line resources to satisfy the
operational requirements.
Test Configuration:
SOC–A, SOC–B, Crater–A, and Crater–B (see Figure 1).
Participants & Support
Requirements:
To be performed by the SOC software test engineer.
Test Data:
None.
Test Case Descriptions:
The test script runs a series of commands, e.g., ls, df, to
determine whether adequate resources are available. The script
may also ask Yes/No questions of the form “Does adequate
resource exist to satisfy the following requirement: text of
FN_xxx”.
Requirements List:
SOC: FN_050, FN_060, FN_070, FN_500, PF_060, PF_070,
PF_080.
Test Procedures:
~soc/test/resource_01.sh
Table 8: Backup Test
Test Title:
BACKUP_01
Test Objectives:
Verify that all online SOC data and software are backed up to
off-site storage, and can be fully or selectively restored without
breaking the security rules laid down in the CRaTER IT
security plan.
Test Configuration:
Run on either Crater–A or Crater–B (see Figure 1).
Participants & Support
Requirements:
To be performed by the SOC software test engineer.
Test Data:
File systems on the SOC RAID, mounted on SOC–A or –B
File systems local to Crater–A or –B
8
Lunar Reconnaissance Orbiter
CRaTER SOC Test Plan 32-01212 Rev.A
Test Case Descriptions:
Immediately prior to scheduled off-line backups, listings are
made of the contents of the SOC RAID and of the Crater–A and
–B local file systems. Sample files are then restored from the
backups and compared to the originals.
Requirements List:
SOC: FN_060
Security: PS–7, CP–9, CP–10.
Test Procedures:
~soc/test/backup_01.sh
Table 9: Documentation Inspection Test
Test Title:
DOCUMENT_01
Test Objectives:
Verify that existing SOC documentation adequately describes
the stated requirements, and that this documentation has been
reviewed and accepted.
Test Configuration:
None.
Participants & Support
Requirements:
To be performed by the SOC software test engineer.
Test Data:
None.
Test Case Descriptions:
The script asks the tester to verify the mention of the various
requirements in specific documents. The tester responds
PASS/FAIL to each.
Requirements List:
SOC: FN_080, FN_510, FN_520, IF_010, IF_020, IF_030,
IF_040, IF_050, IF_060, IF_070, IF_500, IF_510, PF_030,
PF_040, PF_050, PF_110.
Security: PL-4, CA-1, PS-1, AC-13, AC-14, AU-1, SC-1, MA1, SA-5, SA-6, SA-7, SA-8, IA-1, IA-2, IA-4, IA-5, IA-6, CA7, CM-6, SI-3, MP-2, MA-4, IR-1, IR-6
Test Procedures:
~soc/test/document_01.sh
Table 10: Account Security Test
Test Title:
ACCOUNT_01
Test Objectives:
Verify that access to the secure processors is protected in the
manner described by the SOC Security Plan (see §1.4).
Test Configuration:
Run on SOC–A/B.
Participants & Support
Requirements:
To be performed by the SOC software test engineer.
Test Data:
None.
Test Case Descriptions:
The script inspects the password protection and public key files
9
Lunar Reconnaissance Orbiter
CRaTER SOC Test Plan 32-01212 Rev.A
on the secure SOC processors.
Requirements List:
Security: AC–2, AU–2, AU–4, AU–5, AU–9, AU–11
Test Procedures:
~soc/test/account_01.sh
Table 11: Science Analysis Test
Test Title:
ANALYSIS_01
Test Objectives:
Verify that the Level 1 and Level 2 data fields are computed
according to the prescriptions of the CRaTER Software
Interface Specification and the Calibration Plan (see §1.4).
Test Configuration:
None.
Participants & Support
Requirements:
To be performed by the CRaTER PI or Project Scientist.
Test Data:
Level 1 and 2 files from the PIPELINE_01 test.
Test Case Descriptions:
The script displays raw (Level 0) detector values and calibrated
(Level 1, 2) results (eV and LET). The scientist verifies that
these results are as expected.
Requirements List:
SOC: FN_010, FN_030
Test Procedures:
~soc/test/analysis_01.sh
10
Lunar Reconnaissance Orbiter
CRaTER SOC Test Plan 32-01212 Rev.A
4 Process for Testing the MOC Interface
4.1 Materials

At the SOC, these tests require fully operational SOC–A/B processors and a correctly
configured switch between the secure SOC VLAN and the internet (see Figure 1).
REALTIME_01 also requires a Crater–A/B processor and a screen on which to view the
CHouse display.

The materials required at the MOC are unknown.
4.2 Data Requirements

These vary according to the particular test.
4.3 Test Activities
Table 12: MOC Command Test
Test Title:
COMMAND_01
Test Objectives:
Verify that CRaTER command files can be transmitted to the
MOC and that the SOC operator can subsequently verify their
receipt and their contents.
Test Configuration:
Run on either SOC–A or SOC–B (see Figure 1).
Participants & Support
Requirements:
To be performed by the SOC software test engineer.
Test Data:
One or more LRO Activity Request forms (ARFs) in ~soc/arf.
Test Case Descriptions:
The test script performs checks to ensure that the SOC–A/B
host is secure, and then transmits one or more ARFs to the
MOC host. It then invokes the approved secure MOC interface
and asks the test operator to verify that the transfer has taken
place. If possible, it requests that the ARFs be copied back to
the SOC and compared against the originals.
Requirements List:
SOC: IF_510.
Security: CA–3, CA–4, AC–1, AC–3, AC–7, AC–8, AC–17,
SC–5, SC–7.
Test Procedures:
~soc/test/command_01.sh
Table 13: MOC Realtime Test
Test Title:
REALTIME_01
Test Objectives:
Verify that LRO telemetry from the MOC/ITOS can be
received at the SOC and distributed via the realtime interface.
11
Lunar Reconnaissance Orbiter
CRaTER SOC Test Plan 32-01212 Rev.A
Test Configuration:
Run the TCP receiver on either SOC–A or SOC–B, pdist on
Crater–A or Crater–B, and display tools (e.g., CHouse) on
science workstations (see Figure 1).
Participants & Support
Requirements:
To be performed by the SOC software test engineer.
Test Data:
Housekeeping decalibration files at the SOC. CRaTER
houskeeping and secondary science data at the MOC.
Test Case Descriptions:
The script starts the TCP received locally and starts pdist and
CHouse on Crater–A/B. It waits while the test engineer requests
that the MOC begin sending test data. The script verifies that a
certain number of packets have been received, lists the number
of dropouts and corrupted packets, and asks the operator
whether the CHouse output was acceptible.
Requirements List:
SOC: FN_110, FN_510, IF_030, PF_020, PF_100, PF_110.
Security: CA–3, CA–4. AC–1, AC–3, AC–7, AC–8, AC–17,
SC–5, SC–7, IA–2, IA–4, IA–5, IA–6, CA–7, CM–6, SI–3,
MP–2, MA–4.
Test Procedures:
~soc/test/realtime_01.sh
Table 14: MOC Data Test
Test Title:
DATA_01
Test Objectives:
Verify that the SOC can receive the data products described in
the MOC External ICD (431–ICD–000049, see §1.4).
Test Configuration:
Run on either SOC–A or SOC–B (see Figure 1).
Participants & Support
Requirements:
To be performed by the SOC software test engineer.
Test Data:
None at the SOC. Numerous data products from the MOC, viz.
MOC-2 SLCK Clock Correlation
MOC-3 Spacecraft Housekeeping Data
MOC-4 CRaTER Housekeeping Data
MOC-5 CRaTER Raw Measurement Data
MOC-7 Daily Command Load Report
MOC-33 Event Kernel
MOC-40 Frame Kernels
MOC-42 Definitive Spacecraft Orientation (CK)
MOC-46 CRaTER Housekeeping Summary
MOC-47 CRaTER Raw Measurement Summary
FDF-29 Definitive Spacecraft Ephemeris (SPK)
Test Case Descriptions:
The test engineer starts the script, which waits while s/he
contacts the MOC and requests for the files to be transferred.
12
Lunar Reconnaissance Orbiter
CRaTER SOC Test Plan 32-01212 Rev.A
When they have arrived, the script verifies the contents of the
raw CRaTER data (MOC–4,5) and the SPICE kernels (MOC–
2,40,42 and FDF–29) by executing the pipeline. The gap files
are compared against MOC–46,47.
Requirements List:
SOC: FN_510, IF_010, IF-020, IF-030, IF_040, IF_050,
IF_060, IF_070, PF_010, PF_100, PF_110.
Security: CA–3, CA–4, AC–1, AC–3, AC–7, AC–8, AC–17,
SC–5, SC–7, IA–2, IA–4, IA–5, IA–6, CA–7, CM–6, SI–3,
MP–2, MA–4.
Test Procedures:
~soc/test/data_01.sh
13
Lunar Reconnaissance Orbiter
CRaTER SOC Test Plan 32-01212 Rev.A
5 Process for Testing the PDS Interface
5.1 Materials

These tests require fully operational Crater–A/B processors (see Figure 1) and a directory
tree populated with a test archive.

The materials required at the PDS PPI node are unknown.
5.2 Data Requirements

CRaTER Level 0, 1, and 2 products, e.g., those resulting from the PIPELINE_01 test,
along with their PDS labels, gap, and index files. The standard product types generated
by the CRaTER SOC are listed in Table 15.
Table 15: CRaTER Data Set Types and Contents
Key/Physical
Parameters
Data Set
NASA
Level
CODMAC
Level
CRAT_L0_PRI
CRAT_L0_SEC
CRAT_L0_HK
Raw CRaTER Experiment Data Record: pulse
heights, secondary science, and instrument
housekeeping
0
2
CRAT_L1_PRI
CRAT_L1_SEC
CRAT_L1_HK
CRaTER Calibrated Data Record, split into
primary and secondary science data, and
housekeeping
1
3
CRAT_L2_PRI
CRAT_L2_SEC
CRaTER Derived Data Record, part 1: LET
deposition in silicon. (Pulse heights converted
into energy deposited within unit path length
through each detector.)
2
3/41

PDS label (.LBL), format (.FMT), and catalog (.CAT) files describing the CRaTER
standard products.

Ancillary files as described in the CRaTER Standard SIS (32–01211, see §1.4).
5.3 Test Scenario
The PDS test follows the guidelines in the “PDS End-to-End Tests” document (see §1.4).
Table 16: PDS Archive Test
1
Test Title:
PDS_01
Test Objectives:
Run the software that creates an archive delivery file (tarball)
from the local SOC archive, and transmits it electronically to
the PDS PPI node, where it is unpacked and examined.
Test Configuration:
Run on Crater–A or Crater–B (see Figure 1).
The CR_L2_HK and CR_L2_SS products are CODMAC Level 3, CR_L2_PS is Level 4.
14
Lunar Reconnaissance Orbiter
CRaTER SOC Test Plan 32-01212 Rev.A
Participants & Support
Requirements:
To be performed by the SOC software test engineer.
Test Data:
See above.
Test Case Descriptions:
The test engineer will prepare a directory tree that mimics a
CRaTER archive volume, e.g., the EDR LROCRAT_0001. S/he
will use the VTool program and other resources from the
PIPELINE_01 test to verify the contents, which will then be
assembled into a tar archive and copied to the PDS PPI node
via the Internet using the ssh/scp protocol. Subsequent
verification by the PDS is a PPI node responsibility.
Requirements List:
SOC: FN_040, FN_520, IF_500.
Security: CA–3, CA–4, AC–1, AC–3, AC–7, AC–8, AC–17,
SC–5, SC–7.
Test Procedures:
~soc/test/pds_01.sh
5.4 Additional Data validation
The CRaTER EDR data archive volume set will include all CRaTER data acquired during the
LRO mission. The archive validation procedure described in this section applies to volumes
generated during both the cruise and prime phases of the mission.
PDS standards recommend that all data included in the formal archive be validated through a
peer-review process. This process is designed to ensure that both the data and documentation are
of sufficient quality to be useful to future generations of scientists.
The CRaTER team and the PDS will therefore convene a peer-review of the first archive volume
that they create using data from the nominal LRO mission. This review will determine whether
the archived data are appropriate to meet the stated science objectives of the instrument. The
panel will also review the archive product generation process for robustness and ability to detect
discrepancies in the end products; documentation will be reviewed for quality and completeness.
One of the primary questions addressed during the peer-review process will be: “Can an expert
in the use of similar data meet the stated science objectives of the experiment using only the data
and documentation included in this archive?” The peer-review panel may suggest changes to any
of the areas under review if the answer to this question is not affirmative.
As expertise with the instrument and data develops the CRaTER team may decide that changes
to the structure or content of its standard data products are warranted. Should these changes be
implemented the new data product and archive volume will be subjected to a full PDS peer
review, and this document will be fully revised to reflect the modified archive.
Additionally, the CRaTER team may generate and archive special data products that cover
specific observations or data-taking activities. This document does not specify how, when, or
under what schedule, any such special archive products will be validated.
15
Lunar Reconnaissance Orbiter
CRaTER SOC Test Plan 32-01212 Rev.A
Appendix A. Requirements Traceability Matrix
The following table shows the relationship between the tests defined in the current document and
either the “Requirement” stipulated in the CRaTER Science Operation Center Requirements
Document (32–01209), or the “Operational Controls” listed in the CRaTER Information Security
and Contingency Plan (32–01208). The methodology of each test is classified as A(nalysis),
I(nspection), T(est), or D(emonstration).
Requirement
Description
Type
Tests
Operational requirements (Functional)
FN_010
FN_020
FN_030
FN_040
FN_050
FN_060
FN_070
FN_080
FN_090
FN_110
The SOC shall perform measurement data processing to
produce CRaTER standard data products.
The SOC shall perform measurement data reprocessing to
update CRaTER standard data products as required by the
science team.
The SOC shall create the following CRaTER primary data
products:
a. Time-ordered listing of event amplitude in each detector
b. Linear Energy Transfer (LET) for each processed event
c. Time-ordered listing of secondary science data
d. Time-ordered listing of housekeeping data
The SOC shall provide the CRaTER data products
(CRATER_FN_030) and Level 0 data to the PDS
Planetary Plasma Interactions (PPI) Node for archive and
distribution.
The SOC shall provide sufficient disk space for: a. 10
days of incoming data from the MOC. b. 10 days of Level
1 derived products. c. 10 days of Level 2 derived products.
The SOC shall provide backup storage for disk space used
for software development, user accounts and on-line disk
space used for analysis.
The SOC shall provide sufficient disk resources to stage
PDS deliverables.
The SOC shall support priority assignment of processing
jobs based on input from the science team.
The SOC shall be capable of providing operational and
testing configurations.
The SOC networking connections shall be capable of
capturing, storing and processing CRATER science and
housekeeping at the maximum data rate possible.
T,A
T
T,A
PIPELINE_01
ANALYSIS_01
PIPELINE_01
PIPELINE_01
ANALYSIS_01
T
PDS_01
D
RESOURCE_01
D
BACKUP_01
D
RESOURCE_01
I
DOCUMENT_01
T
PIPELINE_01
T
REALTIME_01
D
RESOURCE_01
I, T
REALTIME_01
DATA_01
Testing requirements (Functional)
FN_500
FN_510
The SOC shall provide resources to support the
development and maintenance of CRATER measurement
data processing software.
The SOC shall provide resources to support testing with
the LRO Ground System.
16
Lunar Reconnaissance Orbiter
Requirement
FN_520
CRaTER SOC Test Plan 32-01212 Rev.A
Description
The SOC shall provide resources to support testing with
the PDS Planetary Plasma Interactions Node.
Type
Tests
I, T
DOCUMENT_01
PDS_01
DOCUMENT_01
Import requirements (Design)
IF_010
IF_020
IF_030
IF_030
IF_040
IF_050
IF_060
IF_070
The SOC shall obtain on a per orbit basis CRATER
instrument Level 0 science data from the LRO MOC.
The SOC shall obtain on a per orbit basis CRATER
instrument housekeeping data from the LRO MOC.
The SOC shall obtain real-time housekeeping data
provided by the MOC.
The SOC shall obtain the daily stored command load from
the LRO MOC.
The SOC shall obtain LRO SPICE SPK data from the
LRO MOC on a monthly basis.
The SOC shall obtain LRO SPICE CK data from the LRO
MOC on a monthly basis.
The SOC shall obtain CRATER Level 0 data needed for
reprocessing from the LRO MOC.
The SOC shall obtain LRO SPICE SCLK, LSK and FK
kernels from the LRO as needed.
T, I
T, I
T, I
T, I
T, I
T, I
T, I
T, I
DATA_01
DOCUMENT_01
DATA_01
DOCUMENT_01
REALTIME_01
DOCUMENT_01
DATA_01
DOCUMENT_01
DATA_01
DOCUMENT_01
DATA_01
DOCUMENT_01
DATA_01
DOCUMENT_01
DATA_01
DOCUMENT_01
Export requirements (Design)
IF_500
IF_510
The SOC shall provide the PDS Planetary Plasma
Interactions Node with the following CRATER data
products: a) Energy deposited in each detector for every
processed event; b) Linear energy transfer in each detector
for every processed event; c) CRaTER mass model.
The SOC shall provide to the LRO MOC instrument
command sequences.
I, T
PDS_01
DOCUMENT_01
I,T
COMMAND_01
DOCUMENT_01
T
DATA_01
T
REALTIME_01
I
DOCUMENT_01
I
DOCUMENT_01
I
DOCUMENT_01
I
RESOURCE_01
Performance requirements
PF_010
PF_020
PF_030
PF_040
PF_050
PF_060
The SOC shall take action to start the ingest of incoming
data within 3 hours after they are made available by the
LRO MOC.
The SOC shall receive data from the LRO MOC on a
daily basis 24 hours per day, 7 days per week, and 52
weeks per year.
The SOC shall process CRATER measurement data for
the entire nominal mission.
The SOC shall be capable of processing CRATER
measurement data for an extended mission, should the
mission be extended.
The SOC shall provide standard data products to the PDS
PPI Node every 3 months starting at launch +6 months.
The SOC shall provide adequate on-line storage to buffer
10 days of incoming data.
17
Lunar Reconnaissance Orbiter
Requirement
PF_070
PF_080
PF_100
PF_110
CRaTER SOC Test Plan 32-01212 Rev.A
Description
Type
Tests
I
RESOURCE_01
I
RESOURCE_01
T
T,I
REALTIME_01
DATA_01
REALTIME_01
DATA_01
DOCUMENT_01
I
DOCUMENT_01
I
DOCUMENT_01
T,D
COMMAND_01
REALTIME_01
DATA_01
PDS_01
These requirements relate to the provision of security
controls within the SOC itself, ensuring that access
control and monitoring is effective.
I,D
REALTIME_01
DATA_01
These requirements relate to reliability and security
issues affecting the interface between the SOC and
external entities. In this case, the only identified entity is
the BU off-site back-up facility.
These requirements relate to incident reporting.
These requirements relate to the provision and
maintenance of SOC user accounts.
D
BACKUP_01
I
D
DOCUMENT_01
ACCOUNT_01
The SOC shall provide adequate on-line storage to buffer
10 days of outgoing data.
The SOC shall provide adequate on-line storage for 10
days of CRATER standard data products.
The SOC shall provide a mechanism for the science team
to validate incoming data.
The SOC shall provide performance and trending
information.
Security requirements
PL–4, CA–1
PS–1, AC–13
AC–14, AU–1
SC–1, MA–1
SA–5, SA–6
SA–7, SA–8
IA–1
CA–3, CA–4
AC–1, AC–3
AC–7, AC–8
AC–17, SC–5
SC–7
IA–2, IA–4
IA–5, IA–6
CA–7, CM–6
SI–3, MP–2
MA–4
PS–7, CP–9
CP–10
IR–1,
AC–2,
AU–4,
AU–9,
IR–6
AU–2
AU–5
AU–11
These requirements relate to the availabilty of written
rules and regulations covering IT usage at the SOC, its
dissemination to all SOC user, and their express
acknowledgement of the rules and of the penalties if
these rules are not followed.
These requirements relate to the availability of
documentation for specific system and user-supplied
software to legitimate SOC users.
These requirements relate to the provision of an interface
between the SOC and external networks.
18
Lunar Reconnaissance Orbiter
CRaTER SOC Test Plan 32-01212 Rev.A
Appendix B. Abbreviations
Table 17: Abbreviations and their meaning
Abbreviation
Meaning
ARF
ASCII
BU
CAS
CDR
CK
CRaTER
CRC
DDR
E&PO
EDR
FTP
GB
GSFC
HK
HTML
ICD
LRO
MB
MIT
MKI
MOC
MOT
NAIF
NASA
ODL
PCK
PDS
PPI
SCET
SCLK
SIS
SOC
SPICE
SPK
TBC
TBD
Activity Request Form
American Standard Code for Information Interchange
Boston University
College of Arts and Sciences (BU)
Calibrated Data Record
C-matrix Kernel (NAIF orientation data)
Cosmic Ray Telescope for the Effects of Radiation
Cyclic Redundancy Check
Derived Data Record
Educational and Public Outreach
Experiment Data Record
File Transfer Protocol
Gigabyte(s)
Goddard Space Flight Center
Housekeeping
Hypertext Markup Language
Interface Control Document
Lunar Reconnaissance Orbiter
Megabyte(s)
Massachusetts Institute of Technology
MIT Kavli Institute for Astrophysics and Space Research
Missions Operations Center (GSFC, LRO)
Mission Operations Team (GSFC, LRO)
Navigation and Ancillary Information Facility (JPL)
National Aeronautics and Space Administration
Object Description Language
Planetary Cartographic and Physical Constants Kernel (NAIF)
Planetary Data System
Planetary Plasma Interactions Node (of the PDS)
Spacecraft Event Time
Spacecraft Clock
Software Interface Specification
Science Operations Center
Spacecraft, Planet, Instrument, C-matrix, and Events (NAIF data format)
SPICE (ephemeris) Kernel (NAIF)
To Be Confirmed
To Be Determined
19