Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “software triggering”

Search indexed NASA NTRS and DOE OSTI research on propulsion, heat transfer, battery materials and energy systems. Follow report and document links to the original sources.

Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.

At least 217 records · Page 12

MaPSA Quality Control and AI-Enhanced Grading For the CMS Phase-II Tracker Upgrade

The Compact Muon Solenoid (CMS) experiment will undergo changes as part of the Large Hadron Collider upgrade. The CMS tracker will be upgraded to cope with the new radiation environment and to provide tracking at the first level trigger. This upgrade features a new type of silicon module called PS Module, which combines a Pixel sensor and a Strip sensor in the same module. The pixel portion of the PS module has a sensor bump bonded to 16 Macro Pixel ASICs (MPA) to form a Macro Pixel Sub Assembly (MaPSA). At Fermilab, MaPSAs are tested for quality control before being assembled with the strip sensors, readout and service electronics to form a PS Module. All of this test data is stored in a centralized database, and is used to grade the final module to determine if it will be installed in the detector. The Phase II Outer Tracker Analyzer of Test Outputs (POTATO) is the software that processes this data and determines the module grades. Using recent technologies, an AI agent is being im plemented into POTATO in order to allow users to more efficiently sort through the large amounts of analysis data and ensure that only the user specified data is being considered. This poster will display the process of testing a MaPSA, how that test data is relevant to module assembly and grading, and how the POTATO grading tool is being improved with the use of an embedded AI agent.

Gzamouranis, Olivia [Purdue U.]↗

Swift-BAT: The First Year of Gamma-Ray Burst Detections

The Burst Alert Telescope (BAT) on the Swift has been detecting gamma-ray bursts (GRBs) since Dec. 17,2004 and automated burst alerts have been distributed since Feb. 14,2005. Since commissioning the BAT has triggered on more than 100 GRBs, nearly all of which have been followed up by the narrow-field instruments on Swift through automatic repointing, and by ground and other satellite telescopes after rapid notification. Within seconds of a trigger the BAT produces and relays to the ground a position good to three arc minutes and a four channel light curve. A full ten minutes of event data follows on subsequent ground station passes. The burst archive has allowed us to determine ensemble burst parameters such as fluence, peak flux and duration. An overview of the properties of BAT bursts and BAT'S performance as a burst monitor will be presented in this talk. BAT is a coded aperture imaging system with a wide (approx.2 sr) field of view consisting of a large coded mask located 1 m above a 5200 cm2 array of 32.768 CdZnTe detectors. All electronics and other hardware systems on the BAT have been operating well since commissioning and there is no sign of any degradation on orbit. The flight and ground software have proven similarly robust and allow the real time localization of all bursts and the rapid derivation of burst light curves, spectra and spectral fits on the ground.

Krimm, Hans A.↗

Agent-Supported Mission Operations Teamwork

This slide presentation reviews the development of software agents to support of mission operations teamwork. The goals of the work was to make automation by agents easy to use, supervise and direct, manage information and communication to decrease distraction, interruptions, workload and errors, reduce mission impact of off-nominal situations and increase morale and decrease turnover. The accomplishments or the project are: 1. Collaborative agents - mixed initiative and creation of instructions for mediating agent 2. Methods for prototyping, evaluating and evolving socio-technical systems 3. Technology infusion: teamwork tools in mISSIons 4. Demonstrations in simulation testbed An example of the use of agent is given, the use of an agent to monitor a N2 tank leak. An incomplete instruction to the agent is handled with mediating assistants, or Intelligent Briefing and Response Assistant (IBRA). The IBRA Engine also watches data stream for triggers and executes Act-Whenever actions. There is also a Briefing and Response Instruction (BRI) which is easy for a discipline specialist to create through a BRI editor.

Malin, Jane T.↗

Precursor Analysis Report: Cyber Attack on Thyssenkrupp Blast Furnace 2014

