Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “operating experience”

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 757 records · Page 42

Support Routines for In Situ Image Processing

This software consists of a set of application programs that support ground-based image processing for in situ missions. These programs represent a collection of utility routines that perform miscellaneous functions in the context of the ground data system. Each one fulfills some specific need as determined via operational experience. The most unique aspect to these programs is that they are integrated into the large, in situ image processing system via the PIG (Planetary Image Geometry) library. They work directly with space in situ data, understanding the appropriate image meta-data fields and updating them properly. The programs themselves are completely multimission; all mission dependencies are handled by PIG. This suite of programs consists of: (1)marscahv: Generates a linearized, epi-polar aligned image given a stereo pair of images. These images are optimized for 1-D stereo correlations, (2) marscheckcm: Compares the camera model in an image label with one derived via kinematics modeling on the ground, (3) marschkovl: Checks the overlaps between a list of images in order to determine which might be stereo pairs. This is useful for non-traditional stereo images like long-baseline or those from an articulating arm camera, (4) marscoordtrans: Translates mosaic coordinates from one form into another, (5) marsdispcompare: Checks a Left Right stereo disparity image against a Right Left disparity image to ensure they are consistent with each other, (6) marsdispwarp: Takes one image of a stereo pair and warps it through a disparity map to create a synthetic opposite- eye image. For example, a right eye image could be transformed to look like it was taken from the left eye via this program, (7) marsfidfinder: Finds fiducial markers in an image by projecting their approximate location and then using correlation to locate the markers to subpixel accuracy. These fiducial markets are small targets attached to the spacecraft surface. This helps verify, or improve, the pointing of in situ cameras, (8) marsinvrange: Inverse of marsrange . given a range file, re-computes an XYZ file that closely matches the original. . marsproj: Projects an XYZ coordinate through the camera model, and reports the line/sample coordinates of the point in the image, (9) marsprojfid: Given the output of marsfidfinder, projects the XYZ locations and compares them to the found locations, creating a report showing the fiducial errors in each image. marsrad: Radiometrically corrects an image, (10) marsrelabel: Updates coordinate system or camera model labels in an image, (11) marstiexyz: Given a stereo pair, allows the user to interactively pick a point in each image and reports the XYZ value corresponding to that pair of locations. marsunmosaic: Extracts a single frame from a mosaic, which will be created such that it could have been an input to the original mosaic. Useful for creating simulated input frames using different camera models than the original mosaic used, and (12) merinverter: Uses an inverse lookup table to convert 8-bit telemetered data to its 12-bit original form. Can be used in other missions despite the name.

Deen, Robert G.↗

Human Exploration of Near-Earth Asteroids and Sample Collection Considerations

In 2009 the Augustine Commission identified near-Earth asteroids (NEAs) as high profile destinations for human exploration missions beyond the Earth-Moon system as part of the Flexible Path. Subsequently, the U.S. presidential administration directed NASA on April 15, 2010 to include NEAs as destinations for future human exploration with the goal of sending astronauts to a NEA in the mid to late 2020s. This directive became part of the official National Space Policy of the United States of America as of June 28, 2010. Human Exploration Considerations: These missions would be the first human expeditions to interplanetary bodies beyond the Earth-Moon system and would prove useful for testing technologies required for human missions to Mars, Phobos and Deimos, and other Solar System destinations. Missions to NEAs would undoubtedly provide a great deal of technical and engineering data on spacecraft operations for future human space exploration while conducting in-depth scientific examinations of these primitive objects. However, prior to sending human explorers to NEAs, robotic investigations of these bodies would be required in order to maximize operational efficiency and reduce mission risk. These precursor missions to NEAs would fill crucial strategic knowledge gaps concerning their physical characteristics that are relevant for human exploration of these relatively unknown destinations. Sample Science Benefits: Information obtained from a human investigation of a NEA, together with ground-based observations and prior spacecraft investigations of asteroids and comets, will also provide a real measure of ground truth to data obtained from terrestrial meteorite collections. Major advances in the areas of geochemistry, impact history, thermal history, isotope analyses, mineralogy, space weathering, formation ages, thermal inertias, volatile content, source regions, solar system formation, etc. can be expected from human NEA missions. Samples directly returned from a primitive body would lead to the same kind of breakthroughs for understanding NEAs that the Apollo samples provided for understanding the Earth-Moon system and its formation history. International Participation: In addition, robotic precursor and human exploration missions to NEAs would allow the NASA and its international partners to gain operational experience in performing complex tasks (e.g., sample collection, deployment of payloads, retrieval of payloads, etc.) with crew, robots, and spacecraft under microgravity conditions at or near the surface of a small body. This would provide an important synergy between the worldwide Science and Exploration communities, which will be crucial for development of future international deep space exploration architectures and has potential benefits for future exploration of other destinations beyond low-Earth orbit.

