SEARCH · Engineering Papers

Results for “Software Requirements”

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.

SourceResearch connectionFrom yearThrough year

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

At least 1,621 records · Page 90

All sources NASA NTRS DOE OSTI

NASA NTRS2008

Ares-I Bending Filter Design using a Constrained Optimization Approach

The Ares-I launch vehicle represents a challenging flex-body structural environment for control system design. Software filtering of the inertial sensor output is required to ensure adequate stable response to guidance commands while minimizing trajectory deviations. This paper presents a design methodology employing numerical optimization to develop the Ares-I bending filters. The design objectives include attitude tracking accuracy and robust stability with respect to rigid body dynamics, propellant slosh, and flex. Under the assumption that the Ares-I time-varying dynamics and control system can be frozen over a short period of time, the bending filters are designed to stabilize all the selected frozen-time launch control systems in the presence of parameter uncertainty. To ensure adequate response to guidance command, step response specifications are introduced as constraints in the optimization problem. Imposing these constrains minimizes performance degradation caused by the addition of the bending filters. The first stage bending filter design achieves stability by adding lag to the first structural frequency to phase stabilize the first flex mode while gain stabilizing the higher modes. The upper stage bending filter design gain stabilizes all the flex bending modes. The bending filter designs provided here have been demonstrated to provide stable first and second stage control systems in both Draper Ares Stability Analysis Tool (ASAT) and the MSFC MAVERIC 6DOF nonlinear time domain simulation.

Hall, Charles↗

NASA NTRS2008

Attitude and Translation Control of a Solar Sail Vehicle

A report discusses the ability to control the attitude and translation degrees-of-freedom of a solar sail vehicle by changing its center of gravity. A movement of the spacecraft s center of mass causes solar-pressure force to apply a torque to the vehicle. At the compact core of the solar-sail vehicle lies the spacecraft bus which is a large fraction of the total vehicle mass. In this concept, the bus is attached to the spacecraft by two single degree-of-freedom linear tracks. This allows relative movement of the bus in the sail plane. At the null position, the resulting solar pressure applies no torque to the vehicle. But any deviation of the bus from the null creates an offset between the spacecraft center of mass and center of solar radiation pressure, resulting in a solar-pressure torque on the vehicle which changes the vehicle attitude. Two of the three vehicle degrees of freedom can be actively controlled in this manner. The third, the roll about the sunline, requires a low-authority vane/propulsive subsystem. Translation control of the vehicle is achieved by directing the solar-pressure-induced force in the proper inertial direction. This requires attitude control. Attitude and translation degrees-of-freedom are therefore coupled. A guidance law is proposed, which allows the vehicle to stationkeep at an appropriate point on the inertially-rotating Sun-Earth line. Power requirements for moving the bus are minimal. Extensive software simulations have been performed to demonstrate the feasibility of this concept.

Singh, Gurkirpal↗

NASA NTRS2007

High-Performance Tiled WMS and KML Web Server

This software is an Apache 2.0 module implementing a high-performance map server to support interactive map viewers and virtual planet client software. It can be used in applications that require access to very-high-resolution geolocated images, such as GIS, virtual planet applications, and flight simulators. It serves Web Map Service (WMS) requests that comply with a given request grid from an existing tile dataset. It also generates the KML super-overlay configuration files required to access the WMS image tiles.

Plesea, Lucian↗

NASA NTRS2011

Spatial Query for Planetary Data

Science investigators need to quickly and effectively assess past observations of specific locations on a planetary surface. This innovation involves a location-based search technology that was adapted and applied to planetary science data to support a spatial query capability for mission operations software. High-performance location-based searching requires the use of spatial data structures for database organization. Spatial data structures are designed to organize datasets based on their coordinates in a way that is optimized for location-based retrieval. The particular spatial data structure that was adapted for planetary data search is the R+ tree.

Shams, Khawaja S.↗

NASA NTRS2013

Descent and Landing Triggers for the Orion Multi-Purpose Crew Vehicle Exploration Flight Test-1

The Orion Multi-Purpose Crew Vehicle (MPCV) will perform a flight test known as Exploration Flight Test-1 (EFT-1) currently scheduled for 2014. One of the primary functions of this test is to exercise all of the important Guidance, Navigation, Control (GN&C), and Propulsion systems, along with the flight software for future flights. The Descent and Landing segment of the flight is governed by the requirements levied on the GN&C system by the Landing and Recovery System (LRS). The LRS is a complex system of parachutes and flight control modes that ensure that the Orion MPCV safely lands at its designated target in the Pacific Ocean. The Descent and Landing segment begins with the jettisoning of the Forward Bay Cover and concludes with sensing touchdown. This paper discusses the requirements, design, testing, analysis and performance of the current EFT-1 Descent and Landing Triggers flight software.

