User Guides for Noise Modeling of Commercial Space Operations—RUMBLE and PCBoom (2018)

Below is the uncorrected machine-read text of this chapter, intended to provide our own search engines and external engines with highly rich, chapter-representative searchable text of each book. Because it is UNCORRECTED material, please consider the following text as a useful but insufficient proxy for the authoritative book pages.

P A R T I RUMBLE Launch Vehicle Acoustic Simulation Model Version 2.0 User Guide Michael M. James Alexandria R. Salton Matthew F. Calton Blue Ridge Research and Consulting, LLC Asheville, NC

9 Chapter 2 Introduction to RUMBLE 9 2.1 About RUMBLE 9 2.2 About this User Guide 11 Chapter 3 Technical Reference 11 3.1 Source 14 3.2 Propagation 15 3.3 Receiver 16 Chapter 4 System and Installation 16 4.1 System Requirements 16 4.2 Installation Package Contents 17 4.3 Software Installation 22 Chapter 5 Noise Metrics 22 5.1 Maximum Sound Level 22 5.2 Maximum A-weighted Sound Level 23 5.3 Sound Exposure Level 23 5.4 Day-Night Average Sound Level 23 5.5 Community Noise Equivalent Level 24 Chapter 6 Input File Descriptions 24 6.1 Fleet Input Format 25 6.2 Trajectory Input Format 26 6.3 Atmospheric Profile Input Format 27 Chapter 7 Program Operation 27 7.1 Getting Started 28 7.2 User Interface Navigation 29 7.3 Workspace 29 7.4 Study Tab 34 7.5 Spaceport Tab 34 7.6 Receptors Tab 37 7.7 Operations Tab 39 7.8 Scenarios Tab 43 7.9 Metric Results Tab 48 Chapter 8 Output File Descriptions 48 8.1 RUMBLE Grid File 48 8.2 RUMBLE Log File 50 Chapter 9 Error and Warning Messages 53 Chapter 10 Instructional Resources 53 10.1 Sample Cases 57 10.2 Create New Study Exercise C O N T E N T S

67 Chapter 11 Approval Process 67 11.1 Procedures for Review of Non-Default Methods and Data 68 11.2 List of Common Methods/Data and AEE Review Requirements 69 11.3 Guidance Regarding a Request to Use Non-Default Methods/Data 71 Chapter 12 RSIF Reference Guide 71 12.1 Introduction 71 12.2 XML Hierarchy 72 12.3 RSIF Examples 73 12.4 Notation 74 12.5 Element Descriptions 90 12.6 Group Descriptions 92 12.7 Complex Type Descriptions 103 12.8 Simple Type Descriptions 106 References 107 Abbreviations

9 2.1 About RUMBLE The launch vehicle acoustic simulation model, RUMBLE, is a software system designed to model commercial space launch, reentry, and static operations in space and time to compute far-field community noise exposure. A primary objective of RUMBLE is to help the analyst effi- ciently answer questions of interest about the environmental consequences of aviation activi- ties. The environmental consequences associated with noise from commercial space activities are evaluated through metrics, many of which are defined by regulatory standards. RUMBLE’s inputs, outputs, workflow, and GUI are designed to complement the FAA AEDT and simplify future integration efforts. 2.2 About this User Guide This user guide provides instruction on how to install, run, and interact with the RUMBLE application. The guide is organized into the following sections: • Chapter 2 introduces RUMBLE. • Chapter 3 presents the technical details of the methodologies employed by RUMBLE. • Chapter 4 provides detailed instructions on how to install and run RUMBLE. • Chapter 5 describes the noise metrics calculated by RUMBLE. • Chapter 6 defines the input files necessary to operate RUMBLE. • Chapter 7 provides instruction on how to interact with RUMBLE. • Chapter 8 describes the output files generated by RUMBLE. • Chapter 9 provides examples of the types of error and warning messages displayed in RUMBLE. • Chapter 10 presents examples and exercises to learn how to create study elements. • Chapter 11 provides guidance on the approval process when using RUMBLE to conduct envi- ronmental modeling for FAA actions subject to NEPA. • Chapter 12 describes the RSIF format and its usage. C h a p T E r 2 Introduction to RUMBLE For the benefit and ease of users familiar with AEDT, this user guide adopts the language and style of the AEDT 2c User Guide, Installation Guide, Technical Manual, ASIF Reference Guide, and Instructional Resources, with changes applicable to the RUMBLE application.

10 User Guides for Noise Modeling of Commercial Space Operations—rUMBLE and pCBoom The following symbols will appear throughout this document to highlight important information: Warnings to avoid errors in execution and ensure that the intended execution occurs. Notes containing helpful information and tips regarding the functionality of the tool. The question mark icon provides answers to common questions.

11 The RUMBLE noise modeling methodology was developed to produce accurate acoustic esti- mates relevant to environmental analysis of commercial space operations. The model is appli- cable to inflight and static operations of vertical and horizontal launch vehicles. Launch vehicle propulsion systems, such as liquid-propellant rocket engines and solid rocket motors, generate high amplitude, broadband noise. The majority of the noise is created by the rocket plume, or jet exhaust, interacting with the atmosphere, and combustion noise of the propellants. This results in noise that radiates in all directions. However, it is highly directive, meaning that a significant portion of the source’s acoustic power is concentrated in specific directions. The emitted sound is modified in several ways as it propagates outward. These effects include the source directivity, forward flight effects, Doppler effect, geometric spreading, atmospheric absorption, and ground interference to a receiver location. The received one-third octave (OTO) band sound levels from a source can be expressed as the sum of source components and propa- gation effects: Source Propagation SPL L A A A A A Aw ffe dir dop spread atm gnd= + + + + + +      where Lw = Source sound power level; Affe = Forward flight effects; Adir = Source directivity, azimuthal symmetry is assumed; Adop = Doppler effect; Aspread = Geometrical spherical spreading loss (point source); Aatm = Atmospheric absorption; and Agnd = Ground interference (interaction between direct and reflected acoustic rays). Rocket propulsion noise is calculated based on a specific source (vehicle trajectory point) to a receiver geometry (grid point). The position of the rocket and the receiver grid is provided in latitude and longitude, defined relative to a reference system (WGS84). Implementation of this geo-referenced coordinate system ensures that large-distance geometric calculations are completed with greater accuracy than traditional flat earth models. The core components of the proposed model are described in the following subsections. A conceptual overview of the rocket noise prediction model methodology is presented in Figure 3. 3.1 Source The definition of a rocket noise source’s strength and characteristics involves the acoustic power of the rocket, forward flight effects, directivity, and Doppler effect. C h a p t e r 3 Technical Reference

12 User Guides for Noise Modeling of Commercial Space Operations—rUMBLe and pCBoom 3.1.1 Acoustic Power Eldred’s Distributed Source Method 1 (DSM-1) [1] is utilized for the source characterization. The DSM-1 model determines the launch vehicle’s sound power based on its total thrust, exhaust- velocity, and the engine/motor’s acoustic efficiency. Recent validation by Blue Ridge Research and Consulting (BRRC) of the DSM-1 model demonstrated very good agreement between four separate full-scale rocket noise measurements and the empirical source curves [2]. The results of this validation are presented in Figure 4. The acoustic efficiency of the rocket engine/motor specifies the percentage of the mechanical power that is converted into acoustic power. The acoustic efficiency of the rocket engine/motor will be modeled using Guest’s variable acoustic efficiency [3]. In the far field, distributed sound sources are modeled as a single compact source located at the nozzle exit with an equivalent total sound power. Therefore, launch vehicle propulsion systems with multiple tightly clustered equivalent engines can be modeled as a single engine with an effective exit diameter and total Figure 3. Conceptual overview of RUMBLE model methodology. Figure 4. Validation of NASA SP-8072’s DSM-1 empirical curves—(Left) overall sound power level for various rockets—(Right) normalized relative power spectrum.

technical reference 13 thrust [1]. Additional boosters or cores (that are not considered to be tightly clustered) are handled by summing the noise contribution from each booster/core. 3.1.2 Forward Flight Effect A rocket in forward flight radiates less noise than the same rocket in a static environment. A standard method to quantify this effect reduces overall sound levels as a function of the relative velocity between the jet and the outside airflow [4, 5, 6, 7]. This outside airflow travels in the same direction as the rocket exhaust. At the onset of a launch, the rocket exhaust travels at far greater speeds than the ambient airflow. Conversely, for a vertical landing of a reusable launch vehicle, the ambient airflow around the descending rocket body and the jet exhaust are in opposing directions, yielding an increased relative velocity differential from the static condition, and creating increased jet mixing and resultant noise. As the differential between the forward flight velocity and exhaust velocity decreases, jet mixing is reduced, which reduces the corresponding noise emission. Notably, the maximum overall sound pressure levels are typically generated while the vehicle is at subsonic speeds. Thus, the modeled noise reduction is capped at a forward flight velocity of Mach 1. 3.1.3 Directivity Rocket noise is highly directive, meaning the acoustic power is concentrated in specific direc- tions and the sound pressure observed will depend on the angle from the source to the receiver. The NASA Project Constellation Program has made significant improvements in determining launch vehicle directivity of the reusable solid rocket motor (RSRM) [8]. The RSRM directivity indices (DI) incorporate a larger range of frequencies and angles than any previously available data. Recently, BRRC and NASA have improved the formulation of the RSRM DI by accounting for the spatial extent and downstream origin of the rocket noise source [9]. This improved formulation substantially changes the directionality of the Overall Sound Pressure Level (OASPL) radiation by approximately 14°, from 51° to 65°, and more closely matches measurements made in the far field during launches. An example sound level map using these modified DI is shown in Figure 5, where Figure 5. Predicted OASPL with modified DI—the downstream direction of the rocket is 0° and distance is indicated in nozzle diameters (De).

14 User Guides for Noise Modeling of Commercial Space Operations—rUMBLe and pCBoom the nozzle exhaust flows in the direction of 0°. These updated DI are included in the model. As future measurements make additional DI sets available, RUMBLE has the capability to implement updated DI sets specific to a spacecraft’s engine(s). 3.1.4 Doppler Effect The Doppler effect is defined as the change in frequency of a wave for an observer moving relative to its source. The frequency at the receiver is related to the frequency generated by the moving sound source and by the speed of the source relative to the receiver. The received frequency is higher (compared to the emitted frequency) if the source is moving toward the receiver, it is identical at the instant of passing by, and it is lower if the source is moving away from the receiver. During a rocket launch, an observer on the ground will hear a downward shift in the frequency of the sound as the distance from the source to receiver increases. The relative changes in frequency can be explained as follows: when the source of the waves is moving toward the observer, each successive wave crest is emitted from a position closer to the observer than the previous wave. Therefore, each wave takes slightly less time to reach the observer than the previ- ous wave, and the time between the arrivals of successive wave crests at the observer is reduced, causing an increase in the frequency. Conversely, if the source of waves is moving away from the observer, then each wave is emitted from a position farther from the observer than the previous wave; the arrival time between successive waves is increased, reducing the frequency. Figure 6 illustrates this spreading effect for an observer in a series of images, where (a) the source is stationary, (b) the source is moving less than the speed of sound, (c) the source is moving at the speed of sound, and (d) the source is moving faster than the speed of sound. As the frequency is shifted lower, the A-weighting filtering on the spectrum results in a decreased A-weighted sound level. For unweighted overall sound levels, the Doppler effect does not change the levels since all frequencies are accounted for equally. 3.2 Propagation The modeled sound propagation from the source to a receiver includes geometric spreading, atmospheric absorption, and ground interference. 3.2.1 Geometric Spreading When sound leaves a source, it travels out in all directions, expanding outward as it travels. This expansion reduces the sound level the farther the sound travels. For every doubling of the slant range distance between the source and a receiver, the received sound level is reduced by 6 decibels (dB). Figure 6. Effect of expanding wavefronts (decrease in frequency) that an observer would notice for higher relative speeds of the rocket relative to the observer for: (a) stationary source, (b) source velocity < speed of sound, (c) source velocity = speed of sound, (d) source velocity > speed of sound.

technical reference 15 3.2.2 Atmospheric Absorption Atmospheric absorption arises from the excitation of vibration modes of air molecules. Atmo- spheric absorption is a function of temperature, pressure, and relative humidity of the air. Atmospheric absorption is calculated using formulas found in the American National Standards Institute (ANSI) standard S1.26-1995 (R2004), which provides a sound attenuation coefficient per unit distance that is a function of frequency and atmospheric conditions. Since a rocket travels to high altitudes, it will experience a wide range of atmospheric conditions. The amount of absorp- tion depends on the parameters of the atmosphere in each layer and the distance that the sound travels through those layers. The total sound attenuation is the sum of the absorption experi- enced from each atmospheric layer. The ANSI sound attenuation algorithms are calculated for pure-tone sounds. As the rocket noise analysis is performed on an OTO-band basis, the SAE Method [10] is used as a simplified procedure to calculate the OTO-band attenuations utilizing the pure-tone sound attenuation of the ANSI standard. 3.2.3 Ground Interference The calculated results of the sound propagation using DSM-1 provide a free-field sound level at the receiver. However, sound propagation near the ground is most accurately modeled as the com- bination of a direct wave (source to receiver) and a reflected wave (source to ground to receiver) as shown in Figure 7. The ground will reflect sound energy back toward the receiver and will interfere both constructively and destructively with the direct wave. Additionally, the ground may attenu- ate the sound energy causing the reflected wave to propagate a smaller portion of energy to the receiver. The model accounts for the attenuation of sound by the ground [11, 12] when estimating the received noise. To account for the random fluctuations of wind and temperature on the direct and reflected wave, the effect of atmospheric turbulence is also included in the ground interference [11, 13]. RUMBLE assumes a homogeneous soft ground when calculating ground interference. 3.3 Receiver The received noise is estimated by combining the source components and propagation effects. RUMBLE calculates and prepares the modeled received noise for six noise metrics relevant to environmental noise analysis: A-weighted and unweighted Sound Level (LAMAX, LMAX), Sound Exposure Level (SEL), Day-Night Average Sound Level (DNL), and Community Noise Equivalent Level (CNEL). Figure 7. Sound propagation near the ground is modeled as the combination of a direct wave (blue) and a reflected wave (red) from the source to the receiver.