The Cyber Attack on Thyssenkrupp Blast Furnace 2014 Precursor Analysis Report leverages publicly available information about the Thyssenkrupp Steel Mill cyber attack and catalogs anomalous observables for each technique employed in the attack. This analysis is based upon the methodology of the Cybersecurity for the Operational Technology Environment (CyOTE) program. In December 2014, the German Government’s Federal Office for Information Security (BSI) released a report detailing a cyber attack on a German steel mill that occurred earlier that year, though exact dates and details of the attack were not revealed. While the report did not specify the name of the company, multiple sources identified the victim as one of Europe’s largest steel manufacturers, Thyssenkrupp AG. Further, Thyssenkrupp announced on 16 May of that year that Europe’s largest blast furnace, “Schwelgern 2,” located at its facility in Duisburg, Germany, would be offline for several weeks for repairs and upgrades, suggesting Schwelgern 2 was likely the target of the attack. The attack began in early 2014, when adversaries infiltrated the victim steel mill’s Information Technology (IT) network via a spearphishing campaign, then worked their way into the Operational Technology (OT) environment, where they executed software that caused denial of service, denial of control, and eventually a loss of control. This led to the blast furnace shutting down without proper safety procedures, resulting in catastrophic physical damage. No lives were lost in the incident, but ThyssenKrupp suffered $4 million in damage to the blast furnace and an additional $6 million in lost revenue. The adversaries required specialized knowledge and expertise in steel production, which enabled them to compromise a variety of internal systems and components across both IT and OT networks. The attack also demonstrated detailed knowledge of the industrial control systems (ICS) and production processes being used. This combination resulted in one of the earliest known publicly reported cybersecurity incidents resulting in physical damage to ICS equipment. Researchers and analysts identified 19 unique techniques (used in a sequence of 20 steps) utilized during the attack with a total of 454 observables using MITRE ATT&CK® for Industrial Control Systems. The CyOTE program assesses observables accompanying techniques used prior to the triggering event to identify opportunities to detect malicious activity. If observables accompanying the attack techniques are perceived and investigated prior to the triggering event, earlier comprehension of malicious activity can take place. Fifteen of the identified techniques used during the Thyssenkrupp cyber attack were precursors to the triggering event. Analysis identified 369 observables associated with these precursor techniques, 316 of which were assessed to have an increased likelihood of being perceived in the 120 days preceding the triggering event. The response and comprehension time could have been reduced if the observables had been identified earlier. The information gathered in this report contributes to a library of observables tied to a repository of artifacts, data sources, and technique detection references for practitioners and developers to support the comprehension of indicators of attack. Asset owners and operators can use these products if they experience similar observables or to prepare for comparable scenarios.

45 MILITARY TECHNOLOGY, WEAPONRY, AND NATIONAL DEF↗

Deployment of ADTimePix3 areaDetector Driver at Neutron and X-ray User Facilities

TimePix3 is a 65k hybrid pixel readout chip with simultaneous Time-of-Arrival (ToA) and Time-over-Threshold (ToT) recording in each pixel*. The chip operates without a trigger signal with a sparse readout where only pixels containing events are read out. The flexible architecture allows 40 MHits/s/cm² readout throughput, using simultaneous readout and acquisition by sharing readout logic with transport logic of superpixel matrix formed using 2x4 structure. The chip ToA records 1.5625 ns time resolution. The X-ray and charged particle events are counted directly. However, indirect neutron counts use 6Li fission in a scintillator matrix, such as ZnS(Ag). The fission space-charge region is limited to 5-9 um. A photon from scintillator material excites a photocathode electron, which is further multiplied in dual-stack MCP. The neutron count event is a cluster of electron events at the chip. We report on the EPICS areaDetector** ADTimePix3 driver that controls Serval*** using json commands. The driver directs data to storage and to a real-time processing pipeline and configures the chip. The time-stamped data are stored in raw .tpx3 file format and passed through a socket where the clustering software identifies individual neutron events. The conventional 2D images are available as images for each exposure frame, and a preview is useful for sample alignment. The areaDetector driver allows integration of time-enhanced capabilities of this detector into SNS beamlines controls and unprecedented time resolution.

Gofron, Kaz↗

Complex Event Recognition Architecture

Complex Event Recognition Architecture (CERA) is the name of a computational architecture, and software that implements the architecture, for recognizing complex event patterns that may be spread across multiple streams of input data. One of the main components of CERA is an intuitive event pattern language that simplifies what would otherwise be the complex, difficult tasks of creating logical descriptions of combinations of temporal events and defining rules for combining information from different sources over time. In this language, recognition patterns are defined in simple, declarative statements that combine point events from given input streams with those from other streams, using conjunction, disjunction, and negation. Patterns can be built on one another recursively to describe very rich, temporally extended combinations of events. Thereafter, a run-time matching algorithm in CERA efficiently matches these patterns against input data and signals when patterns are recognized. CERA can be used to monitor complex systems and to signal operators or initiate corrective actions when anomalous conditions are recognized. CERA can be run as a stand-alone monitoring system, or it can be integrated into a larger system to automatically trigger responses to changing environments or problematic situations.

Fitzgerald, William A.↗

Creating Interactive Graphical Overlays in the Advanced Weather Interactive Processing System Using Shapefiles and DGM Files