Bihari, Brian D.↗

NASA NTRS2013

STS Case Study Development Support

The Shuttle Case Study Collection (SCSC) has been developed using lessons learned documented by NASA engineers, analysts, and contractors. The SCSC provides educators with a new tool to teach real-world engineering processes with the goal of providing unique educational materials that enhance critical thinking, decision-making and problem-solving skills. During this third phase of the project, responsibilities included: the revision of the Hyper Text Markup Language (HTML) source code to ensure all pages follow World Wide Web Consortium (W3C) standards, and the addition and edition of website content, including text, documents, and images. Basic HTML knowledge was required, as was basic knowledge of photo editing software, and training to learn how to use NASA's Content Management System for website design. The outcome of this project was its release to the public.

Rosa de Jesus, Dan A.↗

NASA NTRS2014

Integration of a MicroCAT Propulsion System and a PhoneSat Bus into a 1.5U CubeSat

NASA Ames Research Center and the George Washington University have developed an electric propulsion subsystem that can be integrated into the PhoneSat bus. Experimental tests have shown a reliable performance by firing three different thrusters at various frequencies in vacuum conditions. The three thrusters were controlled by a SmartPhone that was running the PhoneSat software. The subsystem is fully operational and it requires low average power to function (about 0.1 W). The interface consists of a microcontroller that sends a trigger pulses to the PPU (Plasma Processing Unit), which is responsible for the thruster operation. Frequencies ranging from 1 to 50Hz have been tested, showing a strong flexibility. A SmartPhone acts as the main user interface for the selection of commands that control the entire system. The micro cathode arc thruster MicroCAT provides a high 1(sub sp) of 3000s that allows a 4kg satellite to obtain a (delta)V of 300m/s. The system mass is only 200g with a total of volume of 200(cu cm). The propellant is based on a solid cylinder made of Titanium, which is the cathode at the same time. This simplicity in the design avoids miniaturization and manufacturing problems. The characteristics of this thruster allow an array of MicroCATs to perform attitude control and orbital correcton maneuvers that will open the door for the implementation of an extensive collection of new mission concepts and space applications for CubeSats. NASA Ames is currently working on the integration of the system to fit the thrusters and PPU inside a 1.5U CubeSat together with the PhoneSat bus into a 1.5U CubeSat. This satellite is intended to be deployed from the ISS in 2015 and test the functionality of the thrusters by spinning the satellite around its long axis and measure the rotational speed with the phone byros. This test flight will raise the TRL of the propulsion system from 5 to 7 and will be a first test for further CubeSats with propulsion systems, a key subsystem for long duration or interplanetary CubeSat missions.

PhoneSat↗

NASA NTRS2014

Three Dimensional Lightning Launch Commit Criteria Visualization Tool

Lightning occurrence too close to a NASA LSP or future SLS program launch vehicle in flight would have disastrous results. The sensitive electronics on the vehicle could be damaged to the point of causing an anomalous flight path and ultimate destruction of the vehicle and payload.According to 45th Weather Squadron (45 WS) Lightning Launch Commit Criteria (LLCC), a vehicle cannot launch if lightning is within 10 NM of its pre-determined flight path. The 45 WS Launch Weather Officers (LWOs) evaluate this LLCC for their launch customers to ensure the safety of the vehicle in flight. Currently, the LWOs conduct a subjective analysis of the distance between lightning and the flight path using data from different display systems. A 3-D display in which the lightning data and flight path are together would greatly reduce the ambiguity in evaluating this LLCC. It would give the LWOs and launch directors more confidence in whether a GO or NO GO for launch should be issued. When lightning appears close to the path, the LWOs likely err on the side of conservatism and deem the lightning to be within 10 NM. This would cause a costly delay or scrub. If the LWOs can determine with a strong level of certainty that the lightning is beyond 10 NM, launch availability would increase without compromising safety of the vehicle, payload or, in the future, astronauts.The AMU was tasked to conduct a market research of commercial, government, and open source software that might be able to ingest and display the 3-D lightning data from the KSC Lightning Mapping Array (LMA), the 45th Space Wing Weather Surveillance Radar (WSR), the National Weather Service in Melbourne Weather Surveillance Radar 1988 Doppler (WSR-88D), and the vehicle flight path data so that all can be visualized together. To accomplish this, the AMU conducted Internet searches for potential software candidates and interviewed software developers.None of the available off-the-shelf software had a 3-D capability that could display all of the data in a single visualization. The AMU determined there are two viable software packages that could satisfy the 45 WS requirement with further development and recommends the KSC Weather Office follow-up with both organizations to request development costs.