Abell, Paul↗

Human Factors Guidelines for UAS in the National Airspace System

The ground control stations (GCS) of some UAS have been characterized by less-than-adequate human-system interfaces. In some cases this may reflect a failure to apply an existing regulation or human factors standard. In other cases, the problem may indicate a lack of suitable guidance material. NASA is leading a community effort to develop recommendations for human factors guidelines for GCS to support routine beyond-line-of-sight UAS operations in the national airspace system (NAS). In contrast to regulations, guidelines are not mandatory requirements. However, by encapsulating solutions to identified problems or areas of risk, guidelines can provide assistance to system developers, users and regulatory agencies. To be effective, guidelines must be relevant to a wide range of systems, must not be overly prescriptive, and must not impose premature standardization on evolving technologies. By assuming that a pilot will be responsible for each UAS operating in the NAS, and that the aircraft will be required to operate in a manner comparable to conventionally piloted aircraft, it is possible to identify a generic set of pilot tasks and the information, control and communication requirements needed to support these tasks. Areas where guidelines will be useful can then be identified, utilizing information from simulations, operational experience and the human factors literature. In developing guidelines, we recognize that existing regulatory and guidance material will, at times, provide adequate coverage of an area. In other cases suitable guidelines may be found in existing military or industry human factors standards. In cases where appropriate existing standards cannot be identified, original guidelines will be proposed.

Guidelines↗

Asteroid Redirect Robotic Mission: Robotic Boulder Capture Option Overview

The National Aeronautics and Space Administration (NASA) is currently studying an option for the Asteroid Redirect Robotic Mission (ARRM) that would capture a multi-ton boulder (typically 2-4 meters in size) from the surface of a large (is approximately 100+ meter) Near-Earth Asteroid (NEA) and return it to cislunar space for subsequent human and robotic exploration. This alternative mission approach, designated the Robotic Boulder Capture Option (Option B), has been investigated to determine the mission feasibility and identify potential differences from the initial ARRM concept of capturing an entire small NEA (4-10 meters in size), which has been designated the Small Asteroid Capture Option (Option A). Compared to the initial ARRM concept, Option B allows for centimeter-level characterization over an entire large NEA, the certainty of target NEA composition type, the ability to select the boulder that is captured, numerous opportunities for mission enhancements to support science objectives, additional experience operating at a low-gravity planetary body including extended surface contact, and the ability to demonstrate future planetary defense strategies on a hazardous-size NEA. Option B can leverage precursor missions and existing Agency capabilities to help ensure mission success by targeting wellcharacterized asteroids and can accommodate uncertain programmatic schedules by tailoring the return mass.

Mazanek, Daniel D.↗

Scheduling Spitzer: The SIRPASS Story

NASA's Spitzer Space Telescope was launched on August 25, 2003 from Florida's Cape Canaveral Air Force Base. Drifting in a unique Earth-trailing orbit around the Sun, Spitzer sees an optically invisible universe dominated by dust and stars. Since 1997, the Spitzer Integrated Resource Planning and Scheduling System (SIRPASS) has helped produce spacecraft activity plans for the Spitzer Space Telescope. SIRPASS is used by members of the Observatory Planning and Scheduling Team to plan, schedule and sequence the Telescope from data made available to them from the science and engineering community. Because of the volume of data that needs to be scheduled, SIRPASS offers a variety of automated assistants to aid in this task. This paper will describe the functional elements of the SIRPASS software system -- emphasizing the role that automation plays in the system -- and will highlight lessons learned for the software developer from a decade of Spitzer Space Telescope operations experience.

flight systems↗

The Mission Accessibility of Near-Earth Asteroids