16 This section provides detailed instructions for installing and running RUMBLE 2.0. Installa- tion components must run locally. 4.1 System Requirements System specifications for computers capable of hosting the RUMBLE application are dis- played in Table 2. The preferred specifications are listed with suggested minimum requirements, where applicable. RUMBLE requires administrative privileges for both installation and execution of the software. RUMBLE uses web map servers to display map layers. Access to the web map servers is disabled when accessing RUMBLE without an internet connection. When disabled, map layers may require additional time to load. 4.2 Installation Package Contents 4.2.1 RUMBLE Software Install RUMBLE 2.0.exe – Installer for RUMBLE 2.0 4.2.2 Required Software RUMBLE uses MATLAB Runtime v92. MATLAB Runtime v92 will automatically be installed in conjunction with the installation of the RUMBLE software. If the target computer contains one or more previous versions of the MATLAB Runtime, complete one of the following steps to ensure reliable performance. 1. Uninstall previous versions of MATLAB Runtime, or 2. Edit the environment variables for MATLAB Runtime. If a previous version of MATLAB Runtime is required to execute other applications on the target computer, use the second option to edit the environment variables to avoid uninstalling the necessary MATLAB Runtime(s). To uninstall previous versions of MATLAB Runtime: 1. Navigate to Start, Control Panel, and select Uninstall a Program. 2. Select previous version(s) of MATLAB Runtime and click Uninstall/Change. 3. Follow the steps in the wizard to uninstall the runtime. C h a p t e r 4 System and Installation

System and Installation 17 To edit environment variables for MATLAB Runtime: 1. Navigate to Start, Control Panel, System and Security and select System. 2. Select Advanced System Settings. 3. Under the advanced tab, select Environment Variables . . . 4. Select Path in the “System variables” box and click Edit . . . 5. Find and select the entry for MATLAB Runtime v92. 6. Click Move Up to move MATLAB Runtime v92 to the top. 7. Click OK to exit and save changes. Windows limits the environment variable to 2,047 characters. In the event that the entry for MATLAB Runtime v92 cannot be found and the environment variable has a character length greater than 2,047, consider removing obsolete paths from the environment vari- able to make space for MATLAB Runtime v92. 4.3 Software Installation 4.3.1 Install RUMBLE Follow the instructions below to install the RUMBLE 2.0 application. 1. To start the installer, double-click the Install RUMBLE 2.0.exe file. 2. If a User Account Control dialog opens, click “Yes” to allow necessary files to be installed. 3. After performing a brief initial setup, the RUMBLE Installer wizard will open. If your internet connection requires a proxy server, click “Connection Settings” and follow the instructions. Press “Next” to continue to the next step (Figure 8). 4. Click Browse and select the desired RUMBLE installation folder. Click Add a shortcut to the desktop. Click Next.(Figure 9) 5. Click Browse and select the desired MATLAB Runtime installation folder. Click Next. (Figure 10) 6. Read the license terms and click Yes to accept the terms of the MATLAB Runtime license agreement. Click Next. (Figure 11) 7. Click Install to start the installation. The installation progress will be displayed. (Figure 12) 8. Read the RUMBLE End User License Agreement and click Finish to accept when installation is complete. (Figure 13) Minimum Preferred Operating Systems Microsoft Windows 7 x64-based Systems Microsoft Windows 7 x64-based Systems Processor Modern Dual Core Processor with 2 GHz or Higher Clock Modern Many Core (>2) Processors with 2 GHz or Higher Clock RAM 4 GB Memory 64 GB Memory Hard-disk Space 2 GB Storage 2 TB Storage RAID Software Requirements Adobe Reader DC Adobe Reader DC Screen Resolution 1280 x 768 1920 x 1080 Table 2. RUMBLE system specifications.

18 User Guides for Noise Modeling of Commercial Space Operations—rUMBLe and pCBoom Figure 8. RUMBLE install wizard – welcome. Figure 9. RUMBLE install wizard – installation options.

System and Installation 19 Figure 10. RUMBLE install wizard – folder selection. Figure 11. RUMBLE install wizard – license agreement.

20 User Guides for Noise Modeling of Commercial Space Operations—rUMBLe and pCBoom Figure 12. RUMBLE install wizard – ready to install. Figure 13. RUMBLE install wizard – installation complete.

System and Installation 21 4.3.2 Steps to Uninstall RUMBLE To uninstall RUMBLE: 1. Navigate to Start, Control Panel, and select Uninstall a program. 2. Select RUMBLE from the program list and click Uninstall. 3. The uninstall wizard will open. Click Uninstall. This will uninstall RUMBLE. (Figure 14) 4. Once the uninstallation is complete, the confirmation window will display. Click Finish to close the window. (Figure 15) Figure 15. RUMBLE install wizard – uninstallation complete. Figure 14. RUMBLE install wizard – ready to uninstall.

22 Noise metrics are used to describe the noise event and to identify any potential impacts to receptors within the environment. These metrics are based on the nature of the event and who or what is affected by the sound. Noise sources can be continuous (constant) or transient (short- duration) and contain a wide range of frequency (pitch) content. Determining the character and level of sound aids in predicting the way it is perceived. The unit of measure for defining a noise level or a noise exposure level is a decibel (dB). The number of decibels is calculated as 10log10 of the ratio of mean-square pressure or noise exposure. The reference root-mean-square pressure is 20 µPa, the threshold of human hearing. The noise level metrics computed by RUMBLE are associated with two groups: A-weighted and unweighted. A-weighted noise metrics give less weighting to the low and high frequency portions of the spectrum, providing a good approximation of the response of the human ear, and correlates well with an average person’s judgement of the relative loudness of a noise event. Unweighted noise metrics weight all frequencies equally. The noise metrics computed by RUMBLE are summarized in Table 3. The metrics that can be computed in RUMBLE can be organized into two categories: expo- sure-based metrics and maximum noise level metrics. The exposure-based metrics (SEL, DNL, and CNEL) represent the total sound exposure for a given time period. The maximum noise level metrics (LAMAX and LMAX) represent the maximum noise level at a receptor location, taking into account a particular set of spacecraft operations. The RUMBLE noise metrics are computed by applying metric-specific, time-averaging constants and/or day, evening, and nighttime weighting factors to the base metrics. The time-averaging constant applies a metric-specific duration factor to the noise metric. For exposure metrics, the weighting factor applies time-period-specific weighting (or penalties) to events that occur during those periods. For the maximum-level metrics, the weighting factors equal one. The weighting and averaging factors used to compute the noise metrics in RUMBLE are summarized in Table 4. The metric-specific time-averaging constants and weighting factors are used to accumulate the noise metrics from all the spacecraft operations at all the receptors in a RUMBLE analysis. The noise metrics computed by RUMBLE are described in more detail in the following sections. 5.1 Maximum Sound Level LMAX describes the maximum sound pressure level over the duration of a single event. 5.2 Maximum A-weighted Sound Level LAMAX describes the maximum A-weighted sound pressure level over the duration of a single event. C h a p t e r 5 Noise Metrics

Noise Metrics 23 5.3 Sound Exposure Level SEL is a logarithmic measure of the total acoustic energy transmitted to the listener during the event. However, SEL does not directly represent the sound level heard at any given time. Mathematically, it represents the sound level of a constant sound that would generate the same acoustical energy in one second as the actual time-varying noise event. 5.4 Day-Night Average Sound Level DNL averages sound levels at a location over a 24-hour period, with a 10 dB adjustment added to those noise events that take place between 10:00 p.m. and 7:00 a.m. (local time). This 10 dB penalty represents the increased human sensitivity to sounds that occur during normal sleeping hours. Therefore, the DNL depends on the number of annual daytime and nighttime events. 5.5 Community Noise Equivalent Level CNEL is a noise metric specific to the state of California. Similar to DNL, CNEL averages sound levels at a location over a 24-hour period. However, CNEL is based on three daily periods: daytime, evening, and nighttime. The daytime period is defined from 7:00 a.m. to 7:00 p.m., and the evening period is defined from 7:00 p.m. and 10:00 p.m., with a 5 dB adjustment added to noise events which occur during the evening period. The nighttime adjustment of 10 dB is identical to that of DNL. Metric Type RUMBLE Name Standard Name Definition/Full Name A-weighted Noise Metrics Exposure SEL LAE A-Weighted Sound Exposure Level DNL Ldn Day-Night Average Sound Level CNEL Lden Community Noise Equivalent Level Maximum Level LAMAX LASmx A-Weighted Maximum Sound Level Unweighted Noise Metrics Maximum Level LMAX LSmx Unweighted Maximum Sound Level Table 3. Summary of RUMBLE noise metric abbreviations and definitions. Noise Family Metric Type Noise Metric Weighting Factor Averaging Time (hr) Time- Averaging Constant Day Evening Night A-weighted Exposure Base SEL 1 1 1 - 1 DNL 1 1 10 24 86,400 CNEL 1 5 10 24 86,400 Maximum Level LAMAX 1 1 1 - - Unweighted Maximum Level LMAX 1 1 1 - - Table 4. RUMBLE noise metric-specific weighting and averaging factors.

24 RSIF provides a standard file format to allow for the import of data into a RUMBLE study. A detailed description of the RSIF format for the RSIF schema is provided in Chapter 12. The following sections describe the partial RSIF files required to import user-defined fleet data (air- frame, engine, and spacecraft), trajectory data, and atmospheric profile data. At a minimum, a RSIF consists of the standard XML declaration, a content section (fleet, trajectorySet, or atmosphericProfile), and content metadata. In the examples below, the RSIF tags appear between < > or </> braces. The sample content information (which can be set by the user) appears between these tags. The examples should be used as an aid for understanding the RSIF format, and not as a data reference. 6.1 Fleet Input Format The fleet input data describes the user-defined spacecraft fleet participating in the study. Refer to Section 12.7.11 for a detailed description of the required and optional parameters associated with the fleet input data. Fleet data may be imported into an existing study from the Operations tab by selecting Browse from the Choose Spacecraft drop-down menu. <RsifXml version=”1” content=”fleet” xmlns:RsifXml=”RSIF.xsd” xmlns:xsi=”http://www.w3.org/2001/XMLSchema-instance”> <fleet> <airframe> <model>Notional Suborbital Spacecraft 1 - Airframe</model> <cores> <core> <identifier>Primary</identifier> <numEngines>1</numEngines> <count>1</count> </core> </cores> </airframe> <engine> <code>Notional Suborbital Spacecraft 1 - Engine</code> <propellantDescription>LOX/Kerosene(RP-1)</propellantDescription> <thrust>13340</thrust> <nozzleExitDiameter>12.9</nozzleExitDiameter> <nozzleExitVelocity>9514</nozzleExitVelocity> <nozzleCount>1</nozzleCount> </engine> <spacecraft> <identifier>Notional Suborbital Spacecraft 1</identifier> C h a p t e r 6 Input File Descriptions

Input File Descriptions 25 <description>Notional Spacecraft for Sample Case 1</description> <airframeModel>Notional Suborbital Spacecraft 1 - Airframe</airframeModel> <cores> <core> <identifier>Primary</identifier> <engineCode>Notional Suborbital Spacecraft 1 - Engine</engineCode> </core> </cores> </spacecraft> </fleet> </RsifXml> 6.2 Trajectory Input Format The trajectory input data describes the user-defined trajectories associated with the study. Refer to Section 12.5.27 for a description of the required and optional parameters asso ciated with the trajectory input data. Trajectory data may be imported into an existing study from the Oper- ations tab by selecting Browse from the Trajectory drop-down menu. Trajectory data input is the only external user-defined input required to operate RUMBLE. <RsifXml version=”1” content=”trajectorySet” xmlns:RsifXml=”RSIF.xsd” xmlns:xsi=”http://www.w3.org/2001/XMLSchema-instance”> <trajectorySet> <trajectory> <name>Notional Suborbital Trajectory 1</name> <opType>Launch</opType> <trajectoryNodes> <trajectoryNode> <id>NaN</id> <description>NaN</description> <time>0</time> <latitude>28.632758</latitude> <longitude>-80.706064</longitude> <altitude>7</altitude> <speed>7</speed> <flightPathHeading>150</flightPathHeading> <flightPathAngle>0</flightPathAngle> <vehicleHeading>150</vehicleHeading> <vehiclePitch>0</vehiclePitch> </trajectoryNode> <trajectoryNode> <id>NaN</id> <description>NaN</description> <time>1</time> <latitude>28.632751</latitude> <longitude>-80.706059</longitude> <altitude>7</altitude> <speed>7</speed> <flightPathHeading>150</flightPathHeading> <flightPathAngle>0.1</flightPathAngle> <vehicleHeading>150 </vehicleHeading> <vehiclePitch>0.1</vehiclePitch> </trajectoryNode> </trajectoryNodes> </trajectory> </trajectorySet> </RsifXml>

