Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “VIOLATIONS”

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 685 records · Page 38

Gamma-Ray, Cosmic Ray and Neutrino Tests of Lorentz Invariance and Quantum Gravity Models

High-energy astrophysics observations provide the best possibilities to detect a very small violation of Lorentz invariance such as may be related to the structure of space-time near the Planck scale of approximately 10(exp -35) m. I will discuss here the possible signatures of Lorentz invariance violation (LIV) from observations of the spectra, polarization, and timing of gamma-rays from active galactic nuclei and gamma-ray bursts. Other sensitive tests are provided by observations of the spectra of ultrahigh energy cosmic rays and neutrinos. Using the latest data from the Pierre Auger Observatory one can already derive an upper limit of 4.5 x 10(exp -23) to the amount of LIV of at a proton Lorentz factor of approximately 2 x 10(exp 11). This result has fundamental implications for quantum gravity models. I will also discuss the possibilities of using more sensitive space based detection techniques to improve searches for LIV in the future.

Stecker, Floyd↗

High Energy Astrophysics Tests of Lorentz Invariance and Quantum Gravity Models

High-energy astrophysics observations provide the best possibilities to detect a very small violation of Lorentz invariance such as may be related to the structure of space-time near the Planck scale of approximately 10-35 m. I will discuss here the possible signatures of Lorentz invariance violation (LIV) from observations of the spectra, polarization, and timing of gamma-rays from active galactic nuclei and gamma-ray bursts. Other sensitive tests are provided by observations ofthe spectra of ultrahigh energy cosmic rays and neutrinos. Using the latest data from the Pierre Auger Observatory one can already derive an upper limit of 4.5 x 10(exp -23) to the amount of LIV at a proton Lorentz factor of -2 x 10(exp 11). This result has fundamental implications for quantum gravity models. I will also discuss the possibilities of using more sensitive space based detection techniques to improve searches for LIV in the future.

Stecker, Floyd W.↗

Peak Wind Forecasts for the Launch-Critical Wind Towers on Kennedy Space Center/Cape Canaveral Air Force Station, Phase IV

This final report describes the development of a peak wind forecast tool to assist forecasters in determining the probability of violating launch commit criteria (LCC) at Kennedy Space Center (KSC) and Cape Canaveral Air Force Station (CCAFS). The peak winds arc an important forecast clement for both the Space Shuttle and Expendable Launch Vehicle (ELV) programs. The LCC define specific peak wind thresholds for each launch operation that cannot be exceeded in order to ensure the safety of the vehicle. The 45th Weather Squadron (45 WS) has found that peak winds are a challenging parameter to forecast, particularly in the cool season months of October through April. Based on the importance of forecasting peak winds, the 45 WS tasked the Applied Meteorology Unit (AMU) to update the statistics in the current peak-wind forecast tool to assist in forecasting LCC violations. The tool includes onshore and offshore flow climatologies of the 5-minute mean and peak winds and probability distributions of the peak winds as a function of the 5-minute mean wind speeds.

Crawford, Winifred↗

Launch Commit Criteria Monitoring Agent

The Spaceport Processing Systems Branch at NASA Kennedy Space Center has developed and deployed a software agent to monitor the Space Shuttle's ground processing telemetry stream. The application, the Launch Commit Criteria Monitoring Agent, increases situational awareness for system and hardware engineers during Shuttle launch countdown. The agent provides autonomous monitoring of the telemetry stream, automatically alerts system engineers when predefined criteria have been met, identifies limit warnings and violations of launch commit criteria, aids Shuttle engineers through troubleshooting procedures, and provides additional insight to verify appropriate troubleshooting of problems by contractors. The agent has successfully detected launch commit criteria warnings and violations on a simulated playback data stream. Efficiency and safety are improved through increased automation.

Semmel, Glenn S.↗

Autonomous Flight Safety System September 27, 2005, Aircraft Test