weather↗

NASA NTRS2016

Orion Burn Management, Nominal and Response to Failures

An approach for managing Orion on-orbit burn execution is described for nominal and failure response scenarios. The burn management strategy for Orion takes into account per-burn variations in targeting, timing, and execution; crew and ground operator intervention and overrides; defined burn failure triggers and responses; and corresponding on-board software sequencing functionality. Burn-to- burn variations are managed through the identification of specific parameters that may be updated for each progressive burn. Failure triggers and automatic responses during the burn timeframe are defined to provide safety for the crew in the case of vehicle failures, along with override capabilities to ensure operational control of the vehicle. On-board sequencing software provides the timeline coordination for performing the required activities related to targeting, burn execution, and responding to burn failures.

Odegard, Ryan↗

NASA NTRS2016

CASIS Fact Sheet: Hardware and Facilities

Vencore is a proven information solutions, engineering, and analytics company that helps our customers solve their most complex challenges. For more than 40 years, we have designed, developed and delivered mission-critical solutions as our customers' trusted partner. The Engineering Services Contract, or ESC, provides engineering and design services to the NASA organizations engaged in development of new technologies at the Kennedy Space Center. Vencore is the ESC prime contractor, with teammates that include Stinger Ghaffarian Technologies, Sierra Lobo, Nelson Engineering, EASi, and Craig Technologies. The Vencore team designs and develops systems and equipment to be used for the processing of space launch vehicles, spacecraft, and payloads. We perform flight systems engineering for spaceflight hardware and software; develop technologies that serve NASA's mission requirements and operations needs for the future. Our Flight Payload Support (FPS) team at Kennedy Space Center (KSC) provides engineering, development, and certification services as well as payload integration and management services to NASA and commercial customers. Our main objective is to assist principal investigators (PIs) integrate their science experiments into payload hardware for research aboard the International Space Station (ISS), commercial spacecraft, suborbital vehicles, parabolic flight aircrafts, and ground-based studies. Vencore's FPS team is AS9100 certified and a recognized implementation partner for the Center for Advancement of Science in Space (CASIS

Solomon, Michael R.↗

NASA NTRS2016

Deploying a Route Optimization EFB Application for Commercial Airline Operational Trials

The Traffic Aware Planner (TAP), developed for NASA Langley Research Center to support the Traffic Aware Strategic Aircrew Requests (TASAR) project, is a flight-efficiency software application developed for an Electronic Flight Bag (EFB). Tested in two flight trials and planned for operational testing by two commercial airlines, TAP is a real-time trajectory optimization application that leverages connectivity with onboard avionics and broadband Internet sources to compute and recommend route modifications to flight crews to improve fuel and time performance. The application utilizes a wide range of data, including Automatic Dependent Surveillance Broadcast (ADS-B) traffic, Flight Management System (FMS) guidance and intent, on-board sensors, published winds and weather, and Special Use Airspace (SUA) schedules. This paper discusses the challenges of developing and deploying TAP to various EFB platforms, our solutions to some of these challenges, and lessons learned, to assist commercial software developers and hardware manufacturers in their efforts to implement and extend TAP functionality in their environments. EFB applications (such as TAP) typically access avionics data via an ARINC 834 Simple Text Avionics Protocol (STAP) server hosted by an Aircraft Interface Device (AID) or other installed hardware. While the protocol is standardized, the data sources, content, and transmission rates can vary from aircraft to aircraft. Additionally, the method of communicating with the AID may vary depending on EFB hardware and/or the availability of onboard networking services, such as Ethernet, WIFI, Bluetooth, or other mechanisms. EFBs with portable and installed components can be implemented using a variety of operating systems, and cockpits are increasingly incorporating tablet-based technologies, further expanding the number of platforms the application may need to support. Supporting multiple EFB platforms, AIDs, avionics datasets, and user interfaces presents a challenge for software developers and the management of their code baselines. Maintaining multiple baselines to support all deployment targets can be extremely cumbersome and expensive. Certification also needs to be considered when developing the application. Regardless of whether the software is itself destined to be certified, data requirements in support of the application and user interface elements may introduce certification requirements for EFB manufacturers and the airlines. The example of TAP, the challenges faced, solutions implemented, and lessons learned will give EFB application and hardware developers insight into future potential requirements in deploying TAP or similar flight-deck EFB applications.

Roscoe, David A.↗

NASA NTRS2018

Unmanned Aircraft Systems Traffic Management (UTM)