26 User Guides for Noise Modeling of Commercial Space Operations—rUMBLe and pCBoom 6.3 Atmospheric Profile Input Format The atmospheric profile input data describes the user-defined atmospheric profile(s) asso- ciated with the study. Refer to Section 12.5.4 for a description of the required and optional parameters associated with the atmospheric profile input data. Atmospheric profile data may be imported into an existing study from the Metric Results tab by selecting Browse from the Atmo- spheric Profile drop-down menu. <RsifXml version=”1” content=”atmosphericProfile” xmlns:RsifXml=”RSIF.xsd” xmlns:xsi=”http://www.w3.org/2001/XMLSchema-instance”> <atmosphericProfile> <name>U.S. Standard Atmosphere</name> <atmosphericProfileNodes> <atmosphericProfileNode> <altitude>0</altitude> <temperature>58.91</temperature> <pressure>29.92</pressure> <humidity>76.03</humidity> <soundSpeed>1116.47</soundSpeed> </atmosphericProfileNode> <atmosphericProfileNode> <altitude>1640</altitude> <temperature>53.15</temperature> <pressure>28.19</pressure> <humidity>76.03</humidity> <soundSpeed>1110.24</soundSpeed> </atmosphericProfileNode> </atmosphericProfileNodes> </atmosphericProfile> </RsifXml>

27 This chapter provides instruction on how to interact with the RUMBLE 2.0 application. It is organized according to the order in which the tabs appear in the RUMBLE application, from left to right. High-level steps for creating a new study in RUMBLE are described in Section 7.1.2. 7.1 Getting Started If RUMBLE is not already installed, follow the instructions provided in Chapter 4 to install the application software. RUMBLE requires administrative privileges for both (1) installation and (2) execution of the software. 7.1.1 Start RUMBLE 2.0 To start the RUMBLE 2.0 application: 1. On the Desktop, right click on the RUMBLE shortcut and click Run as Administrator. – RUMBLE 2.0 can also be accessed by navigating to C:\Program Files\BRRC\RUMBLE\ application and right-clicking on the executable named RUMBLE.exe and selecting Run as Administrator. 2. The Study tab opens upon application startup. – Click Open to select an existing study (see Section 7.4.1 for more information); – Click New to create a blank study (see Section 7.4.3 for more information); or – Click Import to import a study into RUMBLE (see Section 7.4.2). 7.1.2 High-Level Workflow for Building a New Study 1. In the Study tab, create a new study (Section 7.4). 2. In the Spaceport tab, add a spaceport (Section 7.5). 3. In the Receptors tab, add receptors (Section 7.6). 4. In the Operations tab, create desired operations (Section 7.7). 5. In the Scenarios tab, create desired scenario(s) for the operations (Section 7.8). 6. In the Metric Results tab, define metric result(s) (Section 7.9). 7. In the Metric Results tab, run the metric result(s) and view contours (Sections 7.9.3 and 7.9.6). Study progress is saved upon exiting the application and no explicit “save” is required. How- ever, saving the study periodically as changes are made is recommended. C h a p t e r 7 Program Operation

28 User Guides for Noise Modeling of Commercial Space Operations—rUMBLe and pCBoom 7.2 User Interface Navigation The RUMBLE 2.0 graphical interface consists of three main components (Figure 16): 1. Tabs 2. Ribbon 3. Workspace The Study tab opens upon application startup (Figure 16). The recommended screen resolution is 1920 x 1080 (or full HD resolution). 7.2.1 Tabs RUMBLE 2.0 features are organized by tabs as follows: Study Tab The Study tab includes the following menu options: • Open: displays the Open Study box. • Import: displays the Import Study box. • New: displays the Create New Study box. • Log: displays RUMBLE log messages. • Help & About: displays RUMBLE version and a link to the User Guide. See Section 7.4 for more information on Study tab functionality. Figure 16. Study tab.

program Operation 29 Spaceports Tab The Spaceports tab supports adding a spaceport. See Section 7.5 for more information. Receptors Tab The Receptors tab supports setting up receptors. See Section 7.6 for more information. Operations Tab The Operations tab supports managing spacecraft operations. See Section 7.7 for more information. Scenarios Tab The Scenarios tab supports setting up scenarios. See Section 7.8 for more information. Metric Results Tab The Metric Results tab supports construction and processing of metric result definitions, and generating and viewing result layers. See Section 7.9 for more information. 7.2.2 Ribbon The ribbon provides easy access to commands that are applicable in the current tab. The com- mand buttons are grouped together by functional categories. 7.3 Workspace The workspace in the RUMBLE interface is the area where users can complete actions initi- ated via the ribbon buttons. In the Receptors, Operations, Scenarios, and Metric Results tabs, the workspace is divided into two sections. While the divisions are consistent between these tabs, the content changes as specific to each tab. Table Work Area: The table work area contains a list of data available for use in the currently selected tab. This work area is present in every tab except for the Study and Spaceport tabs. Details Work Area: The details work area provides appropriate tools to manage the content in the table work area. 7.4 Study Tab In RUMBLE 2.0, the Study tab provides access to studies. See the following sections for detailed information on the features of the study tab. 7.4.1 Open Study To open a study: 1. Click the Study tab and click Open to display the Open Study work area (Figure 17). 2. Click on the name of the desired study. 3. Click Open to load the study. Sample Studies The following study files are included in RUMBLE 2.0: • Horizontal Launch Sample Case: This study contains the vehicle and trajectory input data associated with a notional horizontal launch operation. • Vertical Launch Sample Case: This study contains the vehicle and trajectory input data associated with a notional vertical launch operation.

30 User Guides for Noise Modeling of Commercial Space Operations—rUMBLe and pCBoom The sample studies contain different data sets and highlight different features of RUMBLE. Refer to Section 10.1 for a detailed description of the content included in the two sample studies. Sample case studies cannot be edited or deleted. 7.4.2 Import Study To import a full study from RSIF: 1. Click the Study tab and click Import to display the Import Study work area (Figure 18). 2. Click the Browse button, navigate to the RSIF study file and select Import. 3. In the study name field, enter a unique study name or accept the default name. – Enter a description in the study description field, if desired. 4. Click Create to import the study. When the import is complete, the imported study is opened and the Spaceports tab is displayed. 7.4.3 Create New Study To create a new study: 1. Click the Study tab, then click New to display the Create New Study work area (Figure 19). 2. Enter a study name (study description is optional). 3. Click Create to create a new study. Figure 17. Study tab Open panel.

Figure 18. Study tab Import panel. Figure 19. Study tab New panel.

32 User Guides for Noise Modeling of Commercial Space Operations—rUMBLe and pCBoom 7.4.4 Save Study To close the currently open study, click the Study tab then click Save from the Actions ribbon group. 7.4.5 Close Study To close the currently open study, click the Study tab then click Close from the Actions ribbon group. An opened study must be closed before a new study can be opened, imported, or created. 7.4.6 View RUMBLE Log To view system status and logged information, click on the Study tab and click Log (Figure 20). The information shown in the message pane is also written to the RUMBLE.log file in the C:\RUMBLE\Logs folder. The message pane displays the system status and messages, timestamp, and the originating RUMBLE module name. There are three different log levels: • Information; • Warning: minor (non-critical) issues/events; • Error: a critical error or problem. To clear all messages from the message pane, click Clear Log. To open the RUMBLE log file, click Open Log File. Figure 20. Study tab Log panel.

program Operation 33 7.4.7 Help & About To view version information, click on the Study tab then click Help & About (Figure 21). The following information is displayed: • The version numbers for RUMBLE and MATLAB Runtime. • An Open user guide button which opens a PDF of the RUMBLE 2.0 User Guide. 7.4.8 Exit the RUMBLE Application To exit the RUMBLE 2.0 application, click the “X” at the top right corner of the application window. Study progress is saved upon exiting the application and no explicit “save” is required. However, saving a study periodically as changes are made is recommended. 7.4.9 Delete Existing Study To delete an existing study: 1. Click the Study tab and click Open to display the Open Study work area. 2. Click on the name of the desired study. 3. Click Delete to delete the study. Alternatively, 1. Exit the RUMBLE application before deleting a RUMBLE study file. 2. Locate the study output directory C:\RUMBLE\DATA\. 3. Select the study folder of interest and delete. Figure 21. Study tab Help & About panel.

34 User Guides for Noise Modeling of Commercial Space Operations—rUMBLe and pCBoom 7.5 Spaceport Tab The Spaceport tab supports adding a spaceport. 7.5.1 Add Spaceport To add a spaceport: 1. Click the Spaceport tab and click New to enable the Spaceport work area (Figure 22). 2. Enter the appropriate data in the required fields. 3. Click Save to save the spaceport in the study, or Cancel to discard changes. To edit an existing spaceport: 1. Click the Spaceport tab and click Edit to enable the Spaceport work area. 2. Edit the desired fields. 3. Click Save to apply changes or Cancel to discard changes. 7.6 Receptors Tab To view receptors in the current study, click the Receptors tab. There are two receptor types: point and grid. Receptors can be created, copied, edited, and deleted; however, receptors that are assigned to a metric result cannot be deleted. Figure 22. Spaceport tab.

program Operation 35 7.6.1 Point-Type Receptor To create a point-type receptor: 1. Click on the Receptors tab and click New, or select an existing receptor from the Table of Receptors and click Copy in the Actions ribbon group to create a new receptor from an existing receptor. 2. From the Type drop-down menu, select Point to display the point receptor details work area (Figure 23). 3. Enter the appropriate data in the required fields. – The Latitude and Longitude are set to the spaceport origin by default. Update the location information of the location of interest. 4. Click Save to apply changes or Cancel to discard changes. To edit a point-type receptor: 1. Select the desired receptor from the Table of Receptors and click Edit in the Actions ribbon group. 2. Edit the desired fields. 3. Click Save to apply changes or Cancel to discard changes. Elevation MSL (ft): This elevation corresponds to the elevation of the area, for example, the elevation of the spaceport. If the receptors are at a different elevation than the spaceport, the appropriate elevation should be used. Figure 23. Receptors tab – point receptor details.

36 User Guides for Noise Modeling of Commercial Space Operations—rUMBLe and pCBoom 7.6.2 Grid-Type Receptor To create a grid-type receptor: 1. Click on the Receptors tab and click New, or select an existing receptor from the Table of Receptors and click Copy in the Actions ribbon group to create a new receptor from an existing receptor. 2. From the Type drop-down menu, select Grid to display the grid receptor details work area (Figure 24). 3. Enter the appropriate data in the required fields. – The X Distance and Y Distance will automatically display non-zero distances based on the defined count and spacing. – The Latitude and Longitude are set to the spaceport origin by default. Use one of the fol- lowing methods (depicted in Figure 25) to update the grid location: � Method 1: a. In the Location Info section, change the Latitude and Longitude to the location of the lower left corner of the grid. b. Leave the Grid Origin Info set to 0. � Method 2: a. Confirm that the Location Info represents the desired spaceport location (i.e., space- port origin). b. In the Grid Origin Info section, enter the location of the south-west corner of the grid as an offset from the spaceport origin by specifying the X offset and Y offset parameters. 4. Click Save to apply changes or Cancel to discard changes. Figure 24. Receptors tab – grid receptor details.

program Operation 37 To edit a grid-type receptor: 1. Select the desired receptor from the Table of Receptors and click Edit in the Actions ribbon group. 2. Edit the desired fields. 3. Click Save to apply changes or Cancel to discard changes. Elevation MSL (ft): This elevation corresponds to the elevation of the area, for example, the elevation of the spaceport. If the receptors are at a different elevation than the spaceport, the appropriate elevation should be used. 7.6.3 Delete Receptor To delete an existing receptor: 1. Select the desired receptor from the Table of Receptors. 2. From the Actions ribbon group, click Delete. Receptors that are assigned to a metric result cannot be deleted. 7.7 Operations Tab The Operations tab supports managing spacecraft operations. To view operations in the cur- rent study, click the Operations tab. There are three operation types: launch, landing, and static. Operations can be created, copied, edited, and deleted; however, operations that are assigned to a scenario cannot be deleted. Use the buttons in the Actions ribbon group to create, copy, edit, or delete spacecraft operations. • Click New to enable the Operation Details work area (Figure 26 and Figure 27). • Click Copy or Edit to display the Operation Details work area for the currently selected opera- tion. Each field will display the values from the original operation. • Click Delete to delete the currently selected operation. 7.7.1 Create Spacecraft Operation To create a spacecraft operation: 1. Click on the Operations tab and click New, or select an existing operation from the Table of Operations and click Copy in the Actions ribbon group to create a new operation from an existing operation. Figure 25. Depiction of methods to update the grid location.

Figure 26. Operations tab – launch details. Figure 27. Operations tab – static fire details.

program Operation 39 2. From the Operation Type drop-down menu, select an operation type. 3. From the Vehicle drop-down menu, select the desired spacecraft. – The vehicle list includes spacecraft in the RUMBLE database and user-defined spacecraft. � Click Details to view the parameters of a specific vehicle. Data was obtained from the FAA AST STAR Database unless otherwise noted. An asterisk indicates the parameter is required for operating RUMBLE (see Section 12.7.11 for a description of the spacecraft database fields). – Select Browse to import a partial RSIF file that contains user-defined fleet data (see Sec- tion 12.7.11 for a description of the RSIF for user-defined fleet data). � The Imported user-defined spacecraft will be available within the list for future operations. 4. Enter the desired annual operation counts. – To enable the calculation of the DNL and CNEL metrics, the annual operation counts are defined according to two (day and night) or three (day, evening, and night) daily periods. – If CNEL is calculated for operations defined according to two daily periods, zero evening operations are assumed. 5. Choose flight trajectory for launch/landing operations or provide static details. – For launch/landing operation: Select Browse to import a partial RSIF file that contains user- defined trajectory data (see Section 12.5.27 for a description of the RSIF for user-defined trajectory data). � The Imported user-defined trajectory will be available within the list for future operations. – For static operation: Enter the orientation, latitude, longitude, height, heading, and duration. � The heading is disabled when the vertical orientation option is chosen. 6. Click Save to apply changes or Cancel to discard changes. To edit a spacecraft operation: 1. Select the desired operation from the Table of Operations and click Edit in the Actions ribbon group. 2. Edit the desired fields. 3. Click Save to apply changes or Cancel to discard changes. 7.7.2 Delete Spacecraft Operation Click Delete to delete the currently selected operation. Operations that are assigned to a scenario cannot be deleted. 7.8 Scenarios Tab What is a scenario? In RUMBLE, a scenario is a hierarchical grouping of operations associated with the fol- lowing parameters: time period to be analyzed, operations included in the time period, and weighted groupings of the included operations. Creating a scenario provides a convenient way to adjust contributions of individual operation groups by scaling operations up or down using weightings. To view scenarios in the current study, click the Scenarios tab. Scenarios can be created, copied, and deleted; however, operations assigned to a metric result cannot be deleted.