This report describes the first aircraft test of the Autonomous Flight Safety System (AFSS). The test was conducted on September 27, 2005, near Kennedy Space Center (KSC) using a privately-owned single-engine plane and evaluated the performance of several basic flight safety rules using real-time data onboard a moving aerial vehicle. This test follows the first road test of AFSS conducted in February 2005 at KSC. AFSS is a joint KSC and Wallops Flight Facility (WEF) project that is in its third phase of development. AFSS is an independent subsystem intended for use with Expendable Launch Vehicles that uses tracking data from redundant onboard sensors to autonomously make flight termination decisions using software-based rules implemented on redundant flight processors. The goals of this project are to increase capabilities by allowing launches from locations that do not have or cannot afford extensive ground-based range safety assets, to decrease range costs, and to decrease reaction time for special situations. The mission rules are configured for each operation by the responsible Range Safety authorities and can be loosely categorized in four major categories: Parameter Threshold Violations, Physical Boundary Violations present position and instantaneous impact point (TIP), Gate Rules static and dynamic, and a Green-Time Rule. Examples of each of these rules were evaluated during this aircraft test.

Simpson, James C.↗

High Energy Astrophysics Tests of Lorentz Invariance and Quantum Gravity Models

High energy astrophysics observations provide the best possibilities to detect a very small violation of Lorentz invariance such as may be related to the structure of space-time near the Planck scale of approximately 10(exp -35)m. I will discuss the possible signatures of Lorentz invariance violation (LIV) that can be manifested by observing of the spectra, polarization, and timing of gamma-rays from active galactic nuclei and y-ray bursts. Other sensitive tests are provided by observations of the spectra of ultrahigh energy cosmic rays and neutrinos. Using the latest data from the Pierre Auger Observatory one can already derive an upper limit of 4.5 x 10(exp -23) on the fraction of LIV at a Lorentz factor of approximately 2 x 10(exp 11). This result has fundamental implications for quantum gravity models. I will also discuss the possibilities of using more sensitive space-based detection techniques to improve searches for LIV in the future.

Stecker, F. W.↗

TraceContract

TraceContract is an API (Application Programming Interface) for trace analysis. A trace is a sequence of events, and can, for example, be generated by a running program, instrumented appropriately to generate events. An event can be any data object. An example of a trace is a log file containing events that a programmer has found important to record during a program execution. Trace - Contract takes as input such a trace together with a specification formulated using the API and reports on any violations of the specification, potentially calling code (reactions) to be executed when violations are detected. The software is developed as an internal DSL (Domain Specific Language) in the Scala programming language. Scala is a relatively new programming language that is specifically convenient for defining such internal DSLs due to a number of language characteristics. This includes Scala s elegant combination of object-oriented and functional programming, a succinct notation, and an advanced type system. The DSL offers a combination of data-parameterized state machines and temporal logic, which is novel. As an extension of Scala, it is a very expressive and convenient log file analysis framework.

Kavelund, Klaus↗

Plug-in Plan Tool v3.0.3.1

The role of PLUTO (Plug-in Port UTilization Officer) and the growth of the International Space Station (ISS) have exceeded the capabilities of the current tool PiP (Plug-in Plan). Its users (crew and flight controllers) have expressed an interest in a new, easy-to-use tool with a higher level of interactivity and functionality that is not bound by the limitations of Excel. The PiP Tool assists crewmembers and ground controllers in making real-time decisions concerning the safety and compatibility of hardware plugged into the UOPs (Utility Outlet Panels) onboard the ISS. The PiP Tool also provides a reference to the current configuration of the hardware plugged in to the UOPs, and enables the PLUTO and crew to test Plug-in locations for constraint violations (such as cable connector mismatches or amp limit violations), to see the amps and volts for an end item, to see whether or not the end item uses 1553 data, and the cable length between the outlet and the end item. As new equipment is flown or returned, the database can be updated appropriately as needed. The current tool is a macroheavy Excel spreadsheet with its own database and reporting functionality. The new tool captures the capabilities of the original tool, ports them to new software, defines a new dataset, and compensates for ever-growing unique constraints associated with the Plug-in Plan. New constraints were designed into the tool, and updates to existing constraints were added to provide more flexibility and customizability. In addition, there is an option to associate a "Flag" with each device that will let the user know there is a unique constraint associated with it when they use it. This helps improve the safety and efficiency of real-time calls by limiting the amount of "corporate knowledge" overhead that has to be trained and learned through use. The tool helps save time by automating previous manual processes, such as calculating connector types and deciding which cables are required and in what order.