Graphical overlays can be created in real-time in the Advanced Weather Interactive Processing System (AWIPS) using shapefiles or Denver AWIPS Risk Reduction and Requirements Evaluation (DARE) Graphics Metafile (DGM) files. This presentation describes how to create graphical overlays on-the-fly for AWIPS, by using two examples of AWIPS applications that were created by the Applied Meteorology Unit (AMU) located at Cape Canaveral Air Force Station (CCAFS), Florida. The first example is the Anvil Threat Corridor Forecast Tool, which produces a shapefile that depicts a graphical threat corridor of the forecast movement of thunderstorm anvil clouds, based on the observed or forecast upper-level winds. This tool is used by the Spaceflight Meteorology Group (SMG) at Johnson Space Center, Texas and 45th Weather Squadron (45 WS) at CCAFS to analyze the threat of natural or space vehicle-triggered lightning over a location. The second example is a launch and landing trajectory tool that produces a DGM file that plots the ground track of space vehicles during launch or landing. The trajectory tool can be used by SMG and the 45 WS forecasters to analyze weather radar imagery along a launch or landing trajectory. The presentation will list the advantages and disadvantages of both file types for creating interactive graphical overlays in future AWIPS applications. Shapefiles are a popular format used extensively in Geographical Information Systems. They are usually used in AWIPS to depict static map backgrounds. A shapefile stores the geometry and attribute information of spatial features in a dataset (ESRI 1998). Shapefiles can contain point, line, and polygon features. Each shapefile contains a main file, index file, and a dBASE table. The main file contains a record for each spatial feature, which describes the feature with a list of its vertices. The index file contains the offset of each record from the beginning of the main file. The dBASE table contains records for each attribute. Attributes are commonly used to label spatial features. Shapefiles can be viewed, but not created in AWIPS. As a result, either third-party software can be installed on an AWIPS workstation, or new software must be written to create shapefiles in the correct format.

Barrett, Joe H., III↗

In search of Nemesis

The parallax of all stars of visual magnitude greater than about 6.5 has already been measured. If Nemesis is a main-sequence star 1 parsec away, this requires Nemesis's mass to be less than about 0.4 solar masses. If it were less than about 0.05 solar masses its gravity would be too weak to trigger a comet storm. If Nemesis is on the main sequence, this mass range requires it to be a red dwarf. A red dwarf companion would probably have been missed by standard astronomical surveys. Nearby stars are usually found because they are bright or have high proper motion. However, Nemesis's proper motion would now be 0.01 arcsec/yr, and if it is a red dwarf its magnitude is about 10 - too dim to attract attention. Unfortunately, standard four-color photometry does not distinguish between red dwarfs and giants. So although surveys such as the Dearborn Red Star Catalog list stars by magnitude and spectral type, they do not identify the dwarfs. Every star of the correct spectral type and magnitude must be scrutinized. Our candidate list is a hybrid; candidate red stars are identified in the astrometrically poor Dearborn Red Star Catalog and their positions are corrected using the Hubble Guide Star Catalog. When errors in the Dearborn catalog make it impossible to identify the corresponding Hubble star, the fields are split so that we have one centering on each possible candidate. We are currently scrutinizing 3098 fields, which we believe contain all possible red dwarf candidates in the northern hemisphere. Since our last report the analysis and database software has been completely rebuilt to take advantage of updated hardware, to make the data more accessible, and to implement improved methods of data analysis. The software is now completed and we are eliminating stars every clear night.

Carlson, S.↗

BioSentinel: Mission Development of a Radiation Biosensor to Gauge DNA Damage and Repair Beyond Low Earth Orbit on a 6U Nanosatellite.