40 User Guides for Noise Modeling of Commercial Space Operations—rUMBLe and pCBoom Use the buttons in the Actions ribbon group to create, copy, or delete scenarios. • Click New to enable the Scenario Details work area. • Click Copy to display the Scenario Details work area for the currently selected scenario. • Click Delete to delete the currently selected scenario. Editing an existing scenario is supported only through the Copy feature to create a new scenario based on an existing one and to edit the parameters. Each step will display the selections of the existing scenario. 7.8.1 Create Scenario To complete the Create Scenario workflow, the study must already contain spacecraft operations. To access the Scenario Details work area: Click on the Scenarios tab and click New. Step 1: Assign Existing Operation Groups The first step of the Create Scenario workflow is organized into two areas: 1. Select options at the top half of the details work area, and 2. Assign existing operation groups at the bottom of the details work area. Select Option(s) First, select at least one option from the list of checkboxes: 1. Assign existing operation group(s) – check this option to enable the bottom half of the details work area – Existing Operation Groups area, and 2. Add new spacecraft operation group(s). Assign Existing Operation Group(s) Existing operation groups are assigned in the current step (Figure 28). A list of existing operation group(s) is displayed on the left, and a list of operation groups assigned to the annualization is displayed on the right. To assign an existing operation group: 1. Select the desired operation group(s) from the Available operation groups list and click the Add Arrow. 2. To remove existing group(s) from the Assigned operation groups list, click the Remove Arrow. 3. When finished with this step, click Next. Existing operation groups cannot be edited. Operations cannot be assigned or removed from these groups and they cannot be renamed. Step 2: Create Spacecraft Operation Groups In this step, spacecraft operations can be organized into groups and assigned to the scenario. A list of available spacecraft operations is displayed on the left, and a list of operation groups assigned to the scenario is displayed on the right (Figure 29). To create a new spacecraft operation group: 1. Enter a name in the Add New Group field and click Add. 2. The new group is displayed in the Assigned operation groups list and automatically selected. 3. From the Available operations list on the left side of the details work area, select the desired operation(s) by clicking on the appropriate row(s). To select multiple rows, hold the control or shift key on the keyboard while clicking rows.

Figure 28. Scenarios tab – assign existing operation group(s). Figure 29. Scenarios tab – add new operation group(s).

42 User Guides for Noise Modeling of Commercial Space Operations—rUMBLe and pCBoom 4. Click the Add Arrow to add the selected operation(s) to the selected operation group in the Assigned operation groups list. The selected operations are then removed from the Available operations list. 5. To remove operations from an operation group, select the desired operation(s) and click the Remove Arrow to add the selected operation(s) back to the Available operations list. Although operation groups cannot be deleted, groups with zero assigned operations will automatically be removed. When finished grouping operations, click Next. Each operation group must have a unique name. Operations can be assigned and removed from new operation groups. Step 3: Build Scenario The scenario tab allows for user-defined weighting of noise results. A scenario weighting hierarchy can be created in this step for the operation groups defined in the previous steps (Figure 30). By default, the scaling factor for all scenario groups is 1. This represents the unit weight- ing (no change). Change the scaling factor for the scenario and its operation groups as desired. Figure 30. Scenarios tab – assign weighting.

program Operation 43 7.8.2 Copy Scenario The Copy option allows users to create a new scenario based on an existing scenario. To copy a scenario: 1. Click on the Scenarios tab. 2. In the Table of Scenarios, select a desired scenario to copy. 3. Click Copy to enable the Scenario Details work area. 4. Each step will display the values from the original scenario. 7.8.3 Delete Scenario Click Delete to delete the currently selected scenario. In order to delete a scenario, first delete any metric results that use the scenario. Scenarios that are assigned to a metric result cannot be deleted. Deleting a scenario does not delete its operation groups. Operation groups, once created, cannot be deleted. 7.9 Metric Results Tab Each metric result is representative of a metric, scenario (which includes operations), receptor set, and atmospheric profile combination. Metric results are listed in the Metric Results Table. The metrics results tab (Figure 31) allows for running metric results (Section 7.9.3), deleting metric results (Section 7.9.4), exporting metric results (Section 7.9.5), and viewing contours and receptors (Section 7.9.6). 7.9.1 Define New Metric Result To complete the Define Metric Results workflow, the study must already contain scenario(s) (which includes operations) and receptor(s). To define a metric result: 1. Click on the Metric Results tab and click Define, or select an existing metric result from the Metric Results Table and click Copy in the Actions ribbon group to create a new metric result from an existing metric result. 2. From the Metric drop-down menu, select the desired metric. – Available metrics include: DNL, SEL, LAMAX, LMAX, and CNEL. 3. From the Scenario drop-down menu, select the desired scenario. 4. From the Receptor(s) drop-down menu, select the desired receptor(s) (point or grid). 5. From the Atmospheric Profile drop-down menu, select the desired atmospheric profile. – Available atmospheric profiles include: U.S. Standard Atmosphere. � Sources: 0 – 95,000 ft: U.S. Standard Atmosphere (1976), 100,000 – 295,000 ft: NASA Technical Memo, and 300,000 – 350,000 ft: Handbook of Astronautical Engineering (McGraw-Hill 1961). – Select Browse to import a partial RSIF file that contains user-defined atmospheric profile data (see Section 12.5.4 for a description of the RSIF for user-defined atmospheric profile data). � The imported user-defined atmospheric profile will be available within the list for future metric results. 6. Click Save to apply changes or Cancel to discard changes.

44 User Guides for Noise Modeling of Commercial Space Operations—rUMBLe and pCBoom 7.9.2 Copy Metric Results The Copy option allows users to create a new metric result based on an existing metric result. To copy a metric result: 1. Click on the Metric Results tab. 2. In the Metric Results Table, select a desired metric result to copy. 3. Click Copy to enable the Metric Results Details work area. 4. Each field will display the values from the original metric result. 7.9.3 Run Metric Results Metric result definitions that have been defined can be processed to generate the specified results. Metric result definitions can be run individually or in groups from the Metric Results tab. To process metric result definitions listed in the Metric Results Table: 1. Select desired metric result(s) and click Run from the Actions ribbon group. – Use the shift key to select multiple metric results. 2. Once the run is complete, the State column will display a check icon. 7.9.4 Delete Metric Results Click Delete to delete the currently selected metric result. Figure 31. Metric results tab.

program Operation 45 7.9.5 Export Metric Results To enable the Export button, select a completed noise metric result. This button allows the user to export the selected noise metric result in a Noise Model ASCII Grid Format (NMAGF) file. To export noise metric result: 1. In the Metric Results Table, select a completed noise metric result. 2. In the Metric Results Actions group in the ribbon, click the Export button. 3. Accept the default file name or enter a new file name and click Save. 4. A grid file is saved to the selected location. The default export location is C:\RUMBLE\DATA\[Study Folder]. The default filename is based on the scenario name, receptor set name, and metric. 7.9.6 View Contours and Receptors Data can be visualized on a map by generating contour or receptor layers. The View ribbon group in the Metric Results tab supports generating two types of layers: contour and receptor(s). View Noise Contour Layer 1. In the Metric Results Table, select a desired noise metric result that has been processed with a grid-type receptor. 2. From the View ribbon group, click the Contour button. 3. The Viewing Options work area is displayed. 4. Accept the default minimum, maximum, and increment values under Contour Settings or enter new values. 5. Select the desired GeoTIFF map under Basemap Layer or leave the drop-down field empty. A GeoTIFF is a public domain metadata standard which allows georeferencing information to be embedded within a TIFF file. – Select Browse to import a GeoTIFF basemap layer. – The imported GeoTIFF basemap layers will be available for future viewing actions. 6. Click View. 7. The contour layer is displayed on a map (Figure 32). To improve the smoothness of the contours, increase the grid point density and/or the spatial resolution of the trajectory points. View Receptor Layer 1. In the Metric Results Table, select a desired metric result. 2. From the View ribbon group, click the Receptor button. 3. The Viewing Options work area is displayed. 4. Select the desired GeoTIFF map under Basemap Layer or leave the drop-down field empty. a. Select Browse to import a GeoTIFF basemap layer. b. The imported GeoTIFF basemap layers will be available for future viewing actions. 5. Click View. 6. The receptor layer is displayed on a map (Figure 33).

46 User Guides for Noise Modeling of Commercial Space Operations—rUMBLe and pCBoom Figure 32. Metric results tab – view contours.

program Operation 47 Figure 33. Metric results tab – view receptors.

48 8.1 RUMBLE Grid File Noise metric results are exported from RUMBLE in the form of Noise Model Grid Format (NMGF) files. NMGF is a standard data file format that contains predicted noise levels at a set of locations surrounding an installation (Figure 34). A number of standard noise models use NMGF to export results, including the FAA’s AEDT and the U.S. Air Force’s Noisemap. 8.2 RUMBLE Log File System status and information is written to the RUMBLE.log file in the C:\RUMBLE\Logs folder. Logged messages are timestamped and contain information, warnings, and errors. In the event of a fatal error that causes the application to stall or shut down, the RUMBLE.log file may be consulted to understand the case (Figure 35). C h a p t e r 8 Output File Descriptions

Output File Descriptions 49 Figure 34. Sample RUMBLE NMGF file. Figure 35. Sample RUMBLE log file.

50 RUMBLE provides error messages and warnings to inform users of the use of non-standard input or actions which may affect the integrity of the program. RUMBLE provides warning mes- sages to help ensure input data values and formats conform to the model’s requirements. If an invalid input is performed in the GUI, then the entry is outlined in red and a context sensitive message is displayed to aid the user in submitting a valid entry. The context sensitive messages may indicate the input data is outside the range of expected values, as shown in Figure 36, or that the format of the input data is incorrect (Figure 37). Additionally, RUMBLE will display an error message if a user attempts to overwrite default fleet database values. For example, as shown in Figure 38, if the user attempts to input a user- defined spacecraft name which matches an existing spacecraft name defined in the RUMBLE fleet database, then an error will display. To resolve this error, the user should update the space- craft name (identifier) to one that is unique to those used in the RUMBLE fleet database. Fatal situations are accompanied by a chime sound and require cessation of program execu- tion. Runtime error messages are created and saved in the output log file (see Section 8.2) if fatal situations are encountered. These error messages document the specific subroutine(s) that generated the error. C h a p t e r 9 Error and Warning Messages

Figure 36. Sample warning message – invalid value. Figure 37. Sample warning message – invalid format.

52 User Guides for Noise Modeling of Commercial Space Operations—rUMBLe and pCBoom Figure 38. Sample error message – cannot overwrite default spacecraft.

53 10.1 Sample Cases Two sample study files are included in RUMBLE 2.0: the Horizontal Launch Sample Case and the Vertical Launch Sample Case. The study files can be accessed via the list of existing studies displayed within the open panel in the RUMBLE GUI’s study tab (Figure 39). Associ- ated sample case data files are described in Section 10.1.1 and the step-by-step workflow to create the horizontal launch sample case is described via the Create New Study Exercise in Section 10.2. 10.1.1 Sample RSIF A set of sample partial RSIF is located in the C:\Program Files\BRRC\RUMBLE\Examples directory. These files include: • PartialRSIF_SampleHorizontalVehicle.xml – contains Notional Suborbital Spacecraft 1 data for a sample horizontally launched spacecraft. • PartialRSIF_SampleHorizontalLaunch.xml – contains Notional Suborbital Trajectory 1 data for a sample horizontal launch. • PartialRSIF_SampleVerticalLaunch.xml – contains Notional Suborbital Trajectory 2 data for a sample vertical launch. • PartialRSIF_USStandardAtmosphere.xml – contains U.S. Standard Atmosphere data. Although these sample cases are provided in their entirety, the step-by-step workflow to create the horizontal launch sample case is provided in Section 10.2. These examples should be used as an aid for understanding the RSIF format and not as a data reference. 10.1.2 Horizontal Launch Sample Case The horizontal launch sample case is an example noise study that is based on horizontal launch operations from the NASA Shuttle Landing Facility, but the operations do not represent real operations (Figure 40). The study content of this sample case is described in Table 5. 10.1.3 Vertical Launch Sample Case The vertical launch sample case is an example noise study based on vertical launch operations from the Kennedy Space Center’s Launch Complex 39, but the operations do not represent real operations (Figure 41). The study content of this sample case is described in Table 6. C h a p t e r 1 0 Instructional Resources

54 User Guides for Noise Modeling of Commercial Space Operations—rUMBLe and pCBoom Figure 39. Sample cases displayed in the list of existing studies.

Instructional resources 55 Content Name Description Spaceport NASA Shuttle Landing Facility Origin: 28.614894°N, 80.694373°W, 0 ft MSL Receptors SLF 81x81 Grid X Distance: 4.0 nmi (X Count: 81, X Spacing: 0.05) Y Distance: 4.0 nmi (Y Count: 81, Y Spacing: 0.05) Origin: Spaceport Origin SW Corner: -2.0 nmi X Offset and -2.0 nmi Y Offset from Origin Operations SLF Launch Spacecraft: Notional Suborbital Spacecraft 1* Trajectory: Notional Suborbital Trajectory 1* Number of Daily Periods: 2 Annual Operations: 1,560 (30 per week) 75% Daytime, 25% Nighttime Scenarios 2017 Operations Contains one operation group, SLF Launch Op Group, which includes the SLF Launch operations Metric Results - Metrics: DNL (Figure 40), SEL, LAMAX, and LMAX Scenario: 2017 Operations Receptors: SLF 81x81 Grid Atmospheric Profile: U.S. Standard Atmosphere* * See sample RSIF in Section 10.1.1 Table 5. Horizontal launch sample case content. Figure 40. DNL metric result contours of the horizontal launch sample case.