Andrea-Liner, Kathleen E.↗

Vandenberg Air Force Base Upper Level Wind Launch Weather Constraints

The 30th Operational Support Squadron Weather Flight (30 OSSWF) provides comprehensive weather services to the space program at Vandenberg Air Force Base (VAFB) in California. One of their responsibilities is to monitor upper-level winds to ensure safe launch operations of the Minuteman III ballistic missile. The 30 OSSWF tasked the Applied Meteorology Unit (AMU) to analyze VAFB sounding data with the goal of determining the probability of violating (PoV) their upper-level thresholds for wind speed and shear constraints specific to this launch vehicle, and to develop a tool that will calculate the PoV of each constraint on the day of launch. In order to calculate the probability of exceeding each constraint, the AMU collected and analyzed historical data from VAFB. The historical sounding data were retrieved from the National Oceanic and Atmospheric Administration Earth System Research Laboratory archive for the years 1994-2011 and then stratified into four sub-seasons: January-March, April-June, July-September, and October-December. The maximum wind speed and 1000-ft shear values for each sounding in each subseason were determined. To accurately calculate the PoV, the AMU determined the theoretical distributions that best fit the maximum wind speed and maximum shear datasets. Ultimately it was discovered that the maximum wind speeds follow a Gaussian distribution while the maximum shear values follow a lognormal distribution. These results were applied when calculating the averages and standard deviations needed for the historical and real-time PoV calculations. In addition to the requirements outlined in the original task plan, the AMU also included forecast sounding data from the Rapid Refresh model. This information provides further insight for the launch weather officers (LWOs) when determining if a wind constraint violation will occur over the next few hours on day of launch. The interactive graphical user interface (GUI) for this project was developed in Microsoft Excel using Visual Basic for Applications. The GUI displays the critical sounding data easily and quickly for the LWOs on day of launch. This tool will replace the existing one used by the 30 OSSWF, assist the LWOs in determining the probability of exceeding specific wind threshold values, and help to improve the overall upper winds forecast for the launch customer.

Shafer, Jaclyn A.↗

High Energy Astrophysics Tests of Lorentz Invariance and Quantum Gravity Models

High energy astrophysics observations provide the best possibilities to detect a very small violation of Lorentz invariance such as may be related to the structure of space-time near the Planck scale of approx.10(exp -35) m. I will discuss the possible signatures of Lorentz invariance violation (LIV) that can be manifested by observing of the spectra, polarization, and timing of gamma-rays from active galactic nuclei and gamma-ray bursts. Other sensitive tests are provided by observations of the spectra of ultrahigh energy cosmic rays and neutrinos. Using the latest data from the Pierre Auger Observatory one can already derive an upper limit of 4.5 x 10(exp -23) on the fraction of LIV at a Lorentz factor of approx. 2 x 10(exp 11). This result has fundamental implications for quantum gravity models. I will also discuss the possibilities of using more sensitive space-based detection techniques to improve searches for LIV in the future. I will also discuss how the LIV formalism casts doubt on the OPERA superluminal neutrino claim.

Stecker, Floyd W.↗

Developing a Peak Wind Probability Forecast Tool for Kennedy Space Center and Cape Canaveral Air Force Station

This conference presentation describes the development of a peak wind forecast tool to assist forecasters in determining the probability of violating launch commit criteria (LCC) at Kennedy Space Center (KSC) and Cape Canaveral Air Force Station (CCAFS) in east-central Florida. The peak winds are an important forecast element for both the Space Shuttle and Expendable Launch Vehicle (ELV) programs. The LCC define specific peak wind thresholds for each launch operation that cannot be exceeded in order to ensure the safety of the vehicle. The 45th Weather Squadron (45 WS) has found that peak winds are a challenging parameter to forecast, particularly in the cool season months of October through April. Based on the importance of forecasting peak winds, the 45 WS tasked the Applied Meteorology Unit (AMU) to develop a short-range peak-wind forecast tool to assist in forecasting LCC violations. The tool will include climatologies of the 5-minute mean and peak winds by month, hour, and direction, and probability distributions of the peak winds as a function of the 5-minute mean wind speeds.

