SEARCH · Engineering Papers

Results for “building prototypes”

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 289 records · Page 16

All sources NASA NTRS DOE OSTI

NASA NTRS2003

NASA Helps Keep the Light Burning for the Saturn Car Company

The Saturn Electronics & Engineering, Inc. (Saturn) facility in Marks, Miss., that produces lamp assemblies was experiencing itermittent problems with its automotive under the hood lamps. After numerous testing and engineering efforts, technicians could not pin down the root of the problem. So Saturn contacted the NASA Technology Assistance Program (TAP) at Stennis Space Center. The Marks production facility had been experiencing intermittent problems with under the hood lamp assemblies for some time. The failure rate, at 2 percent, was unacceptable. Every effort was made to identify the problem so that corrective action could be put in place. The problem was investigated and researched by Saturn's engineering department. In addition, Saturn brought in several independent testing laboratories. Other measures included examining the switch component suppliers and auditing them for compliance to the design specifications and for surface contaminants. All attempts to identify the factors responsible for the failures were inconclusive. In an effort to get to the root of the problem, and at the recommendation of the Mississippi Department of Economic Development, Saturn contacted the NASA TAP at Stennis. The NASA Materials and Contamination Laboratory, with assistance from the Stennis Prototype Laboratory, conducted a materials evaluation study on the switch components. The laboratory findings showed the failures were caused by a build-up of carbon-based contaminants on the switch components. Saturn Electronics & Engineering, Inc., is a minority-owned provider of contract manufacturing services to a diverse global marketplace. Saturn operates manufacturing facilities globally serving the North American, European, and Asian markets. Saturn's production facility in Marks, Mississippi, produces more than 1,000,000 lamps and switches monthly. "Since the NASA recommendations were implemented, our internal failure rate for intermittency has dropped to less than .02 percent. Most importantly, we restored our high-level of customer satisfaction. Stennis provided an invaluable service to our business," Patrick said. Both NASA and Saturn were pleased with the results form this technical assistance project. The Technology Assistance Program at Stennis makes available to the public NASA technical expertise and access to lab facilities. This project provided both services with a positive outcome.

Source record↗

NASA NTRS2004

Reading Through Paint

Two-dimensional data matrix symbols, which contain encoded letters and numbers, are permanently etched on items for identification. They can store up to 100 times more information than traditional bar codes. While the symbols provide several advantages over bar codes, once they are covered by paint they can no longer be read by optical scanners. Since most products are painted eventually, this presents a problem for industries relying on the symbols for identification and tracking. In 1987, NASA s Marshall Space Flight Center began studying direct parts marking with matrix symbols in order to track millions of Space Shuttle parts. Advances in the technology proved that by incorporating magnetic properties into the paints, inks, and pastes used to apply the matrix symbols, the codes could be read by a magnetic scanner even after being covered with paint or other coatings. NASA received a patent for such a scanner in 1998, but the system it used for development was not portable and was too costly. A prototype was needed as a lead-in to a production model. In the summer of 2000, NASA began seeking companies to build a hand-held scanner that would detect the Read Through Paint data matrix identification marks containing magnetic materials through coatings.

Source record↗

NASA NTRS2005

Coupled fvGCM-GCE Modeling System, 3D Cloud-Resolving Model and Cloud Library

Recent GEWEX Cloud System Study (GCSS) model comparison projects have indicated that cloud-resolving models (CRMs) agree with observations better than traditional singlecolumn models in simulating various types of clouds and cloud systems from Merent geographic locations. Current and future NASA satellite programs can provide cloud, precipitation, aerosol and other data at very fine spatial and temporal scales. It requires a coupled global circulation model (GCM) and cloudscale model (termed a super-parameterization or multiscale modeling framework, MMF) to use these satellite data to improve the understanding of the physical processes that are responsible for the variation in global and regional climate and hydrological systems. The use of a GCM will enable global coverage, and the use of a CRM will allow for better and more sophisticated physical parameteridon NASA satellite and field campaign cloud related datasets can provide initial conditions as well as validation for both the MMF and CRMs. A seed fund is available at NASA Goddard to build a MMF based on the 2D Goddard cumulus Ensemble (GCE) model and the Goddard finite volume general circulation model (fvGCM). A prototype MMF in being developed and production nms will be conducted at the beginning of 2005. In this talk, I will present: (1) A brief review on GCE model and its applications on precipitation processes, (2) The Goddard MMF and the major difference between two existing MMFs (CSU MMF and Goddard MMF), (3) A cloud library generated by Goddard MMF, and 3D GCE model, and (4) A brief discussion on the GCE model on developing a global cloud simulator.