UTM is an 'air traffic management' ecosystem for uncontrolled operations. UTM utilizes industry's ability to supply services under FAA's regulatory authority where these services do not exist. UTM development will ultimately enable the management of large scale, low-altitude UAS operations. Operational concept will address beyond visual line of sight UAS operations under 400 ft. AGL. Information architecture, data exchange protocols, software functions. Roles/responsibilities of FAA and operators. Performance requirements.

UTM↗

NASA NTRS2020

Ground System Milestones: 20 Years of Earth Observing Satellite Mission Operations

Aqua, Aura, and Terra are Earth observing satellites that serve in the Earth Observing System (EOS). Terra, the flagship mission of the EOS, was launched in 1998. Aqua was launched in 2002 and Aura was launched in 2004. Each spacecraft was designed for a 6 year lifespan. Currently, each spacecraft meets all mission and science requirements. As technology advances, the onboard hardware and software remain the same, however, our ground system progresses. In the past twenty years, many changes have taken place. Our goal is to describe the life of the ground system from launch, to present day, and touch on our future plans. The focus of our presentation will be how EOS has and continues to modernize our ground system for the future. We would like to share our experiences and give insight into the operational challenges of a 20 year old ground system. Our hope is for future mission operators and those maintaining potential age defying satellites to use our past experiences and lessons learned for future operational concepts.

Barrett, Grant↗

NASA NTRS2018

A GNSS Receiver for Small-Sats Enabling Precision POD, Radio Occultations and Reflections

A low cost, low power, and low mass GNSS receiver (called Cion) has been developed and is currently flying on the CICERO cubesats. The receiver was designed in less than a year by JPL for Tyvak and GeoOptics for use in the GeoOptics CICERO constellation and leverages 25 years of JPL GNSS reciever design experience. Cion uses a commercial off-the-shelf (COTS) computer along with existing space qualified RF down-converters, software, and firmware to produce atmospheric Radio Occultation (RO) data. By combining a FPGA with dual core ARM processor and an embedded system controller, the Xilinx Zynq processor is an enabling technology that provides a customizable digital signal processing platform integrated into the computer (System on a chip) and enables off-the-shelf hardware to become the main engine behind this software defined radio. Using Linux for the on-board computer allows for fast development times and liberal use of existing open source software libraries. The parts of the receiver that require realtime implementation are performed in the Field Programmable Gate Array (FPGA), which can also be reprogrammed in flight. While the Zynq is not rad hard, the silicon on insulator (SOI) technology is rad tolerant ‘by accident’, allowing for its use in many space-based applications. Early results show that the Cion is working as designed, has demonstrated the first known GLONASS occultations, and obtains high quality atmospheric profiles with excellent lower troposphere penetration (near Earth’s surface).

Young, Larry↗

NASA NTRSDate not supplied

Fracture Mechanics Testing of Titanium 6AL-4V in LMP-103S Propellant

Propellant tank safe-life analysis is a spacecraft propulsion subsystem Launch Range processing requirement. The material property inputs for the safe-life analysis include the stress intensity factor for environment-assisted cracking (KEAC). The KEAC for titanium alloy Ti 6Al-4V in LMP-103S propellant was determined experimentally using an innovative test method following ASTM E1681, Standard Test Method for Determining Threshold Stress Intensity Factor for Environment-Assisted Cracking of Metallic Materials. This effort was a collaboration between NASA Goddard Space Flight Center and NASA Kennedy Space Center to expose the test specimens in the propellant, while loaded in the test fixtures, for 1000- hour (42 days) at 50°C. Two test rounds have been completed to date; 1) testing mechanically loaded specimens but without propellant and 2) testing mechanically loaded specimens wetted with LMP-103S propellant. The dry test was to evaluate the crack growth without exposure to the LMP-103S propellant, and further assess the un-wetted stress intensity factor for the full 1000-hour duration. The second round of testing included the propellant soak for the requisite 1000- hour at 50°C. Current results show that the threshold intensity factor for environment-assisted cracking (exposed to LMP103S) is 22.5 ksi√in for the bulk material and 36. 2 ksi√in for the weld material. A generic ‘candidate’ tank geometry and material thickness is developed for a damage tolerance of known surface cracks below the nondestructive inspection technique detection limit. Evaluations with and without the use of a threshold intensity factor for environment-assisted cracking is performed for the required 4x propellant tank service life using the software tool NASGRO. SP2024_00239

Green propulsion↗

DOE OSTI2022

System Analysis Modeling and Intermodal Transportation for Commercial Spent Nuclear Fuel