Lambert, WInifred↗

Coarse-Grain Bandwidth Estimation Scheme for Large-Scale Network

A large-scale network that supports a large number of users can have an aggregate data rate of hundreds of Mbps at any time. High-fidelity simulation of a large-scale network might be too complicated and memory-intensive for typical commercial-off-the-shelf (COTS) tools. Unlike a large commercial wide-area-network (WAN) that shares diverse network resources among diverse users and has a complex topology that requires routing mechanism and flow control, the ground communication links of a space network operate under the assumption of a guaranteed dedicated bandwidth allocation between specific sparse endpoints in a star-like topology. This work solved the network design problem of estimating the bandwidths of a ground network architecture option that offer different service classes to meet the latency requirements of different user data types. In this work, a top-down analysis and simulation approach was created to size the bandwidths of a store-and-forward network for a given network topology, a mission traffic scenario, and a set of data types with different latency requirements. These techniques were used to estimate the WAN bandwidths of the ground links for different architecture options of the proposed Integrated Space Communication and Navigation (SCaN) Network. A new analytical approach, called the "leveling scheme," was developed to model the store-and-forward mechanism of the network data flow. The term "leveling" refers to the spreading of data across a longer time horizon without violating the corresponding latency requirement of the data type. Two versions of the leveling scheme were developed: 1. A straightforward version that simply spreads the data of each data type across the time horizon and doesn't take into account the interactions among data types within a pass, or between data types across overlapping passes at a network node, and is inherently sub-optimal. 2. Two-state Markov leveling scheme that takes into account the second order behavior of the store-and-forward mechanism, and the interactions among data types within a pass. The novelty of this approach lies in the modeling of the store-and-forward mechanism of each network node. The term store-and-forward refers to the data traffic regulation technique in which data is sent to an intermediate network node where they are temporarily stored and sent at a later time to the destination node or to another intermediate node. Store-and-forward can be applied to both space-based networks that have intermittent connectivity, and ground-based networks with deterministic connectivity. For groundbased networks, the store-and-forward mechanism is used to regulate the network data flow and link resource utilization such that the user data types can be delivered to their destination nodes without violating their respective latency requirements.

Cheung, Kar-Ming↗

A Family of Well-Clear Boundary Models for the Integration of UAS in the NAS

The FAA-sponsored Sense and Avoid Workshop for Unmanned Aircraft Systems (UAS) defines the concept of sense and avoid for remote pilots as "the capability of a UAS to remain well clear from and avoid collisions with other airborne traffic." Hence, a rigorous definition of well clear is fundamental to any separation assurance concept for the integration of UAS into civil airspace. This paper presents a family of well-clear boundary models based on the TCAS II Resolution Advisory logic. For these models, algorithms that predict well-clear violations along aircraft current trajectories are provided. These algorithms are analogous to conflict detection algorithms but instead of predicting loss of separation, they predict whether well-clear violations will occur during a given lookahead time interval. Analytical techniques are used to study the properties and relationships satisfied by the models.

Munoz, Cesar A.↗

Lessons Learned Study Final Report for the Exploration Systems Mission Directorate

