PEGEM_Users_Manual.pdf

UNCLASSIFIED

POST-ENGAGEMENT GROUND

EFFECTS MODEL

PEGEM User’s Manual Version 1.5

30 September 2015

The views, opinions, and/or findings contained in this document are those of the author(s) and should not be construed as an official Department of Defense (DoD) position, policy, or decision, unless so designated by other official documentation.

Warning – This document contains technical data whose export is restricted by the Arms Export Control Act (Title 22, U.S.C., Sec. 2751 et seq) or Executive Order 12470. Violators of these export laws are subject to severe criminal penalties.

Destruction Notice – For classified documents, follow the procedures in DOD 5200.22-M, Industrial Security Manual, Section 11-79 or DoD 5200.1-R, Information Security Program Regulation, Chapter IX. For unclassified and/or limited distribution documents, destroy by any method that will prevent disclosure of contents or reconstruction of the document.

Distribution Statement F – Further dissemination only as directed by the Missile Defense Agency: 7100 Defense Pentagon, Washington, D.C. 20301- 7100, or higher DoD authority.

UNCLASSIFIED Table of Contents

PEGEM USER’S MANUAL ii

Version 1.5 UNCLASSIFIED SEPTEMBER 2015

Table of Contents

CHAPTER 1 - Chapter 1 Introduction ..................................................................................................... 1-1

1.1 BMDS ............................................................................................................................ 1-1

1.2 Purpose of PEGEM ........................................................................................................ 1-2

1.3 PEGEM Overview .......................................................................................................... 1-2

CHAPTER 2 - PEGEM GUI Installation .................................................................................................... 2-1

2.1 System Requirements ................................................................................................... 2-1

CHAPTER 3 - Graphical Interface and Event Wizard ............................................................................. 3-1

3.1 Graphical Interface and Map ........................................................................................ 3-1

3.1.1 Manipulating the Earth................................................................................................. 3-1

3.1.2 Earth File ....................................................................................................................... 3-2

3.1.3 Configuring PEGEM ...................................................................................................... 3-3

3.1.4 Contour File .................................................................................................................. 3-4

3.1.5 Miscellaneous GUI Features ......................................................................................... 3-6

3.2 New PEGEM Project ..................................................................................................... 3-8

3.2.1 Create New Project and Opening Existing Projects ...................................................... 3-9

3.2.2 Project Settings ........................................................................................................... 3-10

3.3 Weather Setup ........................................................................................................... 3-14

3.4 Population Setup ........................................................................................................ 3-17

3.5 Event Wizard .............................................................................................................. 3-19

3.5.1 Event Definition .......................................................................................................... 3-19

3.5.2 Event Location and Velocity State .............................................................................. 3-21

3.5.3 Position/Velocity Covariance...................................................................................... 3-25

3.5.4 Debris Option ............................................................................................................. 3-27

3.5.5 Payload Lethality Options ........................................................................................... 3-31

3.5.6 Casualty and Agent Transport Code Options ............................................................. 3-33

3.5.7 Hazard Type Output Options ...................................................................................... 3-35

3.5.8 Threat Payload Option................................................................................................ 3-37

3.5.9 Miscellaneous Event Options ..................................................................................... 3-40

PEGEM USER’S MANUAL iii

Version 1.5 UNCLASSIFIED SEPTEMBER 2015

3.5.10 Conclusion .................................................................................................................. 3-42

3.6 Process Events ............................................................................................................ 3-43

3.7 Summary File Output.................................................................................................. 3-43

CHAPTER 4 - PEGEM Input Files ............................................................................................................ 4-1

4.1 PEGEM Input Files ........................................................................................................ 4-1

4.2 PEGEM Project File ....................................................................................................... 4-1

4.3 PEGEM Event File ......................................................................................................... 4-4

4.4 Engagement Lethality Input ....................................................................................... 4-11

4.4.1 PEELS STEM Databases ............................................................................................... 4-12

4.4.2 Lethality Data File ....................................................................................................... 4-13

4.5 Threat Description File ............................................................................................... 4-15

4.5.1 Common Threat Data Block........................................................................................ 4-18

4.5.2 Fill Type Data Block ..................................................................................................... 4-19

4.5.3 Payload Type Data Block ............................................................................................ 4-22

4.5.4 Missile Type Data Block .............................................................................................. 4-26

4.5.5 Debris Data Block ....................................................................................................... 4-26

4.6 Aerodynamic Coefficient Database Files .................................................................... 4-29

4.6.1 General Aerodynamic Coefficient Files ...................................................................... 4-30

4.6.2 Aerodynamic Drag Coefficient Files ........................................................................... 4-35

4.7 Magnus Rotor and Ellipsoid Submunition Database File ........................................... 4-36

4.8 Agent Parameter Files ................................................................................................ 4-37