56 User Guides for Noise Modeling of Commercial Space Operations—rUMBLe and pCBoom Content Name Description Spaceport Launch Complex 39 Origin: 28.627105°N, 80.620880°W, 0 ft MSL Receptors LC-39 101x101 Grid X Distance: 10 nmi (X Count: 101, X Spacing: 0.1) Y Distance: 10 nmi (Y Count: 101, Y Spacing: 0.1) Origin: Spaceport Origin SW Corner: -5.0 nmi X Offset and -5.0 nmi Y Offset from Origin Operations SLF Launch Spacecraft: Delta IV Medium Trajectory: Notional Suborbital Trajectory 2* Number of Daily Periods: 2 Annual Operations: 12 (1 per month) 66.7% Daytime, 33.3% Nighttime Scenarios 2017 Operations Contains one operation group, SLF Launch Op Group, which includes the SLF Launch operations. Metric Results - Metrics: DNL (Figure 41), SEL, LAMAX, and LMAX Scenario: 2017 Operations Receptors: LC-39 101x101 Grid Atmospheric Profile: U.S. Standard Atmosphere* * See sample RSIF in Section 10.1.1 Table 6. Vertical launch sample case content. Figure 41. DNL metric result contours of the vertical launch sample case.

Instructional resources 57 10.2 Create New Study Exercise The goal of the Create New Study Exercise is to learn how to create basic study elements in a new study, use those elements to define metric results, and explore the results. The study ele- ments created in this exercise are intended to demonstrate the mechanics of creating a study structure in RUMBLE 2.0 and do not represent a real analysis. Prerequisites This exercise assumes no prior usage of RUMBLE and is designed to provide the user with basic knowledge of creating a new study and defining a metric result in RUMBLE 2.0. What is a Metric Result? In RUMBLE 2.0, a metric result represents the highest-level organization of data needed to answer questions of interest about the environmental consequences of commercial space activi- ties. Each metric result consists of a metric, receptor set, atmospheric profile, operations, and scenario combination. Major Steps The major steps in this exercise are as follows: • Create a new study, • Add a spaceport, • Create a grid receptor, • Create spacecraft operations, • Create a scenario, • Define metric results, • Run metric results, • View metric results, • Export metric results. 10.2.1 Create a New Study Follow the steps below to create a new study (Figure 42): 1. Open the RUMBLE application. 2. Click on the Study tab then click New to display the Create New Study work area. 3. In the Study Name field, enter “My KSC Study.” 4. In the Study Description, enter “My new Kennedy Space Center Study.” 5. Click Create. The Spaceport tab will open when the new study has been created, and the study name will appear in the top right corner of the application. 10.2.2 Add a Spaceport Follow the steps below to add a spaceport to the study (Figure 43): 1. Click on the Spaceport tab. 2. In the Actions ribbon group, click New and enter the following data: a. In the Name field, enter “NASA Shuttle Landing Facility.” b. In the Latitude field, enter 28.614894.

Figure 42. Create new study work area. Figure 43. Spaceport work area.

Instructional resources 59 c. In the Longitude field, enter −80.694373. d. In the Elevation field, enter 0. 3. Click Save to save the new spaceport. 10.2.3 Create a Grid Receptor Receptors define the locations where noise is calculated. Follow the steps below to define a grid receptor (Figure 44): 1. Click on the Receptors tab. 2. In the Actions ribbon group, click New and enter the following data: a. In the Name field, enter “SLF 81 × 81 Grid.” b. From the Type drop-down menu, select Grid. c. In the X Count field, enter 81. d. In the Y Count field, enter 81. e. In the X Spacing and Y Spacing fields, enter 0.05. f. Confirm that the Location Info represents the spaceport origin. g. In the Grid Origin Info section, enter the location of the south-west corner of the grid as an offset from the spaceport origin by specifying the X offset to be −2.0 and the Y offset to be −2.0. 3. Click Save to create the new receptor. The receptor is created and listed in the Table of Receptors. Figure 44. Create grid receptor work area.

60 User Guides for Noise Modeling of Commercial Space Operations—rUMBLe and pCBoom 10.2.4 Create Spacecraft Operations Follow the steps below to create a launch operation and static fire operation (Figure 45): Launch Operation 1. Click on the Operations tab. 2. In the Actions ribbon group, click New to open the Operation Details work area. 3. From the Operation Type drop-down menu, select Launch. 4. In the User ID field, enter “SLF Launch.” 5. Choose Vehicle: a. From the Choose Vehicle drop-down menu, select Browse to import the PartialRSIF_ SampleHorizontalVehicle.xml file. 6. Define operations: a. Select the “two daily periods” radio button. b. In the Daytime field, enter 1170. c. In the Nighttime field, enter 390. 7. Choose trajectory: a. From the Choose Trajectory drop-down menu, select Browse to import the PartialRSIF_ SampleHorizontalLaunch.xml file. 8. Click Save to create the new operation. The launch operation is created and listed in the Table of Operations. Figure 45. Launch operation details work area.

Instructional resources 61 Static Fire Operation 1. In the Actions ribbon group, click New to open the Operation Details work area (Figure 46). 2. From the Operation Type drop-down menu, select Static Fire. 3. In the User ID field, enter “SLF Static Fire.” 4. Choose Vehicle: a. From the Choose Vehicle drop-down menu, select a spacecraft or Browse to import a user- defined fleet RSIF file. 5. Define operations: a. Check the Two Daily Periods. b. In the Daytime field, enter 12. c. In the Nighttime field, enter 0. 6. Enter static fire data: a. From the Orientation drop-down menu, select Horizontal. b. In the Latitude field, enter 28.632758. c. In the Longitude field, enter -80.706064. d. In the Height field, enter 7. e. In the Heading field, enter 150. f. In the Duration field, enter 15. 7. Click Save to create the new operation. The static fire operation is created and listed in the Table of Operations. Figure 46. Static fire operation details work area.

62 User Guides for Noise Modeling of Commercial Space Operations—rUMBLe and pCBoom 10.2.5 Create a Scenario In RUMBLE, a scenario is a weighted grouping of operations. Scenarios provide a conve- nient way to evaluate the noise with different weightings of individual operation groups. In this example, the operations will be weighted equally, and operation groups will be created for demonstration purposes. Follow the steps to build a scenario consisting of the operations created in previous steps (Figure 47): 1. Click on the Scenarios tab. 2. In the Actions ribbon group, click New to open the Scenario Details work area. 3. Assign Existing Operation Groups: a. In the Name field, enter “2017 Operations.” b. Check the Add new spacecraft operation group(s). c. Click Next. 4. Create Spacecraft Operation Groups (Figure 48): a. In the Add New Group field, enter “SLF Launch Op Group” and click Add. b. Select SLF Launch Op Group from the Operation Groups list and select SLF Launch from the Available Operations list, and click the forward arrows (>>) button to add the selected operation to the selected group. Figure 47. Scenario details work area – existing operation groups step.

Instructional resources 63 c. In the Add New Group field, enter “SLF Static Fire Op Group” and click Add. d. Select SLF Static Fire Op Group from the Operation Groups list and select SLF Static Fire from the Available Operations list, and click the forward arrows (>>) button to add the selected operation to the selected group. e. Click Next. 5. Assign weightings (Figure 49): a. Weightings can be applied to the scenario and/or its operation groups. For this example, leave the weighting as “1” for the scenario and both groups. b. Click Create. The new scenario is listed in the Table of Scenarios. 10.2.6 Define Metric Results Follow the instructions to define noise (DNL) metric results (Figure 50): 1. Click on the Metric Results tab. 2. In the Metric Results Actions ribbon group, click Define and select the following options: a. From the Metric drop-down menu, select DNL, b. From the Scenario drop-down menu, select 2017 Operations, Figure 48. Scenario details work area – new operation groups step.

Figure 49. Scenario details work area – assign weighting step. Figure 50. Metric result work area.

Instructional resources 65 c. From the Receptor(s) drop-down menu, select SLF 51x81, d. From the Atmospheric Profile drop-down menu, select U.S. Standard Atmosphere. 3. Click Save. The new metric result is listed in the Table of Metric Results. 10.2.7 Run Metric Results Follow the instructions to run the metric result definitions: 1. In the table of metric results, select the DNL metric result. 2. From the Metric Result Actions ribbon group, click Run to run the selected metric result definition. When the metric results have finished running, the State column in the Metric Results pane will display a check icon. 10.2.8 View Metric Results Follow the instructions below to view the metric result definitions: 1. In the table of metric results, select the DNL metric result. 2. From the View ribbon group, click Contour. 3. In the Viewing Options work area, click View to accept the default Contour Settings. Upload a GeoTIFF map if desired. 4. The noise contour layer will then be displayed on the associated map (Figure 51). 10.2.9 Export Metric Results Follow the instructions to run the metric result definitions: 1. In the table of metric results, select the DNL metric result. 2. From the Metric Result Actions ribbon group, click Export and click Save to accept the default file path and name.

66 User Guides for Noise Modeling of Commercial Space Operations—rUMBLe and pCBoom Figure 51. View contours figure window.

67 The FAA Office of Environment and Energy (AEE) has approved models for detailed noise analysis. Prior written approval from AEE is required to use another equivalent methodol- ogy or computer model. Modification to standard or default data also requires prior written approval from AEE. As of May 2017, RUMBLE has not been designated as an approved model by AEE, and thus written approval from AEE is required when using RUMBLE. The most current version of FAA’s 1050 desk reference should be consulted to confirm the list of FAA- approved models for detailed noise analysis. Additionally, review and approval of the use of non-default modeling data may be required, such as user-defined vehicles, trajectories, and atmospheric profiles. The approval of particular non-default methods or data in past studies does not guarantee approval in a future study. Each modeling situation is unique and must be evaluated on a case-by-case basis. This section provides guidance for developing an official approval process to conduct reviews of modeling methodology and input data used in the RUMBLE model. The guidance also addresses the essential components of the review package that project consultants must submit to AST for review. The review process is a quality control check on the modeling inputs and methodologies used for environmental assessment of space operations. The guidance presented here is similar to the review and approval process that FAA uses for commercial airport noise studies [14], but it is tailored specifically for the RUMBLE model. Note that the information presented here is not the official AEE internal review and approval process. Section 11.1 describes procedures for review of non-default methods and data, Section 11.2 provides a list of common data and AEE review requirements, and Section 11.3 provides guid- ance regarding information to submit for AEE review of non-default methods and data. 11.1 Procedures for Review of Non-Default Methods and Data This is a description of the steps for review and approval to use non-default methods and data. 1. Initial communication between the project consultant (PC), in coordination with the project sponsor (PS), and FAA project manager (PM) in the region, district office, or service center to determine if the proposed non-default methods/data require formal review by AEE. As part of this discussion, the PC should be prepared to explain the reason for the use of non-default methods/data to the PM and AEE. 2. The PC must then submit a review package to AST, in coordination with the PS and PM. Information in the review package must be complete and presented in a clear manner. The information and the review process must be well documented and may be included as an C h a p t e r 1 1 Approval Process

68 User Guides for Noise Modeling of Commercial Space Operations—rUMBLe and pCBoom appendix to an EA, EIS, or study report as part of the NEPA documentation. The format of the review package is described in Section 11.3. 3. After receiving the review package and checking it for completeness, AST-100 will forward the review package to AEE. 4. Provided the review package is complete and contains all essential information (see Sec- tion 11.3), AEE will begin their review of the package. During the review period, AEE may discuss the review package, gather more facts, and clarify the technical issues directly with the PC. Unless policy implications or substantive issues arise, AEE does not need to coordi- nate with other FAA headquarters offices or the PM during this period, other than providing emails on the status of its review, as appropriate. 5. AEE will prepare a letter addressed to the PM providing the decision on the review package. 6. AEE will forward the decision letter to the PM (with a cc: AST-100) by email. The PM should convey the decision to the PS and PC. 7. If AEE approves the use of non-default methods or data, the following must be included in the FAA’s project file: (1) a copy of AEE’s approval letter and (2) a description of the approved non-default method(s) and/or data. Questions about the above procedures should be addressed to AST-100, whether the ques- tions pertain to the process or as applied to a specific project. Early and clear communications by the PC will reduce the chance of delay caused by an incomplete review package. 11.2 List of Common Methods/Data and AEE Review Requirements Sections 11.2.1 and 11.2.2 describe common data used to model commercial space operations. For information on how to request changes to methods or data not listed in either section, please contact AEE. 11.2.1 Analysis Methods/Data that Do Not Require AEE Review and Approval The following analysis methods or data are recommended to not require AEE review and approval: • Default methods and data that are provided in RUMBLE. • Trajectory information that is provided by a spacecraft manufacturer. Data may require custom editing by the user to smooth out spurious or irregular data. Therefore, it is recom- mended that users compare any modified trajectory data with the original data to make sure that the modified version retains the important features of the original trajectory. • Use of the U.S. Standard Atmosphere 1976 model [15], with altitude extensions, or any atmo- sphere model native to RUMBLE would not require review and approval. • Use of supplemental (i.e., other than DNL) noise metrics that are native to RUMBLE, pro- vided that the study only reports the resulting noise levels and does not draw any specific conclusions about impacts or suggest that the impacts are significant. Conversely, the discus- sion must include effective language about existing scientific uncertainties and the lack of FAA assessment methodology, impact criteria, and policy guidance in the area examined by supplemental metrics. Although the above methods/data do not require approval, they should be well documented in the NEPA documentation.