Tao, Wei-Kuo↗

NASA NTRS2005

Coupled fvGCM-GCE Modeling System, 3D Cloud-Resolving Model and Cloud Library

Recent GEWEX Cloud System Study (GCSS) model comparison projects have indicated that cloud- resolving models (CRMs) agree with observations better than traditional single-column models in simulating various types of clouds and cloud systems from different geographic locations. Current and future NASA satellite programs can provide cloud, precipitation, aerosol and other data at very fine spatial and temporal scales. It requires a coupled global circulation model (GCM) and cloud-scale model (termed a super-parameterization or multi-scale modeling framework, MMF) to use these satellite data to improve the understanding of the physical processes that are responsible for the variation in global and regional climate and hydrological systems. The use of a GCM will enable global coverage, and the use of a CRM will allow for better and more sophisticated physical parameterization. NASA satellite and field campaign cloud related datasets can provide initial conditions as well as validation for both the MMF and CRMs. A seed fund is available at NASA Goddard to build a MMF based on the 2D Goddard Cumulus Ensemble (GCE) model and the Goddard finite volume general circulation model (fvGCM). A prototype MMF in being developed and production runs will be conducted at the beginning of 2005. In this talk, I will present: (1) A brief review on GCE model and its applications on precipitation processes, ( 2 ) The Goddard MMF and the major difference between two existing MMFs (CSU MMF and Goddard MMF), (3) A cloud library generated by Goddard MMF, and 3D GCE model, and (4) A brief discussion on the GCE model on developing a global cloud simulator.

Tao, Wei-Kuo↗

NASA NTRS2022

Scientist-Stakeholder Relationships Drive Carbon Data Product Transfer Effectiveness within NASA Program

Carbon cycle science is at the heart of research on global climate change and its long-term impacts, as it examines the exchange of carbon between the atmosphere, oceans, land, and the impact of fossil fuel emissions on this cycling. Given the urgency of the climate challenge, NASA’s Carbon Monitoring System (CMS) requires all funded investigators to identify and work with stakeholder organizations at project inception to accelerate the transfer of the products developed by funded research into decision making systems. In this study, we contribute to the literature through the implementation of a quantitative analysis of 908 unique survey responses from funded investigators to explore the maturity of the scientist-stakeholder engagement. The paper employs multiple correspondence analysis to provide evidence to support policy options to increase stakeholder integration into research programs. Despite limitations of the dataset used, we demonstrated that multiple funding rounds, long-standing relationships between the stakeholder and scientist, and the scientific productivity of the PI, including the ability to produce datasets and research papers on these datasets, all contribute to carbon products moving from research to operational use. The maturity of relationships between scientists and stakeholders was shown to result improved stakeholder engagement. The use of carbon products should be identified in every stage of the program, and that capacity building is needed to support both existing and newly identified stakeholders better understand and use CMS products. As Federal, State, and local policy on climate adaptation and mitigation matures, the need for information on carbon will expand. Building of stakeholder-scientist relationships in CMS results in an effective generation and use of datasets to support this need and prototype ways that improved information needed for decision making can be created.

Monitoring↗

NASA NTRS2022

Scientist-Stakeholder Relationships Drive Carbon Data Product Transfer Effectiveness within NASA Program