We are designing and developing a "6U" (10 x 22 x 34 cm; 14 kg) nanosatellite as a secondary payload to fly aboard NASA's Space Launch System (SLS) Exploration Mission (EM) 1, scheduled for launch in late 2017. For the first time in over forty years, direct experimental data from biological studies beyond low Earth orbit (LEO) will be obtained during BioSentinel's 12- to 18- month mission. BioSentinel will measure the damage and repair of DNA in a biological organism and allow us to compare that to information from onboard physical radiation sensors. In order to understand the relative contributions of the space environment's two dominant biological perturbations, reduced gravity and ionizing radiation, results from deep space will be directly compared to data obtained in LEO (on ISS) and on Earth. These data points will be available for validation of existing biological radiation damage and repair models, and for extrapolation to humans, to assist in mitigating risks during future long-term exploration missions beyond LEO. The BioSentinel Payload occupies 4U of the spacecraft and will utilize the monocellular eukaryotic organism Saccharomyces cerevisiae (yeast) to report DNA double-strand-break (DSB) events that result from ambient space radiation. DSB repair exhibits striking conservation of repair proteins from yeast to humans. Yeast was selected because of 1) its similarity to cells in higher organisms, 2) the well-established history of strains engineered to measure DSB repair, 3) its spaceflight heritage, and 4) the wealth of available ground and flight reference data. The S. cerevisiae flight strain will include engineered genetic defects to prevent growth and division until a radiation-induced DSB activates the yeast's DNA repair mechanisms. The triggered culture growth and metabolic activity directly indicate a DSB and its successful repair. The yeast will be carried in the dry state within the 1-atm P/L container in 18 separate fluidics cards with each card having 16 independent culture microwells, with integral microchannels and filters to supply nutrients and reagents, confine the yeast to the wells, and enable optical measurement. The measurement subsystem will monitor each subgroup of culture wells continuously for several weeks, optically tracking DSBtriggered cell growth and metabolism. BioSentinel will also include physical radiation sensors based on the TimePix sensor, as implemented by JSC's RadWorks group, which record individual radiation events including estimates of their linear-energytransfer (LET) values. Radiation-dose and LET data will be compared directly to the rate of DSB-and-repair events measured by the S. cerevisiae biosentinels. The spacecraft bus will operate in a deep space environment with functions that include command and data handling, communications, power generation (via deployable solar panels) and storage, and attitude determination-and-control system with micropropulsion. Development of the BioSentinel spacecraft will mature and prove multiple nanosatellite advances in order to function well beyond LEO: Communications from distances of ≥ 500,000 km; Autonomous attitude control, momentum management, and safe mode of nanosatellites in deep space; Shielding-, hardening-, design-, and software-derived radiation tolerance for electronics; Reliable functionality for 12 - 18 months of key subsystems for biofluidics, memory, communications, power, etc.; Close integration of living biological radiation event monitors with miniature physical radiation spectrometers; Biological measurement of solar particle events beyond Earth orbit In addition to providing the first biological results from beyond LEO in over 4 decades, BioSentinel will provide an adaptable small-satellite instrument platform to perform a range of human-exploration-relevant measurements that characterize the biological consequences of multiple outer space environments. BioSentinel is being developed under NASA's Advanced Exploration Systems program.

DNA damage↗

Stochastic Continuous-time Flexibility Scheduling and Pricing in Wholesale Electricity Markets

Large-scale integration of intermittent renewable energy sources (RES) is calling for additional flexibility resources as well as more advanced modeling and optimization techniques to account for the increasing uncertainty and variability in power systems operation. As the RES integration gains momentum, the magnitude and frequency of their variations increase, which may trigger ramping scarcity events in real-time power systems operation. This necessitates revisiting the present definition of power systems flexibility and reserve services to reflect their robustness and adequacy towards sub-interval variations of the load and RES, as well as adjusting the operation models to accommodate the new reserve services. This project took a fundamental approach and aimed at developing continuous-time scheduling and pricing model that accurately models the continuous-time variations of load and RES and efficiently deploys the ramping capability of flexible resources to compensate the sources of variability and uncertainty in the market. In this regard, this project pursued the following goals: Developing stochastic multi-fidelity continuous-time optimization models for scheduling of energy storage (ES) systems and flexible loads in wholesale energy markets; Developing the theory and practices of continuous-time locational marginal pricing for valuating energy storage systems and flexible loads in wholesale energy markets; Developing function space solution approach to convert the proposed stochastic multi-fidelity continuous-time optimization models into tractable mixed-integer linear optimization models; and Defining flexibility reserve as a new type of reserve in markets that would enable ultimate participation of energy storage devices in provision of services to compensate the variability and uncertainty of RES in electricity markets. This project successfully completed all five major tasks defined in the SOPO, and produced 8 high-impact journal papers, 6 conference papers, 3 published U.S. patents, and one web-based software for continuous-time operation optimization of power systems. The application of the proposed flexibility reserve and the stochastic multi-fidelity continuous-time operation scheduling models would modify the forward commitment and schedule of generating units, ES devices and flexible loads, and would line up the resources in such a way that the composition of available resources is better prepared to respond to the sub-hourly variations of the load and renewable resources in real-time operation. Therefore, this project paves the way to sustainable, reliable, and economic integration of renewable energy resources in power system, supporting the progress towards reaching the national targets on energy independence. Even if the proposed models offers a radically different point of view as compared to existing models, it does not alter fundamentally the architecture of power systems operations, nor the complexity of the scheduling problem, so the integration of this project in power systems is extremely practical.