approval process 69 11.2.2 Analysis Methods/Data that Do Require AEE Review and Approval The following analysis methods or data are recommended to require AEE review and approval: • Sensitivity – Any supplemental noise analysis that involves impacts that are likely to be highly contro- versial on environmental grounds. – Any supplemental noise analysis that involves Section 4(f) properties (including, but not limited to, noise-sensitive areas within national parks; national wildlife and waterfowl refuges; and historic sites including traditional cultural properties) where a quiet setting is a generally recognized purpose and attribute. • Supplemental Noise Metrics – Noise metrics not native to RUMBLE. – Interpretation of impacts or significance for supplemental noise metrics listed in the 1050.1F Desk Reference. – Supplemental noise analysis focused on one or more secondary or indirect effects (e.g., sleep disturbance, health effects, classroom learning, low frequency impacts), regardless of the supplemental metric(s) used. • Spacecraft and Trajectories – Spacecraft not native to RUMBLE. – User-defined trajectories not provided by a spacecraft manufacturer. • Non-default weather data used for the analysis of noise. • Alternative models and methodologies not native to RUMBLE. 11.3 Guidance Regarding a Request to Use Non-Default Methods/Data The following information is always required for any request to use non-default methods or data: 1. Background. Briefly describe the project, including location, for which non-default methods or data are needed. State the type of analysis (e.g., Environmental Assessment, Environ- mental Impact Statement, or other type of NEPA analysis). Include any additional relevant information. 2. Statement of Benefit. Briefly describe why the non-default methods or data are needed for this project, how the non-default methods or data are more appropriate, and why the default method or data are not sufficient. RUMBLE allows for the creation of user-defined spacecraft vehicles, trajectories, and atmo- spheric data that differ from default data provided in RUMBLE. If analysts use non-default user- defined spacecraft, trajectories, and/or atmospheric profiles that are not native to RUMBLE for noise analyses, AEE approval is required (see Section 11.2.2). Additional information to include in a submittal package requesting AEE approval for use of user-defined spacecraft, trajectories, or atmospheric profiles are: 1. Spacecraft Information. (If the spacecraft includes more than one engine definition, specify the core/booster engine configuration used.) – Airframe � Model and Manufacture

70 User Guides for Noise Modeling of Commercial Space Operations—rUMBLe and pCBoom – Engine � Model and Manufacture � Number of Engines � Number of Nozzles per Engine � Engine Nozzle Exit Diameter (feet) � Engine Nozzle Exit Velocity (feet/second) � Engine Thrust (lbf) � Source Directivity Index 2. Trajectory Information – Time – Latitude and Longitude – Altitude (feet MSL) – Speed (feet/second) – Flight Path Heading (degrees) – Flight Path Angle (degrees) – Vehicle Heading (degrees) – Vehicle Pitch (degrees) – Thrust* (lbf) 3. Atmospheric Profile Information – Altitude (feet MSL) – Temperature (degrees Fahrenheit) – Pressure (mmHg) – Humidity (%) – Sounds Speed (feet/second) *optional parameter

71 12.1 Introduction RSIF provides a standard file format to allow for the import of data into a RUMBLE study. A RSIF can be used to create new RUMBLE studies and to update existing studies. This chapter provides a description of the RSIF format for the RSIF schema version 2.0 which was based on AEDT’s stan- dard input files (ASIF) schema version 1.2.11. It also provides an overview of RSIF usage and anno- tated sample studies. The guide is intended for analysts and programmers who wish to create RSIFs. 12.1.1 Overview of the RSIF Format The RSIF format allows users to import a complete RUMBLE study. Users can also use a par- tial RSIF file to import fleet, trajectory, or atmospheric profile data. RSIF is based on the XML file format. XML is a text-based file format that is readable by both humans and computers. Data values are tagged with elements and organized in a hierarchi- cal manner such that the elements can contain other elements or data. XML elements can also have attributes which provide metadata that affect how the RSIF importer processes the data in the XML file. This document assumes users have basic familiarity with the XML file format. For additional information about XML, see http://xmlfiles.com/xml/. A RSIF can be created and edited in a standard XML editor. The XML Notepad and Notepad++ are XML editors that can be downloaded for free online and may also be used to validate RSIF against the XML Schema Definition (XSD). 12.1.2 RSIF Schema Documentation and Sample RSIFs The C:\Program Files\BRRC\RUMBLE\application\Examples directory contains the following: • RSIF schema (.xsd) files. • Sample RSIF files. 12.2 XML Hierarchy There are two types of RSIF import files: a full-study import and a partial-study import. The following sections describe each type of import file. 12.2.1 Create New Study with RSIF RUMBLE supports the creation of new studies via RSIF. For a full-study import, the content attribute of the <RsifXML> element must be set to “study.” The RSIF schema describes the C h a p t e r 1 2 RSIF Reference Guide

72 User Guides for Noise Modeling of Commercial Space Operations—rUMBLe and pCBoom hierarchical relationship of structural XML elements within the RSIF import file; some ele- ments are optional. 12.2.2 Partial RSIF Import Partial RSIF is used to import specific pieces of data into an existing RUMBLE study. A partial RSIF file is organized similarly to a full RSIF, except that it contains a single type of data – the content attribute of the <RsifXML> element must specify the data type. There are three data types that can compose a partial ASIF: fleet, trajectorySet, and atmosphericProfile. The format for a partial RSIF is outlined below. The header is the same as a full RSIF, except that the content attribute is not “study.” Instead, the content attribute should specify the data element that appears in the file. <?xml version=”2.0” encoding=”UTF-8”?> <RsifXml xmlns:xsi=”http://www.w3.org/2001/XMLSchema-instance” version=”2.0” content=”ENTER_CONTENT_TYPE_HERE”> <!-- The content code block follows here: --> <*content type here*> . . . </*end content type*> </RsifXml> 12.3 RSIF Examples This section provides simple steps to assist in the creation of RSIFs for possible studies. 12.3.1 Create a Simple Study Follow the steps below to develop an RSIF for a simple RUMBLE study: 1. Create an empty study file, 2. Populate the spaceport section, 3. Create a receptor set, 4. Create a scenario and case hierarchy, 5. Populate the scenario’s cases with tracks and air operations, 6. Create a scenario annualization tree. The hierarchy for a simple RUMBLE study is outlined below, resulting from the above steps. <?xml version=”1.0” encoding=”utf-8”?> <RsifXml xmlns:RsifXml=”RSIF.xsd” xmlns:xsi=”http://www.w3.org/2001/ XMLSchema-instance” content=”study” version=”1”> <study> <name>My KSC Study</name> <studyType>Noise</studyType> <description>My new Kennedy Space Center study</description> <spaceportLayout> . . . </spaceportLayout> <receptorSet> . . . </ receptorSet > <fleet> . . . </fleet > <scenario> <name>Baseline</name> <caseSet> . . . </caseSet> <annualization> . . . </annualization> </scenario> </study> </RsifXml>

rSIF reference Guide 73 12.4 Notation This section describes the notation used in the schema. Tables 7 and 8 describe the notation for XML tag types and the notation for the required number of elements. Some element descriptions include a Choice column. This column indicates the need to choose between one of the elements associated with the same choice letter. For example, refer- ring to the table in section latlonCoordGroup, choice “a” refers to a choice between the latitude and latitudeDMS elements, and choice “b” refers to the longitude and longitudeDMS elements. When creating a tag of type latlonCoordGroup, you can include one element from choice “a” and one element from choice “b.” Some ASIF elements contain attributes. For example, when specifying a thrust (associated with the trajectoryNode element), the optional coreIdentifier and boosterIdentifier attributes can be included. In the following example, the coreIdentifier attribute indicates that the core associated with the thrust of that node is Common Core Booster: <thrust coreIdentifier=”Common Core Booster”>410000</thrust> The following section describes attributes when they are defined for a particular element. The schema diagram (Table 9) illustrates the structure and contents of each XML element. It facili- tates understanding of the relationship between XML elements, and the rules and properties of each element. Some XML elements in RSIF must be in the order specified in the RSIF schema. Type Description integer, double The standard numeric types. string A string with up to N characters. - A complex type that contains other elements. Table 7. Notation for RSIF XML tag types. Num Description + 1 or more instances are required. * 0 or more instances are required, implying the element is optional if 0 elements are desired. ? 0 or 1 instance is required, again implying an optional element. Table 8. Notation for the required number of elements. Notation Icon Description Choice Indicator Only one of the elements contained in the selected group can be present. Sequence Indicator Child elements must appear in the specified sequence. Element Represented by a rectangle with solid or dotted border: Solid rectangle – required element Dotted rectangle – optional element Element with (+) Sign Indicates that the element has child element(s) and/or attribute(s). Element with Min and Max Bound Specifies the min/max number of times an element can occur in the parent element. Table 9. Notation for schema diagram.

74 User Guides for Noise Modeling of Commercial Space Operations—rUMBLe and pCBoom 12.5 Element Descriptions 12.5.1 annualization Contains annualizations. Structure (see Notation for information about reading this table). XML Tag Type Num Description name string255 1 Name of annualization annualizationGroup - 1 Contains one or more weighted annualization group cases. See annualizationGroup. Attributes: None. 12.5.2 annualizationCase Collection of study cases whose results are weighted in the scenario annualization rollup. Structure (see Notation for information about reading this table). XML Tag Type Num Description name string255 1 Description of the case. weight xs:double 1 Weight associated with the case. Attributes: None. 12.5.3 annualizationGroup Contains one or more weighted annualization cases. Structure (see Notation for information about reading this table). XML Tag Type Num Description weight xs:double 1 Weight associated with the annualization group. annualizationCase - * Collection of study cases whose results are weighted in the scenario annualization rollup. See annualizationCase. Attributes: None.

rSIF reference Guide 75 12.5.4 atmosphericProfile Contains one or more atmospheric profile descriptions. Structure (see Notation for information about reading this table). XML Tag Type Num Description name xs:double 1 Name of atmospheric profile. atmosphericProfileNodes - 1 A set of atmospheric profile nodes. See atmosphericProfileNodes. Attributes: None. 12.5.5 atmosphericProfileNode Structure (see Notation for information about reading this table). XML Tag Type Num Description altitude xs:double 1 Node altitude (ft). temperature xs:double 1 Node temperature (°F). pressure xs:double 1 Node atmospheric pressure (mm Hg). humidity xs:double 1 Node relative humidity (%). soundSpeed xs:double 1 Node sound speed (ft/sec). Attributes: None. 12.5.6 atmosphericProfileNodes A set of atmospheric profile nodes. Structure (see Notation for information about reading this table). XML Tag Type Num Description atmosphericProfileNodes - 1 An atmospheric profile node. See atmosphericProfileNode. Attributes: None.

76 User Guides for Noise Modeling of Commercial Space Operations—rUMBLe and pCBoom 12.5.7 case Describes general parameters for a case. Structure (see Notation for information about reading this table). XML Tag Type Num Choice Description name string255 1 a The case name (must be unique within the scenario). description string255 * The case description. staticFire - * b A spacecraft static fire operation. See staticFire. trajectoryOpSet - * b Lists trajectories and associated operations. See trajectoryOpSet. reference - 1 a Refers to a case by its scenario name and case name. Conditions required: the referenced case must have a unique name in the new scenario. See reference. Attributes: None. 12.5.8 caseSet Placeholder for one or more cases. Structure (see Notation for information about reading this table). XML Tag Type Num Description case - * Describes general parameters for a case. See case. Attributes: None.

rSIF reference Guide 77 12.5.9 centroid Describes the geometric center of a polygon. Structure (see Notation for information about reading this table). XML Tag Type Num Description stateFips xs:int 1 Optional census state identifier. countyFips xs:int 1 Optional census county identifier. blockId xs:int 1 Optional census BLOCK ID. bnaId string6 1 Optional census BNA ID. coord2DGroup - 1 Indicates how a two-dimensional group is specified. See coord2DGroup. elevation xs:double * The centroid’s elevation above MSL (ft). If not specified, RUMBLE will use elevation of spaceport. count xs:int 1 The population count of the centroid. Valid values: 0 to 999999. Attributes: None.

78 User Guides for Noise Modeling of Commercial Space Operations—rUMBLe and pCBoom 12.5.10 grid Describes a grid of points. Structure (see Notation for information about reading this table). XML Tag Type Num Description name string255 1 A string up to 255 characters long. coord2DGroup - 1 Indicates how a two-dimensional group is specified. See coord2DGroup. elevation xs:double * The centroid’s elevation above MSL (ft). If not specified, RUMBLE will use the elevation of the spaceport. width xs:double 1 Width of the grid (nmi). height xs:double 1 Height of the grid (nmi). numWidth xs:int 1 Number of points to spread across the width of the grid. The total number of points in the grid is numWidth x numHeight. Points will be located along width of grid using the formula: i x (width÷numWidth) where i is the index of the point (0 … numWidth–1). Valid values: 1 to 999. numHeight xs:int * Number of points to spread across the height of the grid. The total number of points in the grid is numWidth x numHeight. Points will be located along height of grid using the formula: i x (height÷numHeight) where i is the index of the point (0 … numHeight–1). Valid values: 1 to 999. widthOffset xs:double 1 Width offset from the spaceport origin to describe the location of the south-west corner of the grid. heightOffset xs:double 1 Height offset from the spaceport origin to describe the location of the south-west corner of the grid. Attributes: None.

rSIF reference Guide 79 12.5.11 operation Describes a spacecraft flight operation. Structure (see Notation for information about reading this table). XML Tag Type Num Description Id string16 1 User-specified identifier for the operation. spacecraftIdentifier spacecraftId 1 Spacecraft identifier. opType opType 1 Type of operation. numAnnualOperationsDay xs:double 1 Number of annual acoustic daytime operations comprising this operation, where daytime hours are: (07:00 am to 10:00 pm) OR (07:00 am to 07:00 pm) when evening operations are defined. numAnnualOperationsNight xs:double 1 Number of acoustic annual nighttime operations comprising this operation, where nighttime hours are: (10:00 pm to 07:00 am). numAnnualOperationsEvening xs:double * Number of annual acoustic evening operations comprising this operation, where evening hours are: (07:00 pm to 10:00 pm). Attributes: None. 12.5.12 operations Contains a list of spacecraft flight operations. Structure (see Notation for information about reading this table). XML Tag Type Num Description operation - * Describes a spacecraft flight operation. See operation. Attributes: None.