4.9 Surface Meteorological File ........................................................................................ 4-42

4.9.1 PEGEM Formatted Surface File .................................................................................. 4-42

4.9.2 HPAC Surface Observation Files ................................................................................. 4-44

4.9.3 Chemical Downwind Report (CDR) ............................................................................. 4-49

4.10 Upper Atmosphere Meteorological Profile File ......................................................... 4-55

4.10.1 PEGEM Formatted Files .............................................................................................. 4-55

4.10.2 HPAC Upper Air Observation Files .............................................................................. 4-58

4.10.3 Basic Wind Report (BWR) ........................................................................................... 4-63

4.10.4 Historical Meteorological Database Option ............................................................... 4-68

PEGEM USER’S MANUAL iv

Version 1.5 UNCLASSIFIED SEPTEMBER 2015

4.10.5 Weather Server .......................................................................................................... 4-72

4.11 Surface Type Data ....................................................................................................... 4-75

4.12 Atmospheric Model Data ........................................................................................... 4-75

4.13 Population Data File ................................................................................................... 4-76

4.13.1 Protective Posture ...................................................................................................... 4-77

4.13.2 LandScan Data ............................................................................................................ 4-78

4.13.3 Urban Civilian Population (P95) Data ......................................................................... 4-79

4.13.4 Blue Force Facility Data .............................................................................................. 4-81

4.13.5 User-Defined Asset Data ............................................................................................ 4-82

4.13.6 Combined Area and Point Asset Data ........................................................................ 4-86

4.13.7 Population PPL File .................................................................................................... 4-88

4.14 Direct Submunition Velocity Input ............................................................................. 4-88

4.14.1 Auxiliary Dispersion Velocity Components................................................................. 4-88

4.14.2 Statistical Imparted Speed.......................................................................................... 4-89

4.15 Direct Ground Impact Input ....................................................................................... 4-90

4.16 PEGEM Overwrite File ................................................................................................ 4-91

4.17 Trajectory File ............................................................................................................. 4-97

4.17.1 Ballistic Trajectory ...................................................................................................... 4-97

4.17.2 Azimuth Angle Trajectory ........................................................................................... 4-99

4.17.3 Angle Definitions ...................................................................................................... 4-101

4.18 Interceptor Description File ...................................................................................... 4-102

4.19 Interceptor Performance Envelope File ................................................................... 4-105

4.20 Direct Debris Input ................................................................................................... 4-107

4.20.1 Direct Debris ENU Ground Impact Input .................................................................. 4-107

4.20.2 Direct Debris Characterization, Ejection Velocity Input ........................................... 4-109

4.21 Submunition Debris Material Component Input ...................................................... 4-110

4.22 Booster Description File Format ............................................................................... 4-111

4.23 PEGEM Executive Control (.pgm) File ....................................................................... 4-113

CHAPTER 5 - PEGEM References ........................................................................................................... 5-1

APPENDIX A - Sample .pgm File

PEGEM USER’S MANUAL v

Version 1.5 UNCLASSIFIED SEPTEMBER 2015

APPENDIX B – Hazard Types and Default Settings

UNCLASSIFIED List of Figures

PEGEM USER’S MANUAL vi

Version 1.5 UNCLASSIFIED SEPTEMBER 2015

List of Figures

Figure 1.3-1 PEGEM Overview .................................................................................................................. 1-3

Figure 2.1-1 PEGEM Installation................................................................................................................ 2-2

Figure 2.1-2 Software Utility Agreement .................................................................................................. 2-2

Figure 2.1-3 Installation User Information ................................................................................................ 2-3

Figure 2.1-4 Installation Directory Path .................................................................................................... 2-3

Figure 2.1-5 Installation Confirmation ...................................................................................................... 2-4

Figure 2.1-6 Installation Status Update .................................................................................................... 2-4

Figure 2.1-7 Installation Completed.......................................................................................................... 2-5

Figure 3.1-1 PEGEM User Interface ........................................................................................................... 3-1

Figure 3.1-2 Example PEGEM Impact Points and Contours ...................................................................... 3-4

Figure 3.1-3 Sample Contour File .............................................................................................................. 3-5

Figure 3.1-4 View Contour Legend............................................................................................................. 3-6

Figure 3.1-5 PEGEM Tooltip Descriptions .................................................................................................. 3-7

Figure 3.1-6 PEGEM Measure Tool ............................................................................................................ 3-7

Figure 3.1-7 Sample Timeline Dockable Window ..................................................................................... 3-8

Figure 3.1-8 Multiple Sample Time Contours ........................................................................................... 3-8

Figure 3.2-1 PEGEM Opening Screen ........................................................................................................ 3-9

Figure 3.2-2 New PEGEM Project Filename Definition ........................................................................... 3-10