Astrodynamical Earth departure dates; mission v; mission duration; stay time; etc. Physical I NEO size(?); rotation rate; dust satellites environment; chemistry; etc. Architectural Launch vehicle(s); crew vehicle(s); habitat module(s); budget; etc. Operational Operations experience; abort options profiles; etc. Astrodynamical Accessibility is the starting point for understanding the options and opportunities available to us. Here we shall focus on. Astrodynamical Accessibility.2 Earth departure date between 2015-01-01 and 2040-12-31 Earth departure C3 60 km2s2. Total mission v 12 kms. The total v includes (1) the Earth departure maneuver from a 400 km altitude circular parking orbit, (2) the maneuver to match the NEAs velocity at arrival, (3) the maneuver to depart the NEA and, (4) if necessary, a maneuver to control the atmospheric re-entry speed during Earth return. Total round trip mission duration 450 days. Stay time at the NEA 8 days Earth atmospheric entry speed 12 kms at an altitude of 125 km. A near-Earth asteroid (NEA) that offers at least one trajectory solution meeting those criteria is classified as NHATS-compliant.

Trajectory Optimization↗

A Basic Robotic Excavator (the Glenn Digger): Description, Design, and Initial Operation

This paper describes the design, commercial part selections, fabrication, assembly, installation, and initial operation of a two degree of freedom robotic excavator. Colloquially referred to as "the NASA Glenn Digger," it was designed specifically to be mounted onto, and to operate with, the then newly developed Centaur 2 robotic mobility base. The excavator, when mounted to Centaur 2, is designed to scoop loose regolith from the terrain, raise its loaded bucket up and dump the load into a hopper of at least a 1-m-height. The hopper represents the input to a machine that would process the raw material, such as to produce oxygen from lunar regolith as would be required for long-term lunar habitation. This equipment debuted at the annual Research and Technology Studies ("Desert RATS", Ref. 1) event held north of Flagstaff, Arizona, in September of 2010, when the Digger was successfully joined to Centaur 2 and the shoveling articulation was demonstrated. During 2011, the hardware was modified for added strength, strain gauges were added to measure loads, and the controls were improved in preparation for the 2011 Desert RATS event, where additional "field operations" experience was gained.

backhoe↗

On-Demand Mobility (ODM) Technical Pathway: Enabling Ease of Use and Safety

On-demand mobility (ODM) through aviation refers to the ability to quickly and easily move people or equivalent cargo without delays introduced by lack of, or infrequently, scheduled service. A necessary attribute of ODM is that it be easy to use, requiring a minimum of special training, skills, or workload. Fully-autonomous vehicles would provide the ultimate in ease-of-use (EU) but are currently unproven for safety-critical applications outside of a few, situationally constrained applications (e.g. automated trains operating in segregated systems). Applied to aviation, the current and near-future state of the art of full-autonomy, may entail undesirable trade-offs such as very conservative operational margins resulting in reduced trip reliability and transportation utility. Furthermore, acceptance by potential users and regulatory authorities will be challenging without confidence in autonomous systems in developed in less critical, but still challenging applications. A question for the aviation community is how we can best develop practical ease-of-use for aircraft that are sized to carry a small number of passengers (e.g. 1-9) or equivalent cargo. Such development is unlikely to be a single event, but rather a managed, evolutionary process where responsibility and authority transitions from human to automation agents as operational experience is gained with increasingly intelligent systems. This talk presents a technology road map being developed at NASA Langley, as part of an overall strategy to foster ODM, for the development of ease-of-use for ODM aviation.

Goodrich, Ken↗

Conjunction Assessment Techniques and Operational Results from the Magnetospheric Multiscale Mission

This paper will describe the results that have been obtained to date during the MMS mission concerning conjunction assessment. MMS navigation makes use of a weak-signal GPS-based system: this allows signals to be received even when MMS is flying above the GPS orbits, producing a highly accurate determination of the four MMS orbits. This data is downlinked to the MMS Mission Operations Center (MOC) and used by the Flight Dynamics Operations Area (FDOA) for both maneuver design and conjunction assessment. The MMS fly in tetrahedron formations around apogee, in order to collect simultaneous particles and fields science data. The original plan was to fly tetrahedra between 10 and 160 km in size; however, after Phase 1a of the mission, the science team requested that smaller sizes be flown if feasible. After analysis (to be detailed in a companion paper), a new minimum size of 7 km was decided upon. Flying at this reduced scale size makes conjunction assessment between the MMS spacecraft even more important: the methods that are used by the MMS FDOA to address this problem will be described in the paper, and a summary given of the previous analyses that went into the development of these techniques. Details will also be given of operational experiences to date. Finally, two CA mitigation maneuver types that have been designed (but never yet required to actually be performed) will also be outlined.

conjunction Assessment↗

Workload and Performance in Air Traffic Control: Exploring the Influence of Levels of Automation and Variation in Task Demand