80 User Guides for Noise Modeling of Commercial Space Operations—rUMBLe and pCBoom 12.5.13 options Contains default option values applied to the study. Structure (see Notation for information about reading this table). XML Tag Type Num Description utmZoneDefault xs:int 1 Default UTM zone number. Default: –1. Attributes: None. 12.5.14 pointReceptor Element specification for a point receptor. Structure (see Notation for information about reading this table). XML Tag Type Num Description name string255 1 A string up to 255 characters long. coord2DGroup - 1 Indicates how a two-dimensional group is specified. See coord2DGroup. elevation xs:double * The point’s elevation above MSL (ft). If not specified, RUMBLE will use elevation of spaceport. Attributes: None.

rSIF reference Guide 81 12.5.15 polarGrid Describes a two-dimensional grid of individual receptors over an annular sector (polar) of the study area. Structure (see Notation for information about reading this table). XML Tag Type Num Choice Description name string255 1 A string up to 255 characters long. coord2DGroup - 1 a Indicates how a two-dimensional group is specified. See coord2DGroup. originSource originSourceType * a Origin source name for the polar grid (must match a unique name of a specific source reference). originName string40 * Refers to an existing spaceport. elevation xs:double * The centroid’s elevation above MSL (ft). If not specified, RUMBLE will use elevation of spaceport. ringStart xs:double * Initial radius of the first ring from the center point. Default: 1. rightSpacing xs:double * Spacing between rings starting from the first ring. Valid values: 0 to 1,000. Default: 1. ringCount xs:int * Total number of rings, including first ring. Valid values: 0 to 100. Default: 1. vectorStart xs:double * Angle of point along a ring. 0 = north. Valid values: 0 to 360 (degrees) Default: 0. vectorSpacing xs:double * Number of degrees between receptors. Valid values: 0 to 90 (degrees) Default: 1. vectorCount xs:int * Number of receptors along the ring. Valid values: 1 to 36. Default: 1. Attributes: None.

82 User Guides for Noise Modeling of Commercial Space Operations—rUMBLe and pCBoom 12.5.16 polarReceptor Defines receptor points within a polar grid. Structure (see Notation for information about reading this table). XML Tag Type Num Choice Description name string255 1 A string up to 255 characters long. coord2DGroup - 1 a Indicates how a two-dimensional group is specified. See coord2DGroup. originSource originSourceType * a Origin source name for the polar grid (must match a unique name of a specific source reference). originName string40 * Refers to an existing spaceport. distanceFromSource xs:double * Distance of point from polar origin. Valid values: 0 through 999999.999999 (ft). directionFromSource xs:double * Direction of point from polar origin. Valid values: 0 through 360 (degrees). elevation xs:double * The point’s elevation above MSL (ft). If not specified, RUMBLE will use elevation of spaceport. Attributes: None.

rSIF reference Guide 83 12.5.17 receptorSet Contains one or more receptor sets at various locations. Structure (see Notation for information about reading this table). XML Tag Type Num Description name string255 1 Descriptive name of the receptor set. coord2DGroup - 1 Description of a receptor group. See receptorGroup. Attributes: None. 12.5.18 reference Refers to a case by its scenario name and case name. Conditions required: the referenced case must have a unique name in the new scenario. Structure (see Notation for information about reading this table). XML Tag Type Num Description refScenarioName string255 1 Scenario under which an existing case appears. refCaseName string255 1 Existing case that appears under the refScenario. Attributes: None.

84 User Guides for Noise Modeling of Commercial Space Operations—rUMBLe and pCBoom 12.5.19 RsifXml Root node of the RSIF tree. Structure (see Notation for information about reading this table). XML Tag Type Num Choice Description options - ? Contains default option values applied to the study. See options. atmosphericProfile - 1 a Contains one or more atmospheric profile descriptions. fleet fleet ? a Contains study fleet data for RSIF partial import into existing study. See fleet. receptorSet - * a Contains one or more receptor sets at various locations. See receptorSet. spaceportLayout spaceportLayoutType 1 a Contains spaceport layout. study - 1 a Contains specific information about a study. See study. trajectorySet - 1 a A set of flight trajectories. See trajectorySet. Attributes XML Tag Type Use Description version string16 optional A string up to 16 characters long. content xs:string required Valid values: atmosphericProfile, fleet, receptorSet, spaceportLayout, study, and trajectorySet.

rSIF reference Guide 85 12.5.20 scenario Encapsulates a scenario – such as Baseline or Alternative. Structure (see Notation for information about reading this table). XML Tag Type Num Description name string255 1 Scenario under which an existing case appears. description string255 * A description of the scenario. caseSet - 1 Placeholder for one or more cases. See caseSet. annualization - 1 Contains annualizations. See annualization. Attributes: None. 12.5.21 study Contains specific information about a study.

86 User Guides for Noise Modeling of Commercial Space Operations—rUMBLe and pCBoom Structure (see Notation for information about reading this table). XML Tag Type Num Description name string40 1 Name of the study. studyType studyType 1 Type of study. Note that RUMBLE 2.0 only supports the Noise value. description string255 * Optional description of the study. spaceportLayout spaceportLayoutType 1 Contains information about the available layout of each spaceport in the study. atmosphericProfile - 1 Contains one or more atmospheric profile descriptions. See atmosphericProfile. receptorSet - 1 Contains one or more receptor sets at various locations. See receptorSet. fleet fleet * User-defined spacecraft fleet participating in the study. See fleet. scenario - 1 Encapsulates a scenario — such as Baseline or Alternative. See scenario. Attributes: None. 12.5.22 trajectory A flight trajectory that can be used for flight operations. Structure (see Notation for information about reading this table). XML Tag Type Num Description name string64 1 The name of the trajectory. opType opType 1 Type of operation (Launch, Landing, Static). trajectoryNodes - * A set of flight trajectory nodes. See trajectoryNodes. Attributes: None.

rSIF reference Guide 87 12.5.23 trajectoryNode A flight trajectory node.

88 User Guides for Noise Modeling of Commercial Space Operations—rUMBLe and pCBoom Structure (see Notation for information about reading this table). XML Tag Type Num Description nodeIdGroup - 1 A group of nodes. See nodeIdGroup. time xs:double Elapsed time (seconds). coord2DGroup - 1 Indicates how a two-dimensional group is specified. See coord2DGroup. altitude xs:double 1 Node’s altitude above MSL (ft). speed xs:double 1 Speed of spacecraft at node (ft/s). Valid values: nonnegative. flightPathHeading xs:double 1 Heading of flight path measured clockwise relative to True North (degrees). flightPathAngle xs:double 1 Angle of flight path measured relative to the horizon (positive value indicates climb) (degrees). vehicleHeading xs:double 1 Heading of vehicle measured clockwise relative to True North (degrees). If not specified, assume value equivalent to flightPathHeading. vehiclePitch xs:double 1 Pitch of vehicle measured relative to the horizon (positive value indicates climb) (degrees). If not specified, assume value equivalent to flightPathAngle. thrust xs:double * Net thrust for the spacecraft (lbf). Supports user-defined time-varying thrust. If not specified, assume thrust defined in fleet database. Can include optional attributes coreIdentifier and boosterIdentifier. spacecraftWeight xs:double * Net weight of the spacecraft (lbs). Supports user-defined time-varying weight. If not specified, assume weight defined in fleet database. spacecraftLength xs:double * Length of the spacecraft (ft). Supports user-defined time-varying length. If not specified, assume length defined in fleet database. Attributes: None. 12.5.24 trajectoryNodes A set of flight trajectory nodes. Structure (see Notation for information about reading this table). XML Tag Type Num Description trackNode - * A flight trajectory node. See trajectoryNode. Attributes: None.

rSIF reference Guide 89 12.5.25 trajectoryOpSet Lists trajectories and associated operations. Structure (see Notation for information about reading this table). XML Tag Type Num Choice Description trajectory - * a A flight trajectory that can be used for flight operations. See trajectory. trajectoryRef - 1 a Reference to a flight trajectory. See trajectoryRef. operations - 1 Contains a list of spacecraft flight operations. See operations. Attributes: None. 12.5.26 trajectoryRef Reference to a flight trajectory. Structure (see Notation for information about reading this table). XML Tag Type Num Description name string64 1 Name of trajectory. Attributes: None. 12.5.27 trajectorySet A set of flight trajectories. Structure (see Notation for information about reading this table). XML Tag Type Num Description trajectory - 1 A flight trajectory that can be used for flight operations. See trajectory. Attributes: None.

90 User Guides for Noise Modeling of Commercial Space Operations—rUMBLe and pCBoom 12.6 Group Descriptions 12.6.1 coord2DGroup Indicates how a two-dimensional group is specified. Structure (see Notation for information about reading this table). XML Tag Type Num Choice Description latlonCoordGroup - 1 a Specifies a coordinate using latitude and longitude. See latlonCoordGroup. utmCoordGroup - 1 a Specifies a point using Universal Transverse Mercator coordinates. See utmCoordGroup. Attributes: None. 12.6.2 latlonCoordGroup Specifies a coordinate using latitude and longitude. Structure (see Notation for information about reading this table). XML Tag Type Num Choice Description latitude latitudeDecimalType 1 a Latitude specified as degrees in decimal format. Can include optional attribute positive. See latitudeDecimalType. latitudeDMS latitudeDMSType 1 a Latitude expressed as dd”mm’sss with optional indicator N, n, S, s. See latitudeDMSType. longitude longitudeDecimalType 1 b Longitude specified as degrees in decimal format. Can include optional attribute positive. See longitudeDecimalType. longitudeDMS longitudeDMSType 1 b Longitude expressed as dd”mm’sss with optional indicator E, e, W, w. See longitudeDMSType. Attributes: None.

rSIF reference Guide 91 12.6.3 nodeIdGroup A group of nodes. Structure (see Notation for information about reading this table). XML Tag Type Num Description id string16 * String identifier for the grouping of nodes. description string16 * An optional description for the grouping of nodes. Attributes: None. 12.6.4 receptorGroup Description of a receptor group. Structure (see Notation for information about reading this table). XML Tag Type Num Choice Description centroid - 1 a Describes the geometric center of a polygon. See centroid. pointReceptor - 1 a Element specification for a point receptor. See pointReceptor. grid - 1 a Describes a grid of points. See grid. polarReceptor - 1 a Defines receptor points within a polar grid. See polarReceptor. polarGrid - 1 a Describes a two-dimensional grid of individual receptors over an annular sector (polar) of the study area. See polarGrid. Attributes: None.

92 User Guides for Noise Modeling of Commercial Space Operations—rUMBLe and pCBoom 12.6.5 utmCoordGroup Specifies a point using Universal Transverse Mercator coordinates. Structure (see Notation for information about reading this table). XML Tag Type Num Description utmN xs:double 1 UTM Northing of the point in decimal meters north of the equator. utmE xs:double 1 UTM Easting of the point in decimal meters east from a central meridian. utmZone xs:int ? UTM Zone of the point. A default zone can be set in the <options> tag. Default: –1. Attributes: None. 12.7 Complex Type Descriptions 12.7.1 airframe This element supports the definition of custom airframes.

rSIF reference Guide 93 Structure (see Notation for information about reading this table). XML Tag Type Num Description model airframeModel 1 Unique description of airframe. airframeRef xs:int * AST STAR Database reference. type string40 * AST STAR Database type designation: Expendable Launch Vehicle (ELV), Reusable Launch Vehicle (RLV), Suborbital. status string40 * AST STAR Database status designation: Design/Development, No Longer in Service, and Operational. manufacturer string100 * Airframe manufacturer. capacity string40 * AST STAR Database capacity designation: Heavy, Intermediate, Medium, Small, and Suborbital. deployment string40 * AST STAR Database deployment designation: Orbital and Suborbital. numStages xs:int * Number of Stages. length xs:double * Length of this airframe (ft). weight xs:double * Weight of this airframe (lbs). diameter xs:double * Diameter of this airframe (ft). dataSource string100 * Source of airframe data. notes string200 * Free-text notes for the airframe. cores cores 1 This block describes each core/booster. See cores. access string40 * Data access description: public or non-public. Attributes: None. 12.7.2 booster This block describes each booster. Structure (see Notation for information about reading this table). XML Tag Type Num Description identifier boosterId 1 Unique booster identifier. numEngines xs:int 1 Number of engines per booster. count xs:int 1 Number of boosters per core. length xs:double * Length of booster (ft). weight xs:double * Weight of booster (lbs). Attributes: None.

94 User Guides for Noise Modeling of Commercial Space Operations—rUMBLe and pCBoom 12.7.3 boosters This block describes the core’s booster(s). Structure (see Notation for information about reading this table). XML Tag Type Num Description booster booster 1 This block describes each booster. See booster. Attributes: None. 12.7.4 coord2DType A 2D point coordinate. Structure (see Notation for information about reading this table). XML Tag Type Num Choice Description latlonCoordGroup - 1 a Specifies a coordinate using latitude and longitude. See latlonCoordGroup. utmCoordGroup - 1 a Specifies a point using Universal Transverse Mercator coordinates. See utmCoordGroup. Attributes: None.

rSIF reference Guide 95 12.7.5 core This block describes each core. Structure (see Notation for information about reading this table). XML Tag Type Num Description identifier coreId 1 Unique core identifier. numEngines xs:int 1 Number of engines per core. count xs:int 1 Number of cores. length xs:double * Length of core (ft). weight xs:double * Weight of core (lbs). boosters boosters * This block describes each booster. See boosters. Attributes: None. 12.7.6 cores This block describes the airframe’s engine core(s). Structure (see Notation for information about reading this table). XML Tag Type Num Description core core 1 This block describes each core. See core. Attributes: None.