24 POWER TRANSMISSION AND DISTRIBUTION↗

Hypercars: The next industrial revolution

The auto industry -- one-seventh of the GNP, and the highest expression of the Iron Age -- is about to trigger the biggest transformation in industrial structure since the microchip. Ultralight cars molded from net-shape advanced composites can be several-fold lighter than present steel cars, yet safer, sportier, and more comfortable, durable, and beautiful. Modern hybrid-electric drives boost efficiency approximately 1.3-1.5x in heavy steel cars, but approximately 5-20x in ultralight, very slippery plafforms. Synergistically combined into ultralight-hybrid 'hypercars,' these elements can yield state-of-the-shelf family cars that average 150-300+ mi/gal -- twice that with state-of-the-art technologies -- yet can also be superior in all other respects, probably including cost: carbon-fiber monocoques can actually be cheaper to mass-produce that steel unibodies. Designing cars more like aircraft and less like tanks requires not only an approximately 400-500 kg curb mass and very low air and road drag, but also an aerospace philosophy of engineering integration. Mass, cost, and complexity turn out to compound with heavy hybrids but to decompound with ultralight hybrids, owing partly to radical simplification. Excellent aerodynamics, preferable including advanced techniques for passive boundary-layer control, will be the key to successful design integration. Transforming automaking is a competitive and environmental imperative, could form the nucleus of a green industrial Renaissance, and would enhance national security by, among other things, saving as much oil as OPEC now extracts. However, this transformation faces serious cultural barriers. For example, hypercars will be more like computers with wheels than like cars with chips -- they'll have an order of magnitude more code than today's cars -- but Detroit is not a software culture. Just the transition from stamped and welded steel to integrated and adhesive-joined synthetics is difficult enough. Nonetheless, hypercars are rapidly heading to market in the late 1990s, because approximately 25 current and intending automakers are eager to capture their potentially decisive competitive advantages -- including order-of-magnitude reductions in product cycle time, tooling cost, assembly effort, and parts count. Hypercars will succeed, and may well sweep the market, not because of mandates or subsidies, but because of manufacturers' quest for competitive advantage and customers' desire for better, smarter cars.

Lovins, Amory B.↗

Fault Tolerance Middleware for a Multi-Core System

Fault Tolerance Middleware (FTM) provides a framework to run on a dedicated core of a multi-core system and handles detection of single-event upsets (SEUs), and the responses to those SEUs, occurring in an application running on multiple cores of the processor. This software was written expressly for a multi-core system and can support different kinds of fault strategies, such as introspection, algorithm-based fault tolerance (ABFT), and triple modular redundancy (TMR). It focuses on providing fault tolerance for the application code, and represents the first step in a plan to eventually include fault tolerance in message passing and the FTM itself. In the multi-core system, the FTM resides on a single, dedicated core, separate from the cores used by the application. This is done in order to isolate the FTM from application faults and to allow it to swap out any application core for a substitute. The structure of the FTM consists of an interface to a fault tolerant strategy module, a responder module, a fault manager module, an error factory, and an error mapper that determines the severity of the error. In the present reference implementation, the only fault tolerant strategy implemented is introspection. The introspection code waits for an application node to send an error notification to it. It then uses the error factory to create an error object, and at this time, a severity level is assigned to the error. The introspection code uses its built-in knowledge base to generate a recommended response to the error. Responses might include ignoring the error, logging it, rolling back the application to a previously saved checkpoint, swapping in a new node to replace a bad one, or restarting the application. The original error and recommended response are passed to the top-level fault manager module, which invokes the response. The responder module also notifies the introspection module of the generated response. This provides additional information to the introspection module that it can use in generating its next response. For example, if the responder triggers an application rollback and errors are still occurring, the introspection module may decide to recommend an application restart.

Some, Raphael R.↗

Trick Simulation Environment 07