Carbon cycle science is at the heart of research on global climate change and its long-term impacts, as it examines the exchange of carbon between the atmosphere, oceans, land, and the impact of fossil fuel emissions on this cycling. Given the urgency of the climate challenge, NASA's Carbon Monitoring System (CMS) requires all funded investigators to identify and work with stakeholder organizations at project inception to accelerate the transfer of the products developed by funded research into decision making systems. In this study, we contribute to the literature through the implementation of a quantitative analysis of 908 unique survey responses from funded investigators to explore the maturity of the scientist-stakeholder engagement. The paper employs multiple correspondence analysis to provide evidence to support policy options to increase stakeholder integration into research programs. Despite limitations of the dataset used, we demonstrated that multiple funding rounds, long-standing relationships between the stakeholder and scientist, and the scientific productivity of the Principal Investigator, including the ability to produce datasets and research papers on these datasets, all contribute to carbon products moving from research to operational use. The maturity of relationships between scientists and stakeholders was shown to result improved stakeholder engagement. The use of carbon products should be identified in every stage of the program, and that capacity building is needed to support both existing and newly identified stakeholders better understand and use CMS products. As federal, state, and local policy on climate adaptation and mitigation matures, the need for information on carbon will expand. Building of stakeholder-scientist relationships in CMS results in an effective generation and use of datasets to support this need and prototype ways that improved information needed for decision making can be created.

Molly E Brown↗

NASA NTRSDate not supplied

Roadmap to Cooperative Operating Practices for Strategic Conflict Detection and Resolution in the Upper Class-E Traffic Management Concept

As the governing body of flight operations in the highly anticipated emergent area of Upper Class E airspace (60,000 ft and above), the Federal Aviation Administration (FAA) has recognized the potential for a possible extensible traffic management system for new entrants into this domain. Following the successes with Unmanned Aircraft Systems (UAS) Traffic Management (UTM) and Advanced / Urban Air Mobility (AAM / UAM) Traffic Management programs, FAA put forth an initial concept of operations for supporting the start of the Upper Class E Traffic Management (ETM) concept. Like UTM and AAM / UAM, ETM is envisioned to also be a community-based, industry driven cooperative management concept. However, tailoring it to be adaptable to the atmospheric communication, navigation, and surveillance deficits, as well as the diverse vehicle and mission profiles operating in the ETM environment will be the challenge. As such, the National Aeronautics and Space Administration (NASA) Ames Research Center has been investigating several technologies that will help enable industry in the development of this new type of cooperative operating environment. These technologies are being prototyped and will be tested in a collaborative evaluation of an initial ETM system in late 2023. The evaluation will concentrate on building out ETM system technologies that will inform the participants regarding operational intent sharing, strategic conflict detection, and the resultant deconfliction process. In addition to the technical aspects, key roles and responsibilities will need to be defined. This will be done through exploring community-agreed upon Cooperative Operating Practices (COPs) that include procedures and capabilities to aid in timely, strategic conflict identification and resolution to be developed during the evaluation. As an initial step to the evaluation, the ETM research team at NASA Ames solicited industry feedback on various aspects of ETM operations from subject matter experts. A virtual tabletop walkthrough session was held over a two-day period to follow a roadmap through the functional steps needed to build COPs, focusing on strategic conflict detection and resolution. Overall, the ETM tabletop provided insights into how the community wanted to instantiate the generation and sharing of operational intent, detect strategic conflicts and resolve those conflicts using a preliminary set of procedural community-agreed upon COPs.

Upper Class-E Traffic Management (ETM)↗

NASA NTRSDate not supplied

Roadmap to Cooperative Operating Practices for Strategic Conflict Detection and Resolution in the Upper Class E Traffic Management Concept

Upper Class E Traffic Management (ETM)↗

NASA NTRS2011

C-Band Airport Surface Communications System Standards Development. Phase II Final Report. Volume 1: Concepts of Use, Initial System Requirements, Architecture, and AeroMACS Design Considerations