96 User Guides for Noise Modeling of Commercial Space Operations—rUMBLe and pCBoom 12.7.7 directivity This element supports the definition of custom directivities. Structure (see Notation for information about reading this table). XML Tag Type Num Description Identifier string40 1 The unique identifier for this user-defined directivity. directivityNodes directivityNodes 1 A set of directivity nodes. See directivityNodes. Attributes: None. 12.7.8 directivityNode A directivity node. Structure (see Notation for information about reading this table). XML Tag Type Num Description angle xs:double 1 Angle measured from the plume exit angle to the receptor (degrees). strouhalNumber xs:double 1 Strouhal number = frequency times nozzle exit diameter divided by nozzle exit velocity (dimensionless). directivityIndice xs:double 1 Directivity indice characterizes directivity of sound radiation for the angle and strouhal number (dB). Attributes: None. 12.7.9 directivityNodes A set of directivity nodes. Structure (see Notation for information about reading this table). XML Tag Type Num Description directivityNode directivityNode 1 A directivity node. See directivityNode. Attributes: None.

rSIF reference Guide 97 12.7.10 engine User-defined engine information containing custom parameters that reflect a spacecraft engine. This engine definition can be used within a user-defined spacecraft. Structure (see Notation for information about reading this table). XML Tag Type Num Description code engineCode 1 Unique engine code. model engineModel 1 Engine model. weight xs:double * Dry weight of this engine (lbs). manufacturer string100 * Engine manufacturer. propellantDescription string255 * Description of engine propellant. thrust xs:double 1 Net thrust for the engine (lbf). nozzleExitDiameter xs:double 1 Nozzle exit diameter for the engine (ft). nozzleExitVelocity xs:double 1 Nozzle exit velocity for the engine (ft/sec). nozzleExitSoundSpeed xs:double * Nozzle exit sound speed for the engine (ft/sec). nozzleExitMach xs:double * Nozzle exit Mach for the engine (nozzleExitVelocity ÷ nozzleExitSoundSpeed). nozzleCount xs:int 1 Number of nozzles for the engine. notes string200 * Free-text notes for the engine. dataSource string100 * Source of engine data. access string40 * Data access description: public or non-public. Attributes: None.

98 User Guides for Noise Modeling of Commercial Space Operations—rUMBLe and pCBoom 12.7.11 fleet Main block for creating user-defined fleet/spacecraft data. Structure (see Notation for information about reading this table). XML Tag Type Num Description airframe airframe * Supports the definition of custom airframes. See airframe. engine engine * User-defined engine information containing custom parameters that reflect an engine. This engine definition can then be used within a user-defined spacecraft. See engine. directivity directivity * This element supports the definition of custom directivities. See directivity. spacecraft spacecraft * A block used to create new user-defined AEDT aircraft. See spacecraft. Attributes: None. 12.7.12 latitudeDecimalType Latitude specified as degrees in decimal format. Can include optional attribute positive (deci- mal degrees). Attributes XML Tag Type Use Description positive xs:string optional Valid values: N, n, S, s.

rSIF reference Guide 99 12.7.13 longitudeDecimalType Longitude specified as degrees in decimal format. Can include optional attribute positive (decimal degrees). Attributes XML Tag Type Use Description positive xs:string optional Valid values: E, e, W, w. 12.7.14 spacecraft Main block for creating new user-defined spacecraft. Structure (see Notation for information about reading this table). XML Tag Type Num Description identifier spacecraftId * The unique identifier for this user-defined spacecraft. description string255 * The description for this user-defined spacecraft. airframeModel airframeModel * The airframe model used for this user-defined spacecraft. spacecraftCores spacecraftCores 1 This block describes each core/booster. propellantWeight xs:double * Total weight of propellant for this spacecraft (lbs). access string40 * Data access description: public or non-public. Attributes: None.

100 User Guides for Noise Modeling of Commercial Space Operations—rUMBLe and pCBoom 12.7.15 spacecraftBooster This block describes each spacecraft booster. Structure (see Notation for information about reading this table). XML Tag Type Num Description identifier boosterId * Unique identifier of core booster from selected airframeModel. engineCode engineCode * Code for the engine model used for this user-defined spacecraft’s core booster. Attributes: None. 12.7.16 spacecraftBoosters A set of spacecraft boosters. Structure (see Notation for information about reading this table). XML Tag Type Num Description spacecraftBooster spacecraftBooster * This block describes each spacecraft booster. Attributes: None. 12.7.17 spacecraftCore This block describes each spacecraft core. Structure (see Notation for information about reading this table). XML Tag Type Num Description identifier coreId * Unique identifier of core from selected airframeModel. engineCode engineCode * Code for the engine model used for this user-defined spacecraft’s core. spacecraftBoosters spacecraftBoosters * A set of spacecraft boosters. directivityIdentifier directivityId 1 The unique identifier for directivity for this user- defined spacecraft’s core. Attributes: None.

rSIF reference Guide 101 12.7.18 spacecraftCores A set of spacecraft cores. Structure (see Notation for information about reading this table). XML Tag Type Num Description spacecraftCore spacecraftCore * This block describes each spacecraft core. Attributes: None. 12.7.19 spaceportLayoutType Fields defining a spaceport and its layout. Structure (see Notation for information about reading this table). XML Tag Type Num Description name string255 * Id of the layout. Must be unique. elevation xs:double * The elevation above MSL (ft). coord2DGroup - * Indicates how a two-dimensional group is specified. See coord2DGroup. trajectorySet - * A set of flight trajectories. See trajectorySet. Attributes: None.

102 User Guides for Noise Modeling of Commercial Space Operations—rUMBLe and pCBoom 12.7.20 staticFire Structure (see Notation for information about reading this table). XML Tag Type Num Description Id string16 1 User-specified identifier for the static fire operation. spacecraftIdentifier spacecraftId 1 Spacecraft identifier. numAnnualOperationsDay xs:double 1 Number of annual acoustic daytime operations comprising this operation, where daytime hours are: (7:00 am to 10:00 pm) or (7:00 am to 7:00 pm) when evening operations are defined. numAnnualOperationsNight xs:double 1 Number of acoustic annual nighttime operations comprising this operation, where nighttime hours are: (10:00 pm to 7:00 am). numAnnualOperationsEvening xs:double * Number of annual acoustic evening operations comprising this operation, where evening hours are: (7:00 pm to 10:00 pm). orientation string16 1 Orientation of vehicle (vertical or horizontal). coord2DGroup - 1 Indicates how a two-dimensional group is specified. See coord2DGroup. height xs:double 1 The height of the vehicle above ground (ft). duration xs:double 1 The duration of the static fire. heading xs:double * The orientation of the spacecraft (degrees). If not specified, vehicle orientation is vertical. thrust xs:double * The thrust employed for this static fire operation (lbf). If not specified, model will use thrust from fleet database. Attributes: None.

rSIF reference Guide 103 12.8 Simple Type Descriptions 12.8.1 airframeModel Refers to an existing airframe model. Attributes: None. 12.8.2 boosterId ID of booster. Must be a new, unique value within each core. Attributes: None. 12.8.3 coreId ID of core. Must be a new, unique value within each airframe. Attributes: None. 12.8.4 engineCode Code for an airframe’s engine. Attributes: None. 12.8.5 engineModel Attributes: None. 12.8.6 engineType Type of engine on this airframe. Attributes: None. 12.8.7 directivityId ID of directivity data. Must be a new, unique value. Attributes: None. 12.8.8 latitudeDMSType Latitude expressed as dd"mm'sss with optional indicator N, n, S, s (degrees). Attributes: None. 12.8.9 longitudeDMSType Longitude expressed as dd"mm'sss with optional indicator N, n, S, s (degrees). Attributes: None.

104 User Guides for Noise Modeling of Commercial Space Operations—rUMBLe and pCBoom 12.8.10 opType Type of operation. Valid values: Launch, Landing, and Static Fire. Attributes: None. 12.8.11 originSourceType Supports the polarReceptor source type. Original source type can be spaceport. Valid values: Spaceport. Attributes: None. 12.8.12 spacecraftId ID of spacecraft. Must be a new, unique value. Attributes: None. 12.8.13 string100 A string up to 100 characters long. Attributes: None. 12.8.14 string16 A string up to 16 characters long. Attributes: None. 12.8.15 string200 A string up to 200 characters long. Attributes: None. 12.8.16 string255 A string up to 255 characters long. Attributes: None. 12.8.17 string40 A string up to 40 characters long. Attributes: None. 12.8.18 string6 A string up to six characters long. Attributes: None.

rSIF reference Guide 105 12.8.19 string64 A string up to 64 characters long. Attributes: None. 12.8.20 string8 A string up to eight characters long. Attributes: None. 12.8.21 studyType Type of study. Note that RUMBLE 2.0 only supports the Noise value. Valid values: Noise. Attributes: None.

106 1. K. M. Eldred, NASA SP-8072: Acoustic Loads Generated By the Propulsion Systems, NASA, 1971. 2. M. M. James, A. R. Salton, K. L. Gee, T. B. Neilsen and S. A. McInerny, Full-Scale Rocket Motor Acoustic Tests and Comparisons with Empirical Source Models, vol. 18, J. Acoust. Soc. Am., 2014. 3. S. H. Guest, NASA TN D-1999: Acoustic Efficiency Trends for High Thrust Boosters, NASA Marshall Space Flight Center: NASA, 1964. 4. K. Viswanathan and M. J. Czech, Measurements and Modeling of Effect of Forward Flight on Jet Noise, vol. 49, AIAA, 2011. 5. S. Saxena and P. Morris, Noise Predictions for High Subsonic Single and Dual-Stream Jets in Flight, Colorado Springs, CO, 2012. 6. R. Buckley and C. L. Morfey, Scaling Laws for Jet Mixing Noise in Simulated Flight and the Prediction Scheme Associated, Williamsburg, VA: AIAA, 1984. 7. R. Buckley and C. L. Morfey, Flight Effects on Jet Mixing Noise: Scaling Laws Predicted for Single Jets from Flight Simulation Data, Atlanta, GA: AIAA, 1983. 8. J. Haynes and J. R. Kenny, Modifications to the NASA SP-8072 Distributed Source Method II, Miami, Florida: AIAA, 2009. 9. M. M. James, A. R. Salton, K. L. Gee, T. B. Neilsen, S. A. McInerny and R. J. Kenny, Modification of Directivity Curves for a Rocket Noise Model, vol. 18, J. Acoust. Soc. Am., 2014. 10. E. J. Rickley, J. E. Rosenbaum, G. G. Fleming, C. J. Roof and E. R. Boeker, “Development of Simplified Procedure for Computing the Absorption of Sound by the Atmosphere and Applicability to Aircraft Noise Certification: Proposed SAE Method,” U.S. Department of Transportation, Cambridge, MA, 2012. 11. C. Chessel, Propagation of Noise Along a Finite Impedance Boundary, vol. 62, J. Acoust. Soc. Am., 1977, pp. 825–834. 12. T. Embleton, J. Piercy and G. Daigie, Effective Flow Resistivity of Ground Surfaces Determined by Acoustical Measurements, vol. 74, J. Acoust. Soc. Am., 1983, pp. 1239–1244. 13. G. A. Daigle, Effects of Atmospheric Turbulence on the Interference Sound Waves Above a Finite Impedance Boundary, vol. 65, J. Acoust. Soc. Am., 1979. 14. FAA, “Guidance on Using the Aviation Environmental Design Tool (AEDT) to Conduct Environmental Modeling for FAA Actions Subject to NEPA,” 2016. 15. National Oceanic and Atmospheric Administration, National Aeronautics and Space Administration, and United States Air Force, “U.S. Standard Atmosphere, 1976.” 16. F. Fayh and D. Thompson, Fundamentals of Sound and Vibration, Second Edition, Boca Raton, FL: CRC Press, 2015. References

107 AEDT Aviation Environmental Design Tool AEE Office of Environment and Energy AGL Above Ground Level ANSI American National Standards Institute ASIF AEDT Standard Input File AST Office of Commercial Space Transportation BRRC Blue Ridge Research and Consulting, LLC CNEL Community Noise Equivalent Level dB Decibel dBA A-weighted Decibel De Nozzle Diameters DI Directivity Indices DNL Day-Night Average Sound Level DSM-1 Distributed Source Method 1 EA Environmental Assessment EIS Environmental Impact Statement ELV Expendable Launch Vehicle °F Degrees Fahrenheit (temperature) FAA United States Federal Aviation Administration ft Feet (length) GIS Geographic Information System GUI Graphical User Interface ISS International Space Station LAMAX Maximum A-weighted Sound Level with Slow-scale Exponential Time Weighting LMAX Maximum Unweighted Sound Level with Slow-scale Exponential Time Weighting lb Pound (weight) lbf Pounds Force MSL Mean Sea Level NASA National Aeronautics and Space Administration NEPA National Environmental Policy Act NMGF Noise Model Grid Format nmi International Nautical Miles (1,852 m) OASPL Overall Sound Pressure Level OTO One-Third Octave Pa Pascal (unit of pressure, one Newton per square meter) PC Project Consultant Abbreviations

108 User Guides for Noise Modeling of Commercial Space Operations—RUMBLE and PCBoom PM Project Manager PS Project Sponsor RLV Reusable Launch Vehicle RSIF RUMBLE Standard Input File RSRM Reusable Solid Rocket Motor s, sec Second (time duration) SEL A-weighted Sound Exposure Level SPL Sound Pressure Level SS2 Space Ship Two U.S. United States WGS84 World Geodetic System WK2 White Knight 2 XSD XML Schema Definition µPa Micropascal