Figure 3.2-3 Project Setting General Tab ................................................................................................ 3-10

Figure 3.2-4 PEGEM Project Sample ....................................................................................................... 3-11

Figure 3.2-5 Project Overwrite Values Tab ............................................................................................. 3-12

Figure 3.3-1 PEGEM Weather Settings.................................................................................................... 3-15

Figure 3.3-2 Observation Input Dialog .................................................................................................... 3-16

Figure 3.4-1 Population Setting .............................................................................................................. 3-18

Figure 3.5-1 Event Wizard Event Definition ............................................................................................ 3-20

Figure 3.5-2 Event Location and Velocity Components .......................................................................... 3-21

Figure 3.5-3 Event State Calculator from Trajectory Data ...................................................................... 3-22

Figure 3.5-4 Event Trajectory Location Definition .................................................................................. 3-23

Figure 3.5-5 Engagement Crossing Angle ............................................................................................... 3-25 file:///C:/Users/Jackie.Perry/Documents/PEGEM/PEGEM%20Documentation/1.5%20Release/PEGEM%20v1.5%20Users%20Manual%20rev1.docx%23_Toc429997647

PEGEM USER’S MANUAL vii

Version 1.5 UNCLASSIFIED SEPTEMBER 2015

Figure 3.5-6 Engagement Roll Angle ....................................................................................................... 3-25

Figure 3.5-7 Position/Velocity Covariance Page ...................................................................................... 3-26

Figure 3.5-8 Debris Options for Intercept Events ................................................................................... 3-27

Figure 3.5-9 Influence of Impact Kinetic Energy Threshold and Percentage Variation on Bounding Debris

Characterization ....................................................................................................................................... 3-28

Figure 3.5-10 Payload Lethality Options ................................................................................................. 3-31

Figure 3.5-11 Agent Transport and Casualty Options ............................................................................. 3-33

Figure 3.5-12 Agent, HE, and Debris Output Selection ........................................................................... 3-35

Figure 3.5-13 Threat Payload and HE Options ........................................................................................ 3-37

Figure 3.5-14 Event Wizard Miscellaneous Event Options ...................................................................... 3-41

Figure 3.5-15 Event Wizard Event Setup Completion ............................................................................. 3-42

Figure 3.6-1 Process Selected Events ....................................................................................................... 3-43

Figure 3.7-1 PEGEM Summary File Dialog ............................................................................................... 3-44

Figure 4.2-1 Sample Project File ............................................................................................................... 4-3

Figure 4.3-1 Sample Event File ................................................................................................................ 4-11

Figure 4.5-1 Influence of Impact Kinetic Energy Threshold and Percentage Variation on Bounding Debris

Characterization ....................................................................................................................................... 4-29

Figure 4.6-1 Sample Magnus Rotor Aerodynamic Database File ............................................................ 4-34

Figure 4.6-2 Sample Canister Submunition (Type I) Aerodynamic Database File .................................. 4-35

Figure 4.6-3 Sample Spherical Submunition Aerodynamic Database File .............................................. 4-36

Figure 4.8-1 Order of Individual Parameters .......................................................................................... 4-40

Figure 4.8-2 Parameter Key Numbering Scheme .................................................................................... 4-42

Figure 4.9-1 Sample CDR File .................................................................................................................. 4-49

Figure 4.9-2 NATO Area of Validity Methodology (NFEA31) .................................................................. 4-50

Figure 4.10-1 Sample BWR File ............................................................................................................... 4-64

Figure 4.10-2 Sample Historical Meteorological Database File .............................................................. 4-72

Figure 4.10-3 Sample Weather Server Surface File ................................................................................ 4-72

Figure 4.10-4 Sample Weather Server Profile File .................................................................................. 4-73

Figure 4.10-5 Sample MEDOC File .......................................................................................................... 4-74

Figure 4.10-6 Sample Profile ARRAY File ................................................................................................. 4-74

PEGEM USER’S MANUAL viii

Version 1.5 UNCLASSIFIED SEPTEMBER 2015

Figure 4.10-7 Sample HASCAL File .......................................................................................................... 4-75

Figure 4.12-1 Example GRAM-95 Vertical Profile Data ........................................................................... 4-76

Figure 4.13-1 Population Data Overlaid onto Hazard Hotspot ............................................................... 4-77

Figure 4.13-2 Asset and Facility Definitions ............................................................................................ 4-83

Figure 4.13-3 Example of Uniform Population Data File ........................................................................ 4-85

Figure 4.13-4 Example of Point Asset Population Data File .................................................................... 4-86

Figure 4.13-5 Example of Combined Area and Point Asset Population Data File ................................... 4-87

Figure 4.14-1 Auxiliary Deployment Imparted Velocity Component Definition ..................................... 4-89