This report is provided as part of ITT s NASA Glenn Research Center Aerospace Communication Systems Technical Support (ACSTS) contract NNC05CA85C, Task 7: New ATM Requirements-Future Communications, C-Band and L-Band Communications Standard Development and was based on direction provided by FAA project-level agreements for New ATM Requirements-Future Communications. Task 7 included two subtasks. Subtask 7-1 addressed C-band (5091- to 5150-MHz) airport surface data communications standards development, systems engineering, test bed and prototype development, and tests and demonstrations to establish operational capability for the Aeronautical Mobile Airport Communications System (AeroMACS). Subtask 7-2 focused on systems engineering and development support of the L-band digital aeronautical communications system (L-DACS). Subtask 7-1 consisted of two phases. Phase I included development of AeroMACS concepts of use, requirements, architecture, and initial high-level safety risk assessment. Phase II builds on Phase I results and is presented in two volumes. Volume I (this document) is devoted to concepts of use, system requirements, and architecture, including AeroMACS design considerations. Volume II describes an AeroMACS prototype evaluation and presents final AeroMACS recommendations. This report also describes airport categorization and channelization methodologies. The purposes of the airport categorization task were (1) to facilitate initial AeroMACS architecture designs and enable budgetary projections by creating a set of airport categories based on common airport characteristics and design objectives, and (2) to offer high-level guidance to potential AeroMACS technology and policy development sponsors and service providers. A channelization plan methodology was developed because a common global methodology is needed to assure seamless interoperability among diverse AeroMACS services potentially supplied by multiple service providers.

Hall, Edward↗

NASA NTRS2011

C-Band Airport Surface Communications System Standards Development. Phase II Final Report. Volume 2: Test Bed Performance Evaluation and Final AeroMACS Recommendations

This report is provided as part of ITT s NASA Glenn Research Center Aerospace Communication Systems Technical Support (ACSTS) contract NNC05CA85C, Task 7: New ATM Requirements-Future Communications, C-Band and L-Band Communications Standard Development and was based on direction provided by FAA project-level agreements for New ATM Requirements-Future Communications. Task 7 included two subtasks. Subtask 7-1 addressed C-band (5091- to 5150-MHz) airport surface data communications standards development, systems engineering, test bed and prototype development, and tests and demonstrations to establish operational capability for the Aeronautical Mobile Airport Communications System (AeroMACS). Subtask 7-2 focused on systems engineering and development support of the L-band digital aeronautical communications system (L-DACS). Subtask 7-1 consisted of two phases. Phase I included development of AeroMACS concepts of use, requirements, architecture, and initial high-level safety risk assessment. Phase II builds on Phase I results and is presented in two volumes. Volume I is devoted to concepts of use, system requirements, and architecture, including AeroMACS design considerations. Volume II (this document) describes an AeroMACS prototype evaluation and presents final AeroMACS recommendations. This report also describes airport categorization and channelization methodologies. The purposes of the airport categorization task were (1) to facilitate initial AeroMACS architecture designs and enable budgetary projections by creating a set of airport categories based on common airport characteristics and design objectives, and (2) to offer high-level guidance to potential AeroMACS technology and policy development sponsors and service providers. A channelization plan methodology was developed because a common global methodology is needed to assure seamless interoperability among diverse AeroMACS services potentially supplied by multiple service providers.

Hall, Edward↗

NASA NTRSDate not supplied

A Notional Artemis Lunar Surface Exploration Package (ArLSEP) based on the Gandalf Staff Platform