The Trick Simulation Environment is a generic simulation toolkit used for constructing and running simulations. This release includes a Monte Carlo analysis simulation framework and a data analysis package. It produces all auto documentation in XML. Also, the software is capable of inserting a malfunction at any point during the simulation. Trick 07 adds variable server output options and error messaging and is capable of using and manipulating wide characters for international support. Wide character strings are available as a fundamental type for variables processed by Trick. A Trick Monte Carlo simulation uses a statistically generated, or predetermined, set of inputs to iteratively drive the simulation. Also, there is a framework in place for optimization and solution finding where developers may iteratively modify the inputs per run based on some analysis of the outputs. The data analysis package is capable of reading data from external simulation packages such as MATLAB and Octave, as well as the common comma-separated values (CSV) format used by Excel, without the use of external converters. The file formats for MATLAB and Octave were obtained from their documentation sets, and Trick maintains generic file readers for each format. XML tags store the fields in the Trick header comments. For header files, XML tags for structures and enumerations, and the members within are stored in the auto documentation. For source code files, XML tags for each function and the calling arguments are stored in the auto documentation. When a simulation is built, a top level XML file, which includes all of the header and source code XML auto documentation files, is created in the simulation directory. Trick 07 provides an XML to TeX converter. The converter reads in header and source code XML documentation files and converts the data to TeX labels and tables suitable for inclusion in TeX documents. A malfunction insertion capability allows users to override the value of any simulation variable, or call a malfunction job, at any time during the simulation. Users may specify conditions, use the return value of a malfunction trigger job, or manually activate a malfunction. The malfunction action may consist of executing a block of input file statements in an action block, setting simulation variable values, call a malfunction job, or turn on/off simulation jobs.

Lin, Alexander S.↗

Volume Averaged Height Integrated Radar Reflectivity (VAHIRR) Cost-Benefit Analysis

Lightning Launch Commit Criteria (LLCC) are designed to prevent space launch vehicles from flight through environments conducive to natural or triggered lightning and are used for all U.S. government and commercial launches at government and civilian ranges. They are maintained by a committee known as the NASA/USAF Lightning Advisory Panel (LAP). The previous LLCC for anvil cloud, meant to avoid triggered lightning, have been shown to be overly restrictive. Some of these rules have had such high safety margins that they prohibited flight under conditions that are now thought to be safe 90% of the time, leading to costly launch delays and scrubs. The LLCC for anvil clouds was upgraded in the summer of 2005 to incorporate results from the Airborne Field Mill (ABFM) experiment at the Eastern Range (ER). Numerous combinations of parameters were considered to develop the best correlation of operational weather observations to in-cloud electric fields capable of rocket triggered lightning in anvil clouds. The Volume Averaged Height Integrated Radar Reflectivity (VAHIRR) was the best metric found. Dr. Harry Koons of Aerospace Corporation conducted a risk analysis of the VAHIRR product. The results indicated that the LLCC based on the VAHIRR product would pose a negligible risk of flying through hazardous electric fields. Based on these findings, the Kennedy Space Center Weather Office is considering seeking funding for development of an automated VAHIRR algorithm for the new ER 45th Weather Squadron (45 WS) RadTec 431250 weather radar and Weather Surveillance Radar-1988 Doppler (WSR-88D) radars. Before developing an automated algorithm, the Applied Meteorology Unit (AMU) was tasked to determine the frequency with which VAHIRR would have allowed a launch to safely proceed during weather conditions otherwise deemed "red" by the Launch Weather Officer. To do this, the AMU manually calculated VAHIRR values based on candidate cases from past launches with known anvil cloud LLCC violations. An automated algorithm may be developed if the analyses from past launches show VAHIRR would have provided a significant cost benefit by allowing a launch to proceed. The 45 WS at the ER and 30th Weather Squadron (30 WS) at the Western Range provided the AMU with launch weather summaries from past launches that were impacted by LLCC. The 45 WS provided summaries from 14 launch attempts and the 30 WS fkom 5. The launch attempts occurred between December 2001 and June 2007. These summaries helped the AMU determine when the LLCC were "red" due to anvil cloud. The AMU collected WSR-88D radar reflectivity, cloud-to-ground lightning strikes, soundings and satellite imagery. The AMU used step-by-step instructions for calculating VAHIRR manually as provided by the 45 WS. These instructions were used for all of the candidate cases when anvil cloud caused an LLCC violation identified in the launch weather summaries. The AMU evaluated several software programs capable of visualizing radar data so that VAHIRR could be calculated and chose GR2Analyst from Gibson Ridge Software, LLC. Data availability and lack of detail from some launch weather summaries permitted analysis of six launch attempts from the ER and none from the WR. The AMU did not take into account whether or not other weather LCC violations were occurring at the same time as the anvil cloud LLCC since the goal of this task was to determine how often VAHIRR provided relief to the anvil cloud LLCC at any time during several previous launch attempts. Therefore, in the statistics presented in this report, it is possible that even though VAHIRR provided relief to the anvil cloud LLCC, other weather LCC could have been violated not permitting the launch to proceed. The results of this cost-benefit analysis indicated VAHIRR provided relief from the anvil cloud LLCC between about 15% and 18% of the time for varying 5-minute time periods based on summaries fkom six launch attempts and would have allowed launch to proceed that were otherwise "NO GO" due to the anvil cloud LLCC if the T-0 time occurred during the anvil cloud LLCC violations.