This report is the final product of a 90-day study performed for the Exploration Systems Mission Directorate. The study was to assemble lessons NASA has learned from previous programs that could help the Exploration Systems Mission Directorate pursue the Exploration vision. It focuses on those lessons that should have the greatest significance to the Directorate during the formulation of program and mission plans. The study team reviewed a large number of lessons learned reports and data bases, including the Columbia Accident Investigation Board and Rogers Commission reports on the Shuttle accidents, accident reports from robotic space flight systems, and a number of management reviews by the Defense Sciences Board, Government Accountability Office, and others. The consistency of the lessons, findings, and recommendations validate the adequacy of the data set. In addition to reviewing existing databases, a series of workshops was held at each of the NASA centers and headquarters that included senior managers from the current workforce as well as retirees. The full text of the workshop reports is included in Appendix A. A lessons learned website was opened up to permit current and retired NASA personnel and on-site contractors to input additional lessons as they arise. These new lessons, when of appropriate quality and relevance, will be brought to the attention of managers. The report consists of four parts: Part 1 provides a small set of lessons, called the Executive Lessons Learned, that represent critical lessons that the Exploration Systems Mission Directorate should act on immediately. This set of Executive Lessons and their supporting rationale have been reviewed at length and fully endorsed by a team of distinguished NASA alumni; Part 2 contains a larger set of lessons, called the Selected Lessons Learned, which have been chosen from the lessons database and center workshop reports on the basis of their specific significance and relevance to the near-term work of the Exploration Directorate. These lessons frequently support the Executive lessons but are more general in nature; Part 3 consists of the reports of the center workshops that were conducted as part of this activity. These reports are included in their entirety (approximately 200 pages) in Appendix G and have significance for specific managers; Part 4 consists of the remainder of the lessons that have been selected by this effort and assembled into a database for the use of the Explorations Directorate. The database is archived and hosted in the Lessons Learned Knowledge Network, which provides a flexible search capability using a wide variety of search terms. Finally, a spreadsheet lists databases searched and a bibliography identifies reports that have been reviewed as sources of lessons for this task. NASA has been presented with many learning opportunities. We have conducted numerous programs, some extremely successful and others total failures. Most have been documented with a formal lessons learned activity, but we have not always incorporated these learning opportunities into our normal modes of business. For example, the Robbins Report of 2001 clearly indicates that many project failures of the past two decades were the result of violating well documented best practices, often in direct violation of management instructions and directives. An overarching lesson emerges: that disciplined execution in accordance with proven best practices is the greatest single contributor to a successful program. The Lessons Learned task team offers a sincere hope that the lessons presented herein will be helpful to the Exploration Systems Directorate in charting and executing their course. The success of the Directorate and of NASA in general depends on our collective ability to move forward without having to relearn the lessons of those who have gone before.

Van Laak, Jim↗

TASAR Flight Trial 2: Assessment of Air Traffic Controller Acceptability of TASAR Requests

In support of the Flight Trial (FT-2) of NASA's prototype of the Traffic Aware Strategic Aircrew Requests (TASAR) concept, observations were conducted at the air traffic facilities to identify and assess the main factors that affect the acceptability of pilot requests by air traffic controllers. Two observers shadowed air traffic controllers at the Atlanta (ZTL) and Jacksonville (ZJX) air traffic control centers as the test flight pilot made pre-scripted requests to invoke acceptability issues and then they interviewed the observed and other controllers voluntarily. Fifty controllers were interviewed with experience ranging from one to thirty-five years. All interviewed controllers were enthusiastic about the technology and accounting for sector boundaries in pilot requests, particularly if pilots can be made aware of high workload situations. All interviewed controllers accept more than fifty percent of pilot requests; forty percent of them reject less than ten percent of requests. The most common reason for rejecting requests is conflicting with traffic followed by violating letters of agreement (LOAs) and negatively impacting neighboring sector workload, major arrival and departure flows and flow restrictions. Thirty-six requests were made during the test, eight of which were rejected due to: the aircraft already handed off to another sector, violating LOA, opposing traffic, intruding into an active special use airspace (SUA), intruding into another center, weather, and unfamiliarity with the requested waypoint. Nine requests were accepted with delay mostly because the controller needed to locate unfamiliar waypoints or to coordinate with other controllers.

Idris, Husni↗

Evaluating Process Effectiveness to Reduce Risk