Introduction: The Artemis program is planning to deliver crew and cargo to the lunar surface, but there is no current package for supporting lunar in-struments and experiments similar to the Apollo Lunar Surface Exploration Package (ALSEP). This abstract provides a possible concept for such a package using the Gandalf Staff Platform as a common core. Gandalf Staff: The Gandalf Staff is an early prototype system developed over FY’21/FY’22 using NASA Science Technology Mission Directorate (STMD) Center Information Fund (CIF) grants to de-sign, build and test “proof-of-concept” components. These components include a 24v battery powered monopole that powers a suite of subsystems, including a Graphical User Interface (GUI) for crew, surface voice and data communications, Lunar Search and Rescue (LunaSAR) navigation and communications, LiDAR, field site external lighting, 360-degree camera, and a geothermal instrument for measuring sub-surface temperature gradient. The staff can be carried independently by an Extra-Vehicular Activity (EVA) astronaut, or can be mounted into a tripod for “hands free” support at a surface site being investigated. The staff can be attached to an external solar array and power storage system for long-duration operations. [1,2] ALSEP: An ASLEP flew on each mission Apollo 12 to Apollo 17. For Apollo 11, a simplified packaged called the Early Apollo Scientific Experiments Pack-age (EASEP) was flown. Each package included a “Central Station” that provided the power and communications connected to a variety of instruments and sensors. The power was provided by a Radioisotope Thermoelectric Generator (RTG) fueled by Plutoni-um-238 generating 70 watts of power (initially, decayed over time) [3]. The communications system provide for direct to Earth data transfer from the lunar surface. Each pack-age was stowed externally in the Lunar Module (LM) Scientific Equipment (SEQ) bay with a mass up to 163 kg (Apollo 17). The crew unloaded the ALSEP from the LM and deployed the instruments on the lunar surface. Although designed to operate for only 1 year, many sites operated for up to 8 years successfully [4]. The Active Seismic Experiment (ASE) included 3 geophones for detecting seismic waves created by mortars and thumpers deployed by the crew. Other active experiments measured the lunar atmosphere, the heat flow in the subsurface, the lunar gravity and potential gravity waves, the lunar magnetic field, the solar wind and plasma interactions in cislunar space. Passive experiments included collectors for dust and cosmic rays, and retroreflectors for precise measurements of distance using a laser from Earth. The ALSEP program continues to generate insights into lunar formation and evolution. ArLSEP Concepts: The lunar surface science package for the Artemis program will hopefully exceed the capability of the ALSEP. There are multiple issues for discussion leading to the design of a new ArLSEP, needing requirements definition from the science community, NASA mission architecture, and NASA budget planners. 1. Delivery Mechanism Two possible projects currently provide capability to deliver scientific cargo to the lunar surface: 1) the Commercial Lunar Payload Services (CLPS) [5] and the Human Landing System (HLS) [6, 7]. Each project is controlled by a different organization within NASA and budgeted with different criteria although both support lunar exploration. The HLS system delivers crew (and potentially cargo) to human landing sites. If an ArLSEP is “predeployed” to such a site, the design must include power (either from the vehicle or independently) to keep the electronics functioning until deployed by the crew. If an ArLSEP is delivered on a vehicle after the crew is present on the lunar surface, safety protocols require adequate distance from the humans for impact from descent propelled sur-face regolith ejecta. This distance can not exceed the capability of the crew to walk (if no rover) to the vehicle for ArLSEP deployment. 2. Overall Guidelines The general design of ArLSEP will likely follow the ALSEP with a common system for communications and power; however, significant architecture differences between Apollo and Artemis exist. Power: The RTG will not be available for early Artemis missions nor likely follow-on Lunar Exploration Transportation Services (LETS) missions [8]. Thus, ArLSEP power must be supplied by solar arrays with sufficient battery capability to “keep alive” necessary electronics during any lunar surface eclipse period. Communication: The Artemis program is developing a series of communications satellites for lunar orbit to provide surface transmission of data and voice to Earth. Called “LunaNET”, this network is component useful for ArLSEP since south polar locations may not always have direct “line-of-sight” to Earth [9]. 3. Concept of Operations (ConOps) The general ConOps for ArLSEP is to deliver the package to lunar surface before the crew arrives, and then have the crew deploy the package after some period of time. This requires coordinated design (for power systems) and launch window (for schedule) on both the cargo and crew missions. Once the ArLSEP is deployed, it will operate autonomously for a number of years. It should be designed to be EVA compatible for crew maintenance and upgrade. 4. Notional Design (for discussion purpose only) The landing site near the South Pole is expected to have no eclipse cycle exceeding 5 days, so the “keep alive” power is 144 hours (6 days to include margin). A 12v ArLSEP will use rechargeable LiFePO4 cells, which are common in the Electric Vehicle (EV) industry. With a current of 5 amps and a 125 watt system, the mass is about 90kg. The comm. system and structure adds another 10kg, thus the “Central Station” is approximately 100kg. The solar power is collected on four arrays (each 2m above the surface), and the entire ArLSEP is designed to stow in a 2m x 1m x 1m volume. The experiment and instrument design will vary for each installation and add mass to the total (although they are expected to fit within the 2m3 volume). Seismic wave generation will likely not be provided with mortars, thus an electric “thumper” will be required. Active instruments such as imaging systems and sensing instruments will benefit from the additional power and communication capability provided by ArLSEP. Passive systems such as retroreflectors, witness plates, and cosmic dust collectors can be added to either the landing vehicle and/or the ArLSEP. With repeated HLS missions to the same human site, the ArLSEP can be expanded and easily maintained for long duration science collection on the lunar surface.