Figure 4.14-2 Example of Statistical Imparted Speed File Format .......................................................... 4-90

Figure 4.17-1 Sample Ballistic Trajectory File Data ................................................................................. 4-99

Figure 4.17-2 Example User Defined Trajectory ..................................................................................... 4-99

Figure 4.17-3 Example Azimuth Angle Trajectory ................................................................................. 4-100

Figure 4.17-4 Illustration of an Azimuth Angle Trajectory .................................................................... 4-101

Figure 4.17-5 Definitions of Angle-of-Attack and Sideslip .................................................................... 4-102

Figure 4.17-6 Example Trajectory with Terrain ..................................................................................... 4-102

Figure 4.19-1 Definition of Cross_Angle, Threat_Aim, and Miss_Sigma .............................................. 4-106

Figure 4.19-2 Definition of Roll_Angle from the Vertical Trajectory Plane .......................................... 4-106

Figure 4.20-1 Example Direct Debris Input File ..................................................................................... 4-108

Figure 4.20-2 Example Debris Characterization, Imparted Velocity Input File ..................................... 4-110

Figure 4.21-1 Spherical Submunition Debris Material Component Support File ................................. 4-111

Figure 4.22-1 Significant Booster Sections, Example of Booster Sections 1-2 of 4 Interacted by

Interceptor Engagement ........................................................................................................................ 4-111

Figure 4.22-2 Sample Booster Description File ..................................................................................... 4-113

UNCLASSIFIED List of Tables

PEGEM USER’S MANUAL ix

Version 1.5 UNCLASSIFIED SEPTEMBER 2015

List of Tables

Table 2.1-1 PEGEM Installation Requirements .......................................................................................... 2-1

Table 3.1-1 INI Parameters ....................................................................................................................... 3-3

Table 3.2-1 PEGEM Overwrite File Inputs ................................................................................................ 3-13

Table 3.5-1 PEGEM Hazard Output Options based on Payload Type ...................................................... 3-36

Table 4.4-1 PEELS STEM Database Threat/Interceptor Identification .................................................... 4-12

Table 4.6-1 Key Aerodynamic Coefficients and Treat Types ................................................................... 4-30

Table 4.8-1 Common Explosive Material Equivalent TNT Ration, Mott, and Gurney Constants ............ 4-37

Table 4.8-2 Radiological Agent Parameters ............................................................................................ 4-38

Table 4.16-1 PEGEM Overwrite File Inputs ............................................................................................. 4-92

Table 4.23-1 Advanced Debris, Event Data Input Definitions ............................................................... 4-125

PEGEM USER’S MANUAL 1-1

Version 1.5 UNCLASSIFIED SEPTEMBER 2015

CHAPTER 1 - Chapter 1 Introduction

1.1 BMDS

Analyzing the lethality and vulnerability of current and future ballistic missile defense systems is an integral part of any defense element development cycle. Performance must be assessed first against the baseline threat, and then against excursions to simulate dynamic ballistic missile defense systems and combined arms threat environments. Finally, performance must be assessed in the context of future deployment and combined arms scenarios.

The measure of a BMDS element’s performance is sensitive to individual measures of lethality effectiveness. Many lethality endgame simulations assume that a direct correlation exists between probability of hit and probability of kill, i.e., a successful hit can translate into a successful kill. However, detailed analyses have shown that conventional, chemical/biological threat payloads can still create significant residual lethal ground effects after intercept. These post-engagement effects are not readily modeled in a system effectiveness simulation.

In order to be able to assess ground collateral effects from both intercepted and non-intercepted tactical ballistic missiles (TBM), the Missile Defense Agency (MDA) has sponsored the development of an analysis tool called the Post-Engagement Ground Effects Model (PEGEM). As a component of system-level models, the constituent models in PEGEM allow analysis of the BMDS lethality issues such as intercept damage and penetration mechanics, agent breakup, vaporized agent, munition ejection and propagation, agent atmospheric transport and ground hazard assessment, casualties, and unit effectiveness.

PEGEM has been used to support Cost and Operational Effectiveness Analyses (COEA) system milestone decisions, BMDS Consequence Management, and operational requirements. PEGEM provides chemical, biological, radiological, nuclear or conventional high explosive (CBRNE) battlefield effects to the simulated battlefield environment. PEGEM is also used as a stand-alone simulation to support the war fighter in training exercises and simulations. Stand-alone usage includes operational planning and early warning exercise simulation.

Post-engagement events and their corresponding lethality measures of performance (MOP) are some of the technical issues associated with modeling post-engagement phenomena. PEGEM facilitates lethality studies to assess sensitivities to variations in meteorological conditions, threat types, payloads, damage level, ground scenario, casualties, and secondary kill mode criteria.

PEGEM, Kinetic Impact Debris Distribution (KIDD), and Parametric Endo/Exoatmospheric Lethality