In air traffic control, task demand and workload have important implications for the safety and efficiency of air traffic. Task demand is dynamic, however, research on demand transitions and associated controller perception and performance is limited. In addition, there is a comparatively restricted understanding of the influence of task demand transitions on workload and performance, in association with automation. This study used an air traffic control simulation to investigate the influence of task demand transitions and two conditions of varying automation, on workload and efficiency-related performance. Findings showed that a both the direction of the task demand variation, and the amount of automation, influenced the relationship between workload and performance. Further research is needed to enhance understanding of demand transition and workload history effects on operator experience and performance, in both air traffic control and other safety-critical domains.

air traffic control↗

NASA's Space Launch System: Progress Report

After more than four decades exploring the space environment from low Earth orbit and developing long-duration spaceflight operational experience with the International Space Station (ISS), NASA is once again preparing to send explorers into deep space. Development, test and manufacturing is now underway on the launch vehicle, the crew spacecraft and the ground processing and launch facilities to support human and robotic missions to the moon, Mars and the outer solar system. The enabling launch vehicle for these ambitious new missions is the Space Launch System (SLS), managed by NASA's Marshall Space Flight Center (MSFC). Since the program began in 2011, the design has passed Critical Design Review, and extensive development, test and flight hardware has been produced by every major element of the SLS vehicle. Testing continues on engines, boosters, tanks and avionics. While the program has experienced engineering challenges typical of a new development, it continues to make steady progress toward the first SLS mission in roughly two years and a sustained cadence of missions thereafter. This paper will discuss these and other technical and SLS programmatic successes and challenges over the past year and provide a preview of work ahead before first flight.

Cook, Jerry↗

The Relationship Between Workload and Performance in Air Traffic Control: Exploring the Influence of Levels of Automation and Variation in Task Demand

In an air traffic environment, task demand is dynamic. However, previous research has largely considered the association of task demand and controller performance using conditions of stable task demand. Further, there is a comparatively restricted understanding of the influence of task demand transitions on workload and performance in association with different types and levels of automation that are available to controllers. This study used an air traffic control simulation to investigate the influence of task demand transitions, and two conditions of automation, on workload and efficiency-related performance. Findings showed that both the direction of the task demand variation and the amount of automation influenced the relationship between workload and performance. Findings are discussed in relation to capacity and arousal theories. Further research is needed to enhance understanding of demand transition and workload history effects on operator experience and performance, in both air traffic control and other safety-critical domains.

function allocation↗

NASA CA Operations Devolution: Status Update

What is Devolution? Devolution is a spreading of CA (Conjunction Assessment) operations responsibilities to mission FOTs (Flight Operations Teams): Permits efficiencies in handling the increased workload caused by Space Fence and large constellations; Missions given more flexibility in choosing specific approach to CA requirements that resonates best with their particular needs; CARA (Conjunction Assessment Risk Analysis) retains Agency oversight through an established NASA Standard - will establish requirements for devolved CA preparations, processing, and operations conduct. Devolution is a PROPOSED paradigm under consideration by SMD (Space Missions Directorate): Number of activities required before Agency-level decision can be rendered; Agency requirements established via approved CA Standard; Operational experience testimony from two separate pilot programs; After these activities complete, decision will be made whether devolution is a feasible option for missions; CARA is recommending devolution to exist as an option for missions.

conjunction↗

Task Demand Variation in Air Traffic Control: Implications for Workload, Fatigue, and Performance

In air traffic control, task demand and workload have important implications for the safety and efficiency of air traffic, and remain dominant considerations. Within air traffic control, task demand is dynamic. However, research on demand transitions and subsequent controller perception and performance is limited. This research uses an air traffic control simulation to investigate the effect of task demand transitions, and the direction of those transitions, on workload and fatigue and one efficiency performance measure. Results indicate that a change in task demand appears to affect both workload and fatigue ratings, although not necessarily performance. In addition, participants' workload and fatigue ratings in equivalent task demand periods appear to change depending on the demand period preceding the time of the current ratings. Further research is needed to enhance understanding of demand transition and workload history effects on operator experience and performance, in both air traffic control and other safety-critical domains.

workload history↗

Task Demand Variation in Air Traffic Control: Implications for Controller Workload, Fatigue, and Performance