Bauman, William H., III↗

Soft Decision Analyzer

The Soft Decision Analyzer (SDA) is an instrument that combines hardware, firmware, and software to perform realtime closed-loop end-to-end statistical analysis of single- or dual- channel serial digital RF communications systems operating in very low signal-to-noise conditions. As an innovation, the unique SDA capabilities allow it to perform analysis of situations where the receiving communication system slips bits due to low signal-to-noise conditions or experiences constellation rotations resulting in channel polarity in versions or channel assignment swaps. SDA s closed-loop detection allows it to instrument a live system and correlate observations with frame, codeword, and packet losses, as well as Quality of Service (QoS) and Quality of Experience (QoE) events. The SDA s abilities are not confined to performing analysis in low signal-to-noise conditions. Its analysis provides in-depth insight of a communication system s receiver performance in a variety of operating conditions. The SDA incorporates two techniques for identifying slips. The first is an examination of content of the received data stream s relation to the transmitted data content and the second is a direct examination of the receiver s recovered clock signals relative to a reference. Both techniques provide benefits in different ways and allow the communication engineer evaluating test results increased confidence and understanding of receiver performance. Direct examination of data contents is performed by two different data techniques, power correlation or a modified Massey correlation, and can be applied to soft decision data widths 1 to 12 bits wide over a correlation depth ranging from 16 to 512 samples. The SDA detects receiver bit slips within a 4 bits window and can handle systems with up to four quadrants (QPSK, SQPSK, and BPSK systems). The SDA continuously monitors correlation results to characterize slips and quadrant change and is capable of performing analysis even when the receiver under test is subjected to conditions where its performance degrades to high error rates (30 percent or beyond). The design incorporates a number of features, such as watchdog triggers that permit the SDA system to recover from large receiver upsets automatically and continue accumulating performance analysis unaided by operator intervention. This accommodates tests that can last in the order of days in order to gain statistical confidence in results and is also useful for capturing snapshots of rare events.

Steele, Glen↗

Orion MPCV Touchdown Detection Threshold Development and Testing

A robust method of detecting Orion Multi ]Purpose Crew Vehicle (MPCV) splashdown is necessary to ensure crew and hardware safety during descent and after touchdown. The proposed method uses a triple redundant system to inhibit Reaction Control System (RCS) thruster firings, detach parachute risers from the vehicle, and transition to the post ]landing segment of the Flight Software (FSW). The vehicle crew is the prime input for touchdown detection, followed by an autonomous FSW algorithm, and finally a strictly time based backup timer. RCS thrusters must be inhibited before submersion in water to protect against possible damage due to firing these jets under water. In addition, neglecting to declare touchdown will not allow the vehicle to transition to post ]landing activities such as activating the Crew Module Up ]righting System (CMUS), resulting in possible loss of communication and difficult recovery. A previous AIAA paper gAssessment of an Automated Touchdown Detection Algorithm for the Orion Crew Module h concluded that a strictly Inertial Measurement Unit (IMU) based detection method using an acceleration spike algorithm had the highest safety margins and shortest detection times of other methods considered. That study utilized finite element simulations of vehicle splashdown, generated by LS ]DYNA, which were expanded to a larger set of results using a Kriging surface fit. The study also used the Decelerator Systems Simulation (DSS) to generate flight dynamics during vehicle descent under parachutes. Proto ]type IMU and FSW MATLAB models provided the basis for initial algorithm development and testing. This paper documents an in ]depth trade study, using the same dynamics data and MATLAB simulations as the earlier work, to further develop the acceleration detection method. By studying the combined effects of data rate, filtering on the rotational acceleration correction, data persistence limits and values of acceleration thresholds, an optimal configuration was determined. The lever arm calculation, which removes the centripetal acceleration caused by vehicle rotation, requires that the vehicle angular acceleration be derived from vehicle body rates, necessitating the addition of a 2nd order filter to smooth the data. It was determined that using 200 Hz data directly from the vehicle IMU outperforms the 40 Hz FSW data rate. Data persistence counter values and acceleration thresholds were balanced in order to meet desired safety and performance. The algorithm proved to exhibit ample safety margin against early detection while under parachutes, and adequate performance upon vehicle splashdown. Fall times from algorithm initiation were also studied, and a backup timer length was chosen to provide a large safety margin, yet still trigger detection before CMUS inflation. This timer serves as a backup to the primary acceleration detection method. Additionally, these parameters were tested for safety on actual flight test data, demonstrating expected safety margins.