Simulation (PEELS) provide an integrated suite of engagement and post-engagement simulations to perform lethality studies, analyze performance issues, and interface with systems-effectiveness simulations. Integrated suites provide a concise method of exercising system performance and analyzing critical issues.

PEGEM USER’S MANUAL 1-2

Version 1.5 UNCLASSIFIED SEPTEMBER 2015

1.2 Purpose of PEGEM

PEGEM connects payload point-of-intercept lethality in the air with ground collateral effects (ground lethality). PEGEM provides CBRNE munition hazards, as well as agent-coated solid debris field assessment, in the form of effects on the ground against user-definable assets. Output of the model is in the form of CBRNE agent and debris ground extents, as well as estimated casualties at user-specified times-of-interest (TOIs). PEGEM supports ballistic missile defense (BMD) system acquisitions, and provides a valuable tool to both evaluate individual and integrated BMD systems and to estimate

(simulate) CBRNE effects on the battlefield. PEGEM capabilities are designed primarily for hit-to-kill

(HTK) intercepts, although some capability exists for blast/fragment interceptor warheads as well.

The code base for PEGEM has diverged from earlier versions to support integration into larger frameworks and allows these frameworks to access internal, individual PEGEM capabilities. In addition, some of the current file formats, including the threat files, are updated to incorporate additional capabilities. Therefore, current threat files are no longer compatible with legacy versions such as

PEGEM v6.2.

1.3 PEGEM Overview

PEGEM provides a user-friendly platform for calculating CBRNE effects and the subsequent evolution of the hazard area for many weapon systems. PEGEM implements source term evaluation with one of two atmospheric transport codes: Vapor, Liquid, Solid Tracking (VLSTRACK) and Hazard Prediction and

Assessment Capability (HPAC). Figure 1.3-1 illustrates the missile intercept modeling capabilities of the

PEGEM simulation. The analyst specifies a CBRNE event scenario including all threat details and the locations and times of the various events. Intercept engagement lethality information is provided through the output of PEELS or via a direct interface with the PEELS Source Term Estimation

Methodology (STEM) databases. PEELS or STEM provides PEGEM with a prediction of the fraction of surviving payload following an HTK intercept event. In addition, for canister and spherical submunition payloads, PEELS provides the location of surviving submunitions within the target payload, which PEGEM uses to calculate submunition ejection velocities.

STEM is based on a multi-parameter fit to the results of thousands of PEELS runs. Thus, STEM provides a probabilistic approach to estimating fraction of payload kill (versus the deterministic output from

PEELS). STEM provides the user a faster-running estimate of payload kill and is particularly applicable when details of the engagement are unknown.

PEGEM USER’S MANUAL 1-3

FIGURE 1.3-1 PEGEM OVERVIEW

The Bomblet Submunition Flyout Module (BSFM) predicts ground impact points of Magnus rotor bomblet submunitions. The BSFM also warns the user when the conditions of bomblet thermal demise have been met.

The Canister Submunition Flyout Module (CSFM) predicts ground impact points of canister submunitions. Similarly, the Runway Cratering Munition

(RCM) Flyout Module predicts ground impact points of RCMs.

The Spherical Submunition Flyout Module (SSFM) predicts ground impact points of spherical submunitions. The SSFM also warns the user when conditions of spherical submunition thermal demise have been met.

The Ellipsoid Submunition Flyout Module (ESFM) predicts ground impact points of ellipsoid submunitions. The ESFM also warns the user when conditions of ellipsoid submunition thermal demise have been met.

The Aero-Breakup Module (ABM) characterizes the initial chemical agent source cloud for unitary chemical (UC) payload analyses. This portion of the code determines chemical agent source term geometry and droplet size distribution as a function of release conditions.

PEGEM USER’S MANUAL 1-4

Version 1.5 UNCLASSIFIED SEPTEMBER 2015

Once the initial source cloud is described, one of two atmospheric transport codes, VLSTRACK or HPAC, is used to determine ground hazard deposition and dosage. The choice of which transport code to use is left to the user. VLSTRACK was developed and is maintained by the Naval Surface Warfare Center

(NSWC) to provide approximate downwind hazard predictions for a wide range of chemical/biological agents. HPAC was developed and is maintained by the Defense Threat Reduction Agency (DTRA) to provide hazard predictions for chemical, biological, and nuclear agents and materials. As implemented in PEGEM, VLSTRACK and HPAC perform atmospheric transport and dispersion calculations using either a time- and height-variable meteorology over a flat ground plane or four-dimensional (4D) meteorology over varying terrain. Rather than integrating the VLSTRACK and HPAC source code into PEGEM, a