In air traffic control, task demand and workload have important implications for the safety and efficiency of air traffic, and remain dominant considerations. Within air traffic control, task demand is dynamic. However, research on demand transitions and subsequent controller perception and performance is limited. This research uses an air traffic control simulation to investigate the effect of task demand transitions, and the direction of those transitions, on workload and fatigue and one efficiency performance measure. Results indicate that a change in task demand appears to affect both workload and fatigue ratings, although not necessarily performance. In addition, participants workload and fatigue ratings in equivalent task demand periods appear to change depending on the demand period preceding the time of the current ratings. Further research is needed to enhance understanding of demand transition and workload history effects on operator experience and performance, in both air traffic control and other safety-critical domains.

workload history↗

NASA’s Space Launch System: Enabling a New Generation of Lunar Exploration

Following two decades of operational experience in low-Earth orbit (LEO), NASA has turned its focus once again to deep space exploration. The Agency is building the Space Launch System (SLS) to take astronauts and cargo to the Moon and send robotic spacecraft deep into the solar system. Offering unmatched performance, departure energy and payload capacity, SLS is designed to evolve into progressively more powerful configurations, enabling a new generation of human exploration of the Moon in preparation for future missions to Mars. The first build of the Block 1 vehicle is nearly complete for Exploration Mission-1 (EM-1), the first integrated flight of SLS and the Orion crew vehicle. EM-1 will send an uncrewed Orion to a distant retrograde lunar orbit in order to test and verify new systems, and along the way will deploy 13 6U-class CubeSats in deep space along the upper stage disposal trajectory after separation from Orion. The Agency’s current plans call for the first three missions on the SLS manifest to utilize the Block 1 vehicle in crew and cargo configurations. A more powerful evolved vehicle, Block 1B, will provide additional mass and volume performance using a new Exploration Upper Stage (EUS). Block 1B will lift 34 to 40 metric tons (t) to trans-lunar injection (TLI), depending on crew or cargo configuration. The Block 1B crew configuration will offer as much payload volume as industry-standard 5 m-diameter fairings to co-manifested payloads in a Universal Stage Adapter (USA). The Block 1B cargo variant will accommodate 8.4 meter-diameter fairings in 62.7-foot (19.1 meter) or 90-foot (27.4 meter) lengths. Adding smallsat secondary payloads to ride along with primary and co-manifested payloads on future flights may be possible, depending on mass margins. Leveraging a flight-proven, well-understood propulsion system, SLS’s flexible architecture, unmatched performance and expansive payload accommodations will open exciting new mission possibilities in deep space. Launches of habitat modules for NASA’s new Gateway lunar outpost, the next generation of robotic spacecraft to the far reaches of the solar system, large-aperture deep space telescopes, probes to interstellar space and the return of astronauts to the Moon are all possible with SLS.

Creech, Stephen D.↗

TPSAS-NF1676L-11132-DND

The Orion Pad Abort 1 Flight Test occurred on May 6th, 2010 at White Sands Missile Range in New Mexico. The test was the first for the Orion vehicle and was primarily a test of the Orion Launch Abort System’s ability to execute an abort from the launch pad. The test was successful, and, in most cases, results were well within predicted outcomes. For this test, the thermal control subsystem was an inherent part of the flight operations team. The thermal team provided pre-launch predictions of component temperatures, set component temperature limits, and monitored those limits during the flight operations process as part of the primary flight operations team. The thermal team was also responsible for day-of-flight predictions of the main abort motor’s propellant mean bulk temperature, a key launch constraint for the test. After the test, thermal data was collected, reviewed, and compared against pre-launch predictions showing very good agreement in most areas. Based on the pre-test and flight operations experience, a detailed list of lessons learned has been developed and will be reviewed prior to potential future Orion or other such flight tests.

Joseph F Gasbarre↗

TPSAS-NF1676L-11021-DND

The Orion Pad Abort 1 Flight Test occurred on May 6th, 2010 at White Sands Missile Range in New Mexico. The test was the first for the Orion vehicle and was primarily a test of the Orion Launch Abort System’s ability to execute an abort from the launch pad. The test was successful and in most cases results were well within predicted outcomes. For this test, the thermal control subsystem was an inherent part of the flight operations team. The thermal team provided pre-launch predictions of component temperatures, set component temperature limits, and monitored those limits during the flight operations process as part of the primary flight operations team. The thermal team was also responsible for day-of-flight predictions of the main abort motor’s propellant mean bulk temperature, a key launch constraint for the test. After the test, thermal data was collected, reviewed, and compared against pre-launch predictions showing very good agreement in most areas. Based on the pre-test and flight operations experience, a detailed list of lessons learned has been developed and will be reviewed prior to potential future Orion or other such flight tests.

Joseph F Gasbarre↗