Daum, Jared↗

BatAnalysis - A Comprehensive Python Pipeline for Swift BAT Survey Analysis

The Swift Burst Alert Telescope (BAT) is a coded-aperture gamma-ray instrument with a large field of view that primarily operates in survey mode when it is not triggering on transient events. The survey data consist of 80-channel detector plane histograms that accumulate photon counts over periods of at least 5 minutes. These histograms are processed on the ground and are used to produce the survey data set between 14 and 195 keV. Survey data comprise >90% of all BAT data by volume and allow for the tracking of long-term light curves and spectral properties of cataloged and uncataloged hard X-ray sources. Until now, the survey data set has not been used to its full potential due to the complexity associated with its analysis and the lack of easily usable pipelines. Here, we introduce the BatAnalysis Python package, a wrapper for HEASoftpy, which provides a modern, open-source pipeline to process and analyze BAT survey data. BatAnalysis allows members of the community to use BAT survey data in more advanced analyses of astrophysical sources, including pulsars, pulsar wind nebula, active galactic nuclei, and other known/unknown transient events that may be detected in the hard X-ray band. We outline the steps taken by the Python code and exemplify its usefulness and accuracy by analyzing survey data of the Crab Nebula, NGC 2992, and a previously uncataloged MAXI transient. The BatAnalysis package allows for ~18 yr of BAT survey data to be used in a systematic way to study a large variety of astrophysical sources.

79 ASTRONOMY AND ASTROPHYSICS↗

Aging of galaxies along the morphological sequence, marked by bulge growth and disk quenching

Aims: We revisit the color bimodality of galaxies using the extensive EFIGI morphological classification of nearby galaxies. Methods: The galaxy profiles from the Sloan Digital Sky Survey (SDSS) gri images were decomposed as a bulge and a disk by controlled profile modeling with the Euclid SourceXtractor++ software. The spectral energy distributions from our resulting gri SDSS photometry complemented with Galaxy Evolution Explorer (GALEX) NUV photometry were fitted with the ZPEG software and PEGASE.2 templates in order to estimate the stellar masses and specific star formation rates (sSFR) of whole galaxies as well as their bulge and disk components. Results: The absolute NUV-r color versus stellar mass diagram shows a continuous relationship between the present sSFR of galaxies and their stellar mass, which spans all morphological types of the Hubble sequence monotonously. Irregular galaxies to intermediate-type Sab spirals make up the “Blue Cloud” across 4 orders of magnitude in stellar mass but a narrow range of sSFR. This mass build-up of spiral galaxies requires major mergers, in agreement with their frequently perturbed isophotes. At high mass, the Blue Cloud leads to the “Green Plain”, dominated by S0a and Sa early-type spirals. It was formerly called the “Green Valley”, due to its low density, but we rename it because of its wide stretch and nearly flat density over ~2 mag in NUV-r color (hence sSFR), despite a limited range of stellar mass (1 order of magnitude). The Green Plain links up the “Red Sequence”, containing all lenticular and elliptical galaxies with a 2 order of magnitude mass interval, and systematically higher masses for the ellipticals. We confirm that the Green Plain cannot be studied using u - r optical colors because it is overlayed by the Red Sequence, hence NUV data are necessary. Galaxies across the Green Plain undergo a marked growth by a factor 2 to 3 in their bulge-to-total mass ratio and a systematic profile change from pseudo to classical bulges, as well as a significant reddening due to star formation fading in their disks. The Green Plain is also characterized by a maximum stellar mass of 10 11.7 M ⊙ beyond which only elliptical galaxies exist, hence supporting the scenario of ellipticals partly forming by major mergers of massive disk galaxies. Conclusions: The EFIGI attributes indicate that dynamical processes (spiral arms and isophote distortions) contribute to the scatter of the Main Sequence of star-forming galaxies (Blue Cloud), via the enhancement of star formation (flocculence, HII regions). The significant bulge growth across the Green Plain confirms that it is a transition region, and excludes a predominantly quick transit due to rapid quenching. The high frequency of bars for all spirals as well as the stronger spiral arms and flocculence in the knee of the Green Plain suggest that internal dynamics, likely triggered by flybys or (mainly minor) mergers, may be the key to the bulge growth of massive disk galaxies, which is a marker of the aging of galaxies from star forming to quiescence. The Hubble sequence can then be considered as an inverse sequence of galaxy physical evolution.

79 ASTRONOMY AND ASTROPHYSICS↗