VLSTRACK-Driver Module (VLSTRACK-DM) is employed to set up VLSTRACK input files and run VLSTRACK externally, while an HPAC-Driver Module (HPAC-DM) is employed to set up HPAC inputs and run HPAC.

Submunition payload analyses also use VLSTRACK or HPAC to perform atmospheric transport and hazard assessment. Once the ground impact points of munitions have been determined using the appropriate flyout module, munitions are assumed to undergo normal (usually ground level) detonation. The initial source cloud from the detonation is provided to VLSTRACK or HPAC, which then calculates the resulting agent deposition, dosage, or concentration. Once ground deposition, dosage, and concentration for all threats are provided to PEGEM, the final steps are to produce hazard grids and calculate casualties.

High explosive (HE) anti-material canister submunitions and unitary high explosive (UHE) payload analyses require the PEGEM conventional weapon effects High Explosive Module (HEM) to characterize the blast overpressure and deposited fragment kinetic energy (KE) effects. This portion of the code generates overpressure and fragment KE grids in a VLSTRACK output format for common effect integration. RCM payloads produce no ground effects other than a circular damage region around each munition impact location.

Prompt effects from a nuclear weapon detonation are determined using the Simple Nuclear Application

Programs (SNAP) from DTRA’s Integrated Weapons of Mass Destruction Toolkit (IWMDT). The challenge quantities include initial nuclear radiation dose (gamma and neutron, to one minute after burst), blast peak static overpressure and thermal radiation fluence. (Nuclear radiation after one minute is handled by the HPAC fallout module.)

Analyses of mechanical debris, resulting from intercept of all threats, are performed with the PEGEM

Debris Flyout Module (DFM). The DFM utilizes KIDD v7.0.0 and KIDD Bounds to characterize debris masses, ballistic coefficients, and ejection speeds for HTK intercept of unitary and submunition threats, except for HE anti-material submunitions which KIDD does not currently support. Debris from RCM threats is modeled by KIDD and PEGEM. The DFM establishes initial ejection conditions and coordinate transformations. Once initial ejection velocities are established, debris are propagated using PEGEM’s 3-

DOF model, which includes debris lift, meteorological wind, terrain, and rotating earth effects. The debris ground impact KE grid produced by the DFM represents a keepout zone in which debris may be

PEGEM USER’S MANUAL 1-5

Version 1.5 UNCLASSIFIED SEPTEMBER 2015 contaminated with hazardous agent, and could produce hazardous effects against personnel. PEGEM bounding debris assumes a continuous area of lethal, impacting debris for defining and visualizing debris ground impact extents only. Casualties are not predicted for bounding debris.

The PEGEM Effects Integrator Module (EIM) convolves hazard grid data from various sources to produce casualty estimates. These sources include VLSTRACK or HPAC, HEM, population data, probit methodologies for assessing toxicity, overpressure, and fragment and debris KE effects. The approach for estimating casualties is either a standard probit-based methodology as recommended by Edgewood

Research Development and Engineering Center (ERDEC) (now Edgewood Chemical Biological Center) or the Statistical Casualty Model (SCM) option for deposition hazards. Chemical agent toxicity data employed by the model are derived from U.S. Army field manual FM 3-11.9 (Reference 4). Similar toxicity standards are currently being compiled for Agents of Biological Origin (ABO). Overpressure and

KE standards are also available for conventional HE agents (References 8, 9, & 10). Population data used for casualty estimations are drawn either from a database compiled by the Department of Commerce, Bureau of Census (BoC) (Reference 5), or from a database compiled by Oak Ridge National Laboratory

(ORNL) (Reference 18).

PEGEM USER’S MANUAL 2-1

Version 1.5 UNCLASSIFIED SEPTEMBER 2015

CHAPTER 2 - PEGEM GUI Installation

PEGEM v1.4 GUI Installation leverages an API interface to access the internal PEGEM capabilities.

2.1 System Requirements

Although the PEGEM APIs are cross platform, the new PEGEM GUI installation is currently limited to the

Microsoft Windows platform. The software is installed in the Program Files(x86) directory. PEGEM project, event, and output data are stored in the users My Documents\PEGEM\Projects directory.

TABLE 2.1-1 PEGEM INSTALLATION REQUIREMENTS

PEGEM Requirements

Minimum Recommended

15 GB Hard Drive Space* 30 GB Hard Drive Space*

2 GB Hard RAM 4 GB RAM

1.5 GHz Intel Architecture Processor 2.5 GHz Intel Architecture Processor

Monitor SVGA display or greater

Graphics Adapter 3D accelerated graphics, preferably NVidia or ATI, Minimum of OpenGL 2.0, least preferred is Intel Integrated graphics