It is well documented that government agencies do not have the same incentive as the private sector to focus on process effectiveness and continual improvement of those processes. It is also well documented whenever government agencies fail to deliver efficient, effective, consistent, and fair services to the citizens. In spite of the various "reinventing government" and "effectiveness initiatives" of the past decades, and in spite of the efforts on the part of many agencies to improve, government in general still lags behind industry in creating a culture of effective processes and systems. While the tragic events that unfolded recently in Flint, Michigan, teach us that running government "like a business" does not always take the needs of the citizenry into account, there are many lessons and techniques from the private sector that government agencies can use to improve. The incentive to improve, while mandated by various administrations1, needs to come from within the workforce, in order to effectively take root. The best, most effective incentive is to reduce, control or eliminate risk. Government agencies face some of the same risks as the private sector, while some are unique. While ISO 310002 has been around since 2009, risk has taken on increased visibility within the private sector with the advent of the emphasis on risk-based thinking in ISO 9001:20153. The relationship between risk-based thinking and effective processes is simple and direct. Those processes that are well thought out and standardized (i.e. Plan-Do-Check-Act), will have taken into account the applicable policy, statutory, regulatory, safety, quality and technical parameters, which may not occur to someone performing the process with minimal experience or training; and thus protect the employees, the public and the agency from statutory and regulatory violations; delay in providing services; non-delivery of services; harm to public or employee safety and health; cost overruns; breaches in security; loss of confidence in government; failure of publicly funded projects; damage to the environment; ethics violations, and the list goes on; with local, national and even international consequences. The Plan-Do-Check-Act process, also known as the "process approach" can be used at any time to establish and standardize a process, and it can also be used to check periodically for "process creep" (i.e., informal, unauthorized changes that have occurred over time), any necessary updates and improvements. While ISO 9001 compliance is not mandated for all government agencies, if interpreted correctly, it can be useful in establishing a framework and implementing effective management systems and processes.4 Another method that can be used to evaluate effectiveness is the scorecard definitions in Mallory's Process Management Standard5 as a basis for evaluating work on the process level on effective, and continuously improved and improving processes. With processes on the lower end of the scale, agencies are vulnerable to a great many risks, with employees and managers making up many of the rules as they go, leading to the above listed negative results. Without clear guidance for nominal operations, off-nominal situations can, and do, increase the likelihood of chaos. In an increasingly technical environment, with inter-agency communication and collaboration becoming the norm, agencies need to come to grips with the fact that processes can become rapidly outdated, and that the technical community should take on an increased role in the maturation of the agency's processes. Industry has long known that effective processes are also efficient, and process improvement methods such as Kaizen, Lean, Six Sigma, 5S, and mistake proofing lead to increased productivity, improved quality, and decreased cost. Again, government agencies have different concerns, but inefficiencies and mistakes can have dire and wide reaching consequences for the public that they serve. While no one goes to work planning to cause harm, it is up to agencies to establish upper level systems, which make establishment and compliance with processes possible. Again, Mallory provides us with a Systems Management Standard6, similar to the Process Management Standard, with a scale of 0-5 for systems effectiveness and maturity. Deming determined that "eighty-five percent of the reasons for failure are deficiencies in the systems and process rather than the employee. The role of management is to change the process rather than badgering individual employees to do better." 7 It is not just the working level employees who need effective processes, but the mid-and upper level managers as well. A disciplined management culture sets the tone for the employees, aids both routine and off-nominal decision-making, and incorporates risk -based thinking into the systems and processes as a matter of normal activity. Figure 1, illustrates the relationship between ineffective and effective processes and risk, through the use of the "stoplight" colors that are commonly used to show serious situations (red), situations which may be improving or deteriorating depending on trends (yellow), and situations that are under control and continuously improved (green).

Shepherd, Christena C.↗

CCS Control Box and Phasing Analysis Tool

This presentation will discuss the mathematics and future enhancements to the CCS Control Box and Phasing Analysis Tool (CBA). Various plots will be analyzed to show how maneuvers are detected in the user selected ephemerides and how the violation epoch dates are calculated when a control box violation occurs.

MOWG↗

Uncertainty Analysis of Coaxial Thermocouple Calorimeters Used in Arc Jets

Recent introduction of Coaxial Thermocouple type calorimeters into the NASA Ames arc jet facilities has inspired an analysis of 2D conduction effects internal to this type of calorimeter. The 1D finite slab inverse analysis (which is typically used to deduce the heat transfer to the calorimeter) relies on the assumption that lateral conduction (i.e., 2D effects) is negligible. Most calorimeter bodies have a spherical nose, which in itself is a violation of the 1D finite slab analysis assumption. Secondly most calorimeters experience a variation in heating across the face of the body which is also a violation of the 1D finite slab analysis assumption. It turns out that these two effects tend to cancel each other to some extent. This paper shows the extent to which error exists in the analysis of the Coaxial Thermocouple type calorimeters, and also offers analysis strategies for reducing the errors.

Lateral Conduction↗