The United States Department of Energy (DOE) has long term goals to develop solutions for managing the nation’s spent nuclear fuel (SNF) and high-level waste (HLW) inventory. The Integrated Waste Management (IWM) program under the DOE office of Nuclear Energy (DOE-NE) is employing system-level engineering and analysis principles to inform potential future waste management system architectures. Managing the spent nuclear waste requires the use of system-level analysis software that takes various aspects of the fuel cycle into account like waste generation, on-site/centralized storage, transportation infrastructure, and long-term disposal. The Next Generation System Analysis Model (NGSAM) is an agent-based model that was developed to simulate the transportation and storage of SNF and HLW. As an agent-based model, NGSAM has the capability to detail the interaction and movement of individual components and groups, such as rail cars and casks. The SNF inventory from commercial nuclear reactors is currently in temporary storage at multiple locations spread across the United States. Shipping of SNF from these locations relies on one of three transportation modes: rail, heavy-haul truck, or barge. Out of the three modes identified, rail is generally the most preferred due to the size of the canisters and casks the SNF would be shipped in. However, under some scenarios, a direct rail route might not be readily available to a reactor site or improving the rail infrastructure at shutdown sites might be too cost-prohibitive for utilities to opt for a direct rail transfer. Under such scenarios, using a barge or heavy haul truck to de-inventory the site and transfer the SNF to a nearby intermodal transfer site with adequate rail infrastructure where the payload could be transferred to a rail car might prove to be an attractive option. This work initially presents the various intermodal transportation options that could be used to transfer SNF from reactor sites to rail cars. This is followed by exploring the operational steps in each of these modes to move the SNF from a reactor site and transfer it to a rail car. This work also presents the procedure of implementing the intermodal transfer methodology in NGSAM using various Java methods. Finally, the process times for accomplishing each of the individual steps are furnished. The implementation ideology, assumptions, and future steps are presented in this work.

Gadey, Harish Reddy↗

DOE OSTI2023

Mastering HPC Runtime Prediction: From Observing Patterns to a Methodological Approach: Preprint

The continual expansion of high-performance computing (HPC) brings with it an increasing need for efficiency. Heavy investment in energy, hardware, and software infrastructure to support peta- and exascale computing requires the optimization of existing systems and, wherever possible, the discernment and adoption of best-practices towards these goals. Such is the case for runtime prediction. When a job is submitted to an HPC system, an estimate of its runtime is provided by the user in the form of "requested wallclock''. Error in this user-provided estimate can lead to jobs being prematurely killed by the scheduler, increased wait time on the queue, and decreased system utilization. More than fifteen years of research has been directed at mitigating these effects by using data-driven runtime predictions. Codified here is a set of commonalities and insights emerging from this body of work, which we present as recommendations and best practices. These practices are combined into a methodological approach described and evaluated on an 11-million-job dataset from the National Renewable Energy Laboratory's petascale HPC system, Eagle. This dataset and the accompanying codebase have been released to the public domain for the benefit of the wider HPC research community.

high performance computing↗

DOE OSTI2022

A numerical evaluation of the ambient air temperature in the Electron-Ion Collider tunnel

The Electron-Ion Collider (EIC) is a next-generation collider-accelerator that may require consistent operating temperature conditions for the beams within the accelerator tunnels to maintain stable operation. Variations in ambient temperature within the tunnel can cause thermal expansion of beampipe and component supports and can negatively affect the tunnel equipment, impacting the stability of the beamline. Modifications will be made to the Relativistic Heavy Ion Collider (RHIC) at Brookhaven National Laboratory (BNL) to create the EIC, which necessitates a temperature model that addresses these modifications. To approach this problem, the consistency of temperature changes in different tunnel sections was first evaluated by plotting RHIC tunnel temperature data at various times of the day and year. From this data, a tunnel section was selected and a 2D temperature model was created for RHIC, EIC, and EIC with added cooling configurations. Soil temperature data was analyzed to determine the maximum, average, and mode soil temperatures, which were used as boundary conditions in different temperature scenarios. Computational fluid dynamics modeling was used to create 2D temperature profiles for the configurations. From this model, the predicted temperatures indicate that further analysis is required to validate the boundary conditions and benchmark the current conditions to allow the prediction of the tunnel ambient conditions at EIC. This research can be used as a preliminary model to create an EIC tunnel cooling system that will increase the operational stability of the EIC. As a result of my work this summer, I have become familiar with computational fluid dynamics, including creating fluid dynamic simulations using ANSYS Fluent and related software. I have also learned about the project process required for planning large-scale engineering projects.

43 PARTICLE ACCELERATORS↗