PEGEM is distributed on a CDROM. To install PEGEM, check the requirements to ensure the PC is compatible with PEGEM and insert the PEGEM CD. The PEGEM installation will require administrator access. In the event the installation does not start automatically, open a window to the drive and double-click the setup.exe icon to begin installation. Once the PEGEM installer determines the system is ready, a welcome window will display (Figure 2.1-1). From there, follow the Installation Wizard instructions. Note: If you receive permissions errors, ensure you have administrator privileges. If administrator privileges have been granted, execute the setup.exe as administrator by right-clicking on setup.exe and select “Run as administrator”.

PEGEM USER’S MANUAL 2-2

FIGURE 2.1-1 PEGEM INSTALLATION

Agree to PEGEM Software Utility Agreement.

FIGURE 2.1-2 SOFTWARE UTILITY AGREEMENT

PEGEM USER’S MANUAL 2-3

Provide installation identification, organization, and key (provided separately to users).

FIGURE 2.1-3 INSTALLATION USER INFORMATION

Define the location to install the PEGEM executable. The setup defaults to the Program Files (x86) directory but the user can choose to install it to any location on the system.

FIGURE 2.1-4 INSTALLATION DIRECTORY PATH

PEGEM USER’S MANUAL 2-4

Confirm installation options and continue the installation.

FIGURE 2.1-5 INSTALLATION CONFIRMATION

PEGEM installation status is shown next. Note that the installation may take several minutes to complete.

FIGURE 2.1-6 INSTALLATION STATUS UPDATE

PEGEM USER’S MANUAL 2-5

When installation completes, Figure 2.1-7 will be displayed and the PEGEM icon will appear on the desktop.

FIGURE 2.1-7 INSTALLATION COMPLETED

PEGEM USER’S MANUAL 3-1

Version 1.5 UNCLASSIFIED SEPTEMBER 2015

CHAPTER 3 - Graphical Interface and Event Wizard

3.1 Graphical Interface and Map

The PEGEM graphical user interface (GUI) uses open source three - dimensional (3D) mapping tools for the visualization component. While the current GUI is specific to the Windows platform, all GUI components as well as the PEGEM libraries can be built on other platforms if there is a future need for such a capability.

The PEGEM GUI, shown in Figure 3.1-1, includes five primary areas, Mapping Layers, Mapping Display, Timeline, Menu and Toolbar, and the Status Bar at the bottom. The status bar displays the Latitude and

Longitude of the current mouse position when crossing the mapping. The default mapping display includes an earth model, with imagery, place names, country boundaries, and roads. Individual layers may be toggled in the Mapping Layers to the left of the map.

FIGURE 3.1-1 PEGEM USER INTERFACE

3.1.1 Manipulating the Earth

The PEGEM map supports both two dimensional and three dimensional views. The map display is driven by mouse inputs.

Left click and drag– rotates the globe.

PEGEM USER’S MANUAL 3-2

Version 1.5 UNCLASSIFIED SEPTEMBER 2015

Right click and drag – zooms the globe. Dragging up (i.e., towards the display or away from the user) zooms away from the earth’s surface. Dragging down (i.e., away from the display or towards the user) zooms into the earth. The mouse wheel may also be used for zooming.

Both Right and Left click and drag – the globe tilts and rotates about the camera focal point to a

3D perspective.

When a project is saved, the current viewpoint is saved with the project. Then, when reopening a saved project, the map will automatically zoom to the saved viewpoint of the project scenario. Similarly, the toolbar globe may be selected to reset the map to the project’s home position or to the default home position if no project is loaded.

3.1.2 Earth File

The appearance of the Earth in the PEGEM GUI is controlled via an input file called an earth file. The earth file is an input file for osgEarth (osgearth.org), an open source 3D earth rendering toolkit built on top of OpenSceneGraph (www.openscenegraph.org), an open source 3D graphics toolkit. PEGEM uses osgEarth 2.5 and OpenSceneGraph 3.2.0. The earth file defines the imagery layers, mapping layers, elevation layers, and user-defined model data to texture the surface of the globe. The earth file supports static data as well as map tile servers that dynamically load data based on the locations visible in the current view. The default earth file used in PEGEM is

<INSTALL_DIR>/bin/EarthFiles/pegem.earth, which retrieves imagery and terrain elevation data from online map servers. A couple of other example earth files are located in the same folder.

Additional examples as well as documentation on the earth file format can be obtained from the osgEarth web site.

http://www.osgearth.org/ http://www.openscenegraph.org/projects/osg

PEGEM USER’S MANUAL 3-3

Version 1.5 UNCLASSIFIED SEPTEMBER 2015

For offline use, when no networking capability is available (e.g., a classified environment), the earth file supports either using static data or using dynamically loaded data from a disk cache (the disk cache could be populated in an unclassified environment and transferred to the non-networked system).

3.1.3 Configuring PEGEM

PEGEM relies on a set of directory paths to read and write data during execution, including paths to the