ALSEP↗

NASA NTRS2012

Materials and Process Activities for NASA's Composite Crew Module

In January 2007, the NASA Administrator and Associate Administrator for the Exploration Systems Mission Directorate chartered the NASA Engineering and Safety Center (NESC) to design, build, and test a full-scale Composite Crew Module (CCM). The overall goal of the CCM project was to develop a team from the NASA family with hands-on experience in composite design, manufacturing, and testing in anticipation of future space exploration systems being made of composite materials. The CCM project was planned to run concurrently with the Orion project s baseline metallic design within the Constellation Program so that features could be compared and discussed without inducing risk to the overall Program. The materials and process activities were prioritized based on a rapid prototype approach. This approach focused developmental activities on design details with greater risk and uncertainty, such as out-of-autoclave joining, over some of the more traditional lamina and laminate building block levels. While process development and associated building block testing were performed, several anomalies were still observed at the full-scale level due to interactions between process robustness and manufacturing scale-up. This paper describes the process anomalies that were encountered during the CCM development and the subsequent root cause investigations that led to the final design solutions. These investigations highlight the importance of full-scale developmental work early in the schedule of a complex composite design/build project.

Polis, Daniel L.↗

NASA NTRS1996

An Assessment of IMPAC - Integrated Methodology for Propulsion and Airframe Controls

This report documents the work done under a NASA sponsored contract to transition to industry technologies developed under the NASA Lewis Research Center IMPAC (Integrated Methodology for Propulsion and Airframe Control) program. The critical steps in IMPAC are exercised on an example integrated flight/propulsion control design for linear airframe/engine models of a conceptual STOVL (Short Take-Off and Vertical Landing) aircraft, and MATRIXX (TM) executive files to implement each step are developed. The results from the example study are analyzed and lessons learned are listed along with recommendations that will improve the application of each design step. The end product of this research is a set of software requirements for developing a user-friendly control design tool which will automate the steps in the IMPAC methodology. Prototypes for a graphical user interface (GUI) are sketched to specify how the tool will interact with the user, and it is recommended to build the tool around existing computer aided control design software packages.

Walker, G. P.↗

NASA NTRS1999

I/O Parallelization for the Goddard Earth Observing System Data Assimilation System (GEOS DAS)