PEGEM data folder, the two transport codes, the location that PEGEM projects will be stored, and the earth file to use. The PEGEM setup procedure sets all of these paths to default values. These values are stored on disk in an INI file located in the user’s application data folder. The location of this folder depends on the version of Microsoft Windows. On Windows 7 and 8, the folder is

C:/Users/<UserName>/AppData/Roaming/MDA/PEGEM.ini.

The INI file also contains some default values for displaying PEGEM results. Submunition/debris impact locations are displayed in PEGEM as colored points, while various hazard types are displayed as a set of colored contours (Figure 3.1-2). The following INI parameters are available to control some of these display settings.

TABLE 3.1-1 INI PARAMETERS

INI token Default value Definition debrisPointSize 3.0 size of the points representing debris impact locations submunitionPointSize 5.0 size of the points representing submunition impact locations rvDebrisColor 255 (red) color of RV debris impact location points kvDebrisColor 65280 (green) color of KV debris impact location points bstDebrisColor 65535 (yellow) color of booster debris impact location points subDebrisColor 32767 (orange) color of submunition impact location points shpOpacity 0.75 Level of transparency in the hazard contours. 0.0 is totally transparent. 1.0 is totally opaque.

ambientBrightness 0.75

Level of ambient lighting in the terrain model when lighting is turned on.

Note the default pegem.earth file has terrain lighting turned off. Also, some graphics cards do not support this parameter.

measureToolColor 255 (red) Color of the line drawn using the measuring tool (See Section 3.1.5.2) measureToolLineWidth 4.0 Width of line drawn using the measuring tool (See Section 3.1.5.2)

DefaultClassification

FOR OFFICIAL

USE ONLY

Default classification that gets listed for new projects on the Project Settings

Dialog (See Section 3.2.2) clampToTerrain false

Clamp impact points and hazard contours to the terrain. This requires additional computational resources but eliminates the visual effect of the contours appearing to move relative to the terrain.

useGEZoomStyle false Set the mouse scroll wheel to zoom in/out of the scene consistent with

Google Earth

PEGEM USER’S MANUAL 3-4

Version 1.5 UNCLASSIFIED SEPTEMBER 2015

For the colors, the values represent three color components (red, green, blue), each represented by a byte (values from one to 255), concatenated together into an unsigned integer (four bytes). The fourth byte would normally be used for a transparency value but it is unused for the point data. In hexadecimal, red is 0x0000FF (255), green is 0x00FF00 (65280), and blue is 0xFF0000 (16711680). For example, the default value for bstDebrisColor is 65535, which is 0x00FFFF in hexadecimal.

The shpOpacity parameter controls the amount of transparency in the PEGEM hazard contours. A value of 1.0 has no transparency while a value of zero would be totally transparent (i.e., invisible).

FIGURE 3.1-2 EXAMPLE PEGEM IMPACT POINTS AND CONTOURS

3.1.4 Contour File

When PEGEM runs and generates various types of hazard grids, a set of contours are computed from the grids and saved as ESRI shapefiles for display (Figure 3.1-2). The set of contours for each grid type is currently saved in files. There is a file with global settings and a file for project-level settings. When a new project is created, PEGEM retrieves the global contour file, located in the user’s documents folder at My Documents\PEGEM\pegem.cnt. This file contains the default set of contour levels for every new project created with PEGEM. If the file is deleted, it will be regenerated the next time a new project is created. Once this file is read for a new project, a project-level contour file is generated in the project folder at My Documents\PEGEM\<ProjectName>\<ProjectName>.cnt. This file can then be manipulated for the project without affecting other projects.

The contour file is in Extensible Markup Language (XML) format and contains a set of contours for each hazard type generated by PEGEM. An excerpt from a contour file is shown in Figure 3.1-3. Each

Contour tag represents a hazard type. The Hazard attribute identifies the three-letter string associated with that hazard type. The three-letter string is appended to the end of the name of the shapefile and will show up in the layer name in the Map Layers window when the shapefile is added to the map. The hazard types, three-letter strings and default contour settings are provided in Appendix B.

PEGEM USER’S MANUAL 3-5

Version 1.5 UNCLASSIFIED SEPTEMBER 2015

For each Contour, there is a list of ContourItem tags, which represent the contour levels. Each

ContourItem has a Value attribute, which represents the contour level, and a Color attribute. The

Value is in the units of the hazard type. The Color is an unsigned integer defined by appending red, green, and blue color components together as discussed in the previous section.

Note: As shown in Appendix B, PEGEM will generate contours in terms of lethality (i.e., probability of death) for those hazard types which support it, since that is a way of showing different hazard type effects in a common way. Therefore, for example, changing the Inhalation contours (dos) will currently have no effect since they are always shown in terms of Lethality (lth).

…