The National Aeronautics and Space Administration (NASA) Data Assimilation Office (DAO) at the Goddard Space Flight Center (GSFC) has developed the GEOS DAS, a data assimilation system that provides production support for NASA missions and will support NASA's Earth Observing System (EOS) in the coming years. The DAO's support of the EOS project along with the requirement of producing long-term reanalysis datasets with an unvarying system levy a large I/O burden on the future system. The DAO has been involved in prototyping parallel implementations of the GEOS DAS for a number of years and is now converting the production version from shared-memory parallelism to distributed-memory parallelism using the portable Message-Passing Interface (MPI). If the MPI-based GEOS DAS is to meet these production requirements, we must make I/O from the parallel system efficient. We have designed a scheme that allows efficient I/O processing while retaining portability, reducing the need for post-processing, and producing data formats that are required by our users, both internal and external. The first phase of the GEOS DAS Parallel I/O System (GPIOS) will expand upon the common method of gathering global data to a Single PE for output. Instead of using a PE also tasked with primary computation, a number of PEs will be dedicated to I/O and its related tasks. This allows the data transformations and formatting required prior to output to take place asynchronously with respect to the GEOS DAS assimilation cycle, improving performance and generating output data sets in a format convenient for our users. I/O PEs can be added as needed to handle larger data volumes or to meet user file specifications. We will show I/O performance results from a prototype MPI GCM integrated with GPIOS. Phase two of GPIOS development will examine ways of integrating new software technologies to further improve performance and build scalability into the system. The maturing of MPI-IO implementations and other supporting libraries such as parallel HDF should provide performance gains while retaining portability.

Lucchesi, R.↗

NASA NTRS2005

Advanced Opto-Electronics (LIDAR and Microsensor Development)

Our overall intent in this aspect of the project were to establish a collaborative effort between several departments at Montana State University for developing advanced optoelectronic technology for advancing the state-of-the-art in optical remote sensing of the environment. Our particular focus was on development of small systems that can eventually be used in a wide variety of applications that might include ground-, air-, and space deployments, possibly in sensor networks. Specific objectives were to: 1) Build a field-deployable direct-detection lidar system for use in measurements of clouds, aerosols, fish, and vegetation; 2) Develop a breadboard prototype water vapor differential absorption lidar (DIAL) system based on highly stable, tunable diode laser technology developed previously at MSU. We accomplished both primary objectives of this project, in developing a field-deployable direct-detection lidar and a breadboard prototype of a water vapor DIAL system. Paper summarizes each of these accomplishments.

Vanderbilt, Vern C.↗

NASA NTRS2005

MER : from landing to six wheels on Mars ... twice

Application of the Pathfinder landing system design to enclose the much larger Mars Exploration Rover required a variety of Rover deployments to achieve the surface driving configuration. The project schedule demanded that software design, engineering model test, and flight hardware build to be accomplished in parallel. This challenge was met through (a) bounding unknown environments against which to design and test, (b) early mechanical prototype testing, (c) constraining the scope of on-board autonomy to survival-critical deployments, (d) executing a balance of nominal and off-nominal test cases, (e) developing off-nominal event mitigation techniques before landing, (f) flexible replanning in response to surprises during operations. Here is discussed several specific events encountered during initial MER surface operations.

Mars Exploration Rover (MER)↗

NASA NTRS2006

Point-to-Point! Validation of the Small Aircraft Transportation System Higher Volume Operations Concept

Described is the research process that NASA researchers used to validate the Small Aircraft Transportation System (SATS) Higher Volume Operations (HVO) concept. The four phase building-block validation and verification process included multiple elements ranging from formal analysis of HVO procedures to flight test, to full-system architecture prototype that was successfully shown to the public at the June 2005 SATS Technical Demonstration in Danville, VA. Presented are significant results of each of the four research phases that extend early results presented at ICAS 2004. HVO study results have been incorporated into the development of the Next Generation Air Transportation System (NGATS) vision and offer a validated concept to provide a significant portion of the 3X capacity improvement sought after in the United States National Airspace System (NAS).

Williams, Daniel M.↗

NASA NTRS2016

Testing and Characterization of a Prototype Telescope for the Evolved Laser Interferometer Space Antenna (eLISA)

We describe our efforts to fabricate, test and characterize a prototype telescope for the eLISA mission. Much of our work has centered on the modeling and measurement of scattered light performance. This work also builds on a previous demonstration of a high dimensional stability metering structure using particular choices of materials and interfaces. We will discuss ongoing plans to merge these two separate demonstrations into a single telescope design demonstrating both stray light and dimensional stability requirements simultaneously.

gravitational waves↗