Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “team orienteering”

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 55 records · Page 3
All sourcesNASA NTRSDOE OSTI
NASA NTRS2019

Nasa Centennial Challenge: Three Dimensional (3d) Printed Habitat, Phase 3

NASA's Centennial Challenges program uses prize competitions with the goal of accelerating innovation in the aerospace industry. Competitions in the Centennial Challenges portfolio have previously focused on advancements in space robotics, regolith excavation, bio-printing, astronaut suit design, small satellites, and solar-powered vehicles. NASA's Three Dimensional (3D) Printed Habitat Centennial Challenge represents a partnership between NASA and the non-profit partner: Bradley University, with co-sponsors Caterpillar, Bechtel, Brick and Mortar Ventures, the American Concrete Institute, and the United States Army Corps of Engineers (USACE) Engineer Research and Development Center (ERDC) to spur development in automated additive construction technologies. The challenge asks teams to design and construct a scaled and simulated Martian habitat using indigenous materials and large scale 3D automated printing systems. Phase 1 of the competition, held in 2015, was an architectural design competition for habitat concepts that could be 3D printed. Phase 2, completed in 2017, asked teams to develop feedstocks from indigenous materials and hydrocarbon polymer recyclables, and demonstrate automated printing systems to manufacture these feedstocks into test specimens to assess mechanical strength. This paper will discuss the Phase 3 competition, focusing on technology outcomes that can potentially be infused into both terrestrial and planetary construction applications. The Phase 3 competition was divided into two sub-competitions: 1) virtual construction, where teams created a high fidelity building information model (BIM) of their 3D-printed habitat design and 2) the construction competition, which required teams to 3D print a structural foundation and subject materials samples to freeze/thaw testing and impact testing (level 1), produce a habitat element and complete a hydrostatic test (level 2), and additively manufacture a 1:3 scale habitat onsite in a head to head competition at Caterpillar, inc.'s Edwards Demonstration & Learning Center near Peoria, Illinois over the course of three days (level 3). While the Phase 2 competition focused primarily on the development of novel feedstocks and robotic printing systems, Phase 3 emphasized the scale-up of these systems and autonomous operation (demonstrating the capability to operate systems on precursor missions prior to the arrival of crew, or terrestrially in field operation settings where human tending of a manufacturing system may be limited). The Phase 3 virtual construction levels yielded a number of novel habitat designs, including both modular habitats and vertically-oriented habitat concepts. The Phase 3 construction competition also challenged teams to autonomously place penetrations and interfacing elements in additively manufactured structures. The paper will emphasize potential applications for the new materials and technologies developed under the umbrella of the competition within NASA's portfolio and in Earth-based applications such as disaster response and infrastructure improvement.

Centennial challenge↗
NASA NTRS2013

Dawn Orbit Determination Team: Modeling and Fitting of Optical Data at Vesta

The Dawn spacecraft was launched on September 27th, 2007. Its mission is to consecutively rendezvous with and observe the two largest bodies in the main asteroid belt, Vesta and Ceres. It has already completed over a year's worth of direct observations of Vesta (spanning from early 2011 through late 2012) and is currently on a cruise trajectory to Ceres, where it will begin scientific observations in mid-2015. Achieving this data collection required careful planning and execution from all Dawn operations teams. Dawn's Orbit Determination (OD) team was tasked with reconstruction of the as-flown trajectory as well as determination of the Vesta rotational rate, pole orientation and ephemeris, among other Vesta parameters. Improved knowledge of the Vesta pole orientation, specifically, was needed to target the final maneuvers that inserted Dawn into the first science orbit at Vesta. To solve for these parameters, the OD team used radiometric data from the Deep Space Network (DSN) along with optical data reduced from Dawn's Framing Camera (FC) images. This paper will de-scribe the initial determination of the Vesta ephemeris and pole using a combination of radiometric and optical data, and also the progress the OD team has made since then to further refine the knowledge of Vesta's body frame orientation and rate with these data.

imagery↗
NASA NTRS2000

A NASA Spaceliner 100 Propulsion Oriented Technology Assessment

In response to a NASA request, the National Space Propulsion Synergy Team (SPST) team agreed to provide technical and programmatic support to NASA in formulating a Spaceliner 100 Technology Program. The SPST offered a broad cross-section of expertise and experience. Its membership consists of senior level, volunteer representatives from across government, industry, and academia. The purpose of this paper is to provide a summary of the SPST support of SL100, which culminated in a propulsion technologies assessment and prioritization workshop conducted at MSFC. The results of this workshop and the follow-up analysis are part of this report. Also included, is a review of some "lessons learned" that were solicited from the workshop participants.

Dankhoff, W.↗
NASA NTRS1977

VEEP - Vehicle Economy, Emissions, and Performance program

VEEP is a general-purpose discrete event simulation program being developed to study the performance, fuel economy, and exhaust emissions of a vehicle modeled as a collection of its separate components. It is written in SIMSCRIPT II.5. The purpose of this paper is to present the design methodology, describe the simulation model and its components, and summarize the preliminary results. Topics include chief programmer team concepts, the SDDL design language, program portability, user-oriented design, the program's user command syntax, the simulation procedure, and model validation.

Heimburger, D. A.↗
NASA NTRSDate not supplied

The Application of Artificial Intelligence Deep Learning to Visually Identify Micrometeoroid and Orbital Debris Impacts

Recent advances in Artificial Intelligence (AI) are changing the World. Novel approaches to training AI systems have led to dramatic reductions in the amount of time required. Training an AI system could take years and teams of people using traditional methods, but with the advancements of Deep Learning (DL) models this training can now be accomplished by an individual in a matter of minutes. The development of “fast AI” libraries has delivered AI to essentially everyone. Democratization of AI power has inspired many to revisit past problems that will benefit from DL approaches. For example, the application of AI has improved detection of breast cancer by 20% compared to traditional detection methods. Computer vision and machine learning are being used to identify soil deficiencies and provide planting recommendations to farmers. Success stories like these and many others have provided inspiration to see if AI can help improve one of our needed capabilities – that of visually identifying micrometeoroid and orbital debris (MMOD) impact damage to spacecraft from images of the spacecraft exterior. The need to visually locate and characterize spacecraft MMOD impact damage has been present since the early days of space travel. This is often done by either having a crew member take photographs of the spacecraft through a window using a hand-held camera or ground personnel directing externally-mounted cameras. The photographs are then transmitted back to Earth for visual analysis. This method of MMOD damage inspection works well and has been used on various spacecraft including the Space Shuttle and the International Space Station (ISS). One of the issues with the current method that we believe AI could improve is the speed and possibly the accuracy in identifying MMOD impacts. Note that detecting MMOD impacts in images can be very difficult. The visual appearance of an MMOD impact can change dramatically with lighting conditions, size of impact, depth of penetration, material types, surface waviness, fabric coverings, camera & lens, distance to surface, spacecraft orientation, analyst experience, and many other factors. Currently, this takes a team of highly-experienced specialists in both the fields of Image Analysis and MMOD impacts. This paper documents our initial research in training an AI DL model using the fast-AI library to identify actual and simulated MMOD impacts and perforations into exposed flat surfaces. While we recognize that this initial goal seems modest, it must be noted that what we have done would have taken teams of individuals and years of training just ten years ago. Our long-term goal is to add complexity and use-cases to the DL model being trained to expand the capabilities of this model so that it can be used to identify MMOD impacts on all types of spacecraft surfaces.

Cameron M Collins↗
NASA NTRS1981

Government and industry interactions in the development of clock technology

It appears likely that everyone in the time and frequency community can agree on goals to be realized through the expenditure of resources. These goals are the same as found in most fields of technology: lower cost, better performance, increased reliability, small size and lower power. Related aspects are examined in the process of clock and frequency standard development. Government and industry are reviewed in a highly interactive role. These interactions include judgements on clock performance, what kind of clock, expenditure of resources, transfer of ideas or hardware concepts from government to industry, and control of production. Successful clock development and production requires a government/industry relationship which is characterized by long-term continuity, multidisciplinary team work, focused funding and a separation of reliability and production oriented tasks from performance improvement/research type efforts.

Hellwig, H.↗
NASA NTRS2020

An MBSE-based Approach to Architecting a Robotic Sample Capture System Concept for Potential Mars Sample Return

A model-based systems engineering (MBSE) approach was applied to architecting an orbiting sample Capture and Orient Module (COM) system concept for a Capture, Contain, and Return System (CCRS) payload concept for the notional Mars Sample Return (MSR) campaign at the NASA Jet Propulsion Laboratory. An architecture framework was established, covering multiple organizational layers of the system, along with structural, behavioral, data, and requirements perspectives. A workflow process to implement the architecting activities within the COM engineering team was established. The approach helped maintain consistency in terminology, helped ensure alignment of structural, behavioral, data, and requirements elements within each organization layer, and guided the engineering team through an architecting process that helped develop the architecture for a Capture and Orient Module system concept.

Younse, Paulo↗
NASA NTRS2009

Extreme Programming: Maestro Style

"Extreme Programming: Maestro Style" is the name of a computer programming methodology that has evolved as a custom version of a methodology, called extreme programming that has been practiced in the software industry since the late 1990s. The name of this version reflects its origin in the work of the Maestro team at NASA's Jet Propulsion Laboratory that develops software for Mars exploration missions. Extreme programming is oriented toward agile development of software resting on values of simplicity, communication, testing, and aggressiveness. Extreme programming involves use of methods of rapidly building and disseminating institutional knowledge among members of a computer-programming team to give all the members a shared view that matches the view of the customers for whom the software system is to be developed. Extreme programming includes frequent planning by programmers in collaboration with customers, continually examining and rewriting code in striving for the simplest workable software designs, a system metaphor (basically, an abstraction of the system that provides easy-to-remember software-naming conventions and insight into the architecture of the system), programmers working in pairs, adherence to a set of coding standards, collaboration of customers and programmers, frequent verbal communication, frequent releases of software in small increments of development, repeated testing of the developmental software by both programmers and customers, and continuous interaction between the team and the customers. The environment in which the Maestro team works requires the team to quickly adapt to changing needs of its customers. In addition, the team cannot afford to accept unnecessary development risk. Extreme programming enables the Maestro team to remain agile and provide high-quality software and service to its customers. However, several factors in the Maestro environment have made it necessary to modify some of the conventional extreme-programming practices. The single most influential of these factors is that continuous interaction between customers and programmers is not feasible.

Norris, Jeffrey↗
NASA NTRS2014

Designing an Alternate Mission Operations Control Room

The Huntsville Operations Support Center (HOSC) is a multi-project facility that is responsible for 24x7 real-time International Space Station (ISS) payload operations management, integration, and control and has the capability to support small satellite projects and will provide real-time support for SLS launches. The HOSC is a service-oriented/ highly available operations center for ISS payloads-directly supporting science teams across the world responsible for the payloads. The HOSC is required to endure an annual 2-day power outage event for facility preventive maintenance and safety inspection of the core electro-mechanical systems. While complete system shut-downs are against the grain of a highly available sub-system, the entire facility must be powered down for a weekend for environmental and safety purposes. The consequence of this ground system outage is far reaching: any science performed on ISS during this outage weekend is lost. Engineering efforts were focused to maximize the ISS investment by engineering a suitable solution capable of continuing HOSC services while supporting safety requirements. The HOSC Power Outage Contingency (HPOC) System is a physically diversified compliment of systems capable of providing identified real-time services for the duration of a planned power outage condition from an alternate control room. HPOC was designed to maintain ISS payload operations for approximately three continuous days during planned HOSC power outages and support a local Payload Operations Team, International Partners, as well as remote users from the alternate control room located in another building.

Montgomery, Patty↗
NASA NTRS2005

Decentralized Formation Flying Control in a Multiple-Team Hierarchy

This paper presents the prototype of a system that addresses these objectives-a decentralized guidance and control system that is distributed across spacecraft using a multiple-team framework. The objective is to divide large clusters into teams of manageable size, so that the communication and computational demands driven by N decentralized units are related to the number of satellites in a team rather than the entire cluster. The system is designed to provide a high-level of autonomy, to support clusters with large numbers of satellites, to enable the number of spacecraft in the cluster to change post-launch, and to provide for on-orbit software modification. The distributed guidance and control system will be implemented in an object-oriented style using MANTA (Messaging Architecture for Networking and Threaded Applications). In this architecture, tasks may be remotely added, removed or replaced post-launch to increase mission flexibility and robustness. This built-in adaptability will allow software modifications to be made on-orbit in a robust manner. The prototype system, which is implemented in MATLAB, emulates the object-oriented and message-passing features of the MANTA software. In this paper, the multiple-team organization of the cluster is described, and the modular software architecture is presented. The relative dynamics in eccentric reference orbits is reviewed, and families of periodic, relative trajectories are identified, expressed as sets of static geometric parameters. The guidance law design is presented, and an example reconfiguration scenario is used to illustrate the distributed process of assigning geometric goals to the cluster. Next, a decentralized maneuver planning approach is presented that utilizes linear-programming methods to enact reconfiguration and coarse formation keeping maneuvers. Finally, a method for performing online collision avoidance is discussed, and an example is provided to gauge its performance.

Mueller, Joseph .↗
NASA NTRSDate not supplied

Repurposing Drilling Control Diagnostics for Subsurface Edge Detection and Boundary Advisement During Planetary Drilling

Informed decision-making during lunar drilling and sampling missions will require data monitoring tools and specialized ground data systems. Accurate and updated situational awareness, with ongoing data monitoring, is critical for timely responses by to incoming science data. Traverse plans and scheduled activities may need to be flexibly changed in order to react to unexpected data or situations. Unlike (for example) Mars missions, the relative lightspeed closeness of the Moon allows for near-real-time ground processing of incoming mission and instrument data. An Apollo-class lunar regolith drill will in a sense “travel” a meter or two vertically at a given subsurface characterization site. As the drill penetrates into lunar regolith, it is likely to encounter a range of material densities, orientations, fracture toughness, and (perhaps) ice percentages. Lunar drill telemetry can provide science teams with a valuable first look into the subsurface structure, the regolith bulk properties, and constituents at each drilled site. Real-time AI-based recognition and reaction to downhole situations has been developed for automated deeper drilling on Mars and beyond. We can leverage the same knowledge bases and pattern-matching as areal-time interpreter of the subsurface, a situational awareness tool during drilling operations. We recently (Sept. 2019) demonstrated this AI drilling monitoring and analysis capability, in control of in-situ drilling and sampling operations, mounted on a KREX-2 rover in Chile’s Atacama Desert. Terrestrial automated drilling log analyses in oil exploration have used similar machine learning techniques in classifying and identifying features in drilling logs –but these typically are designed assuming a drilling fluid influencing downhole measurements and data (permeability, resistivity). Drilling models and existing AI software designed to detect and respond to drilling faults and hard materials can be repurposed, for near-real-time (ground-based) interpretation of drilling telemetry –a potentially valuable advisory tool for strata boundaries and changes in drilling parameters. On the Moon, this approach could be used to study the structure and to some extent the composition of lunar regolith vs. borehole depth, based on recognizable variations in fracture hardness, drilling energy and penetration rates while actively drilling. Since the early 2000s, a series of increasingly-capable real-time drilling telemetry interpretation and characterization software tools have been developed. These subsurface models and software tools have monitored the real-time drilling data received, and automatically identified changes in drill behavior (e.g., encountering a harder target layer, bit inclusions, drill choking due to infall downhole, and others) correlating these with subsurface structures and features. We discuss the mappings between drill borehole parameters, faults or events detected, and modeled changes in rock layer boundaries, in examples drawn from field testing at analog sites in an Arctic impact crater, Rio Tinto, and Chile’s Atacama Desert. These demonstrate how subsurface structural boundaries led to fault detections and responses by the software.

drilling advisor↗
NASA NTRS2011

Mission Operations Planning and Scheduling System (MOPSS)

MOPSS is a generic framework that can be configured on the fly to support a wide range of planning and scheduling applications. It is currently used to support seven missions at Goddard Space Flight Center (GSFC) in roles that include science planning, mission planning, and real-time control. Prior to MOPSS, each spacecraft project built its own planning and scheduling capability to plan satellite activities and communications and to create the commands to be uplinked to the spacecraft. This approach required creating a data repository for storing planning and scheduling information, building user interfaces to display data, generating needed scheduling algorithms, and implementing customized external interfaces. Complex scheduling problems that involved reacting to multiple variable situations were analyzed manually. Operators then used the results to add commands to the schedule. Each architecture was unique to specific satellite requirements. MOPSS is an expert system that automates mission operations and frees the flight operations team to concentrate on critical activities. It is easily reconfigured by the flight operations team as the mission evolves. The heart of the system is a custom object-oriented data layer mapped onto an Oracle relational database. The combination of these two technologies allows a user or system engineer to capture any type of scheduling or planning data in the system's generic data storage via a GUI.

Wood, Terri↗
NASA NTRS2015

Mission Oriented Support and Theory (MOST) for MMS -- The Goddard Space Flight Center/University of California Los Angeles Interdisciplinary Science Program

The MOST IDS team was tasked with focusing on two general areas: The first was to participate with the Fast Plasma Investigation (FPI) team in the development of virtual detectors that model the instrument responses of the MMS FPI sensors. The virtual instruments can be 'flown through' both simulation data (from magnetohydrodynamic, hybrid, and kinetic simulations) and Cluster and THEMIS spacecraft data. The goal is to determine signatures of magnetic reconnection expected during the MMS mission. Such signatures can serve as triggers for selection of burst mode downloads. The chapter contributed by the FPI team covers that effort in detail and, therefore, most of that work has not been included here. The second area of emphasis, and the one detailed in this chapter, was to build on past and present knowledge of magnetic reconnection and its physical signatures. Below we describe intensive analyses of Cluster and THEMIS data together with theoretical models and simulations that delineate the plasma signatures that surround sites of reconnection, including the effects of turbulence as well as the detailed kinetic signatures that indicate proximity to reconnection sites. In particular, we point out that particles are energized in several regions, not only at the actual site of reconnection.

Goldstein, Melvyn L.↗
NASA NTRS1993

Object-oriented technologies in a multi-mission data system

The Operations Engineering Laboratory (OEL) at JPL is developing new technologies that can provide more efficient and productive ways of doing business in flight operations. Over the past three years, we have worked closely with the Multi-Mission Control Team to develop automation tools, providing technology transfer into operations and resulting in substantial cost savings and error reduction. The OEL development philosophy is characterized by object-oriented design, extensive reusability of code, and an iterative development model with active participation of the end users. Through our work, the benefits of object-oriented design became apparent for use in mission control data systems. Object-oriented technologies and how they can be used in a mission control center to improve efficiency and productivity are explained. The current research and development efforts in the JPL Operations Engineering Laboratory are also discussed to architect and prototype a new paradigm for mission control operations based on object-oriented concepts.

Murphy, Susan C.↗
NASA NTRS2006

The Human-Robot Interaction Operating System

In order for humans and robots to work effectively together, they need to be able to converse about abilities, goals and achievements. Thus, we are developing an interaction infrastructure called the "Human-Robot Interaction Operating System" (HRI/OS). The HRI/OS provides a structured software framework for building human-robot teams, supports a variety of user interfaces, enables humans and robots to engage in task-oriented dialogue, and facilitates integration of robots through an extensible API.

Fong, Terrence↗
NASA NTRSDate not supplied

NASA Space Communications and Navigation: One Network Evolution

The NASA Space Communications and Navigation (SCaN) Program is responsible for providing the essential connectivity to robotic and human space explorers. The missions relying on SCaN range from suborbital and balloon missions to those traveling beyond the edge of the solar system. The demands for communications and navigation services enabled by SCaN (and its affiliated partners) are projected to increase and outpace the current network capacity. At the same time, the Agency finds itself surrounded by a burgeoning commercial space marketplace, technological advancement, and other government agencies that share common interests in space resiliency, robustness, and performance. As a result, SCaN has begun pivoting toward commercial services and collaborating with partners to close capacity and capability gaps. Given these growing demands of the Agency there is increasing need for multi-network solutions. Future mission concepts will rely on both government and commercial capabilities, both Near Space Network capacity and Deep Space Network capacity. Integrating these diverse support services together from a technical, programmatic and implementation standpoint will be key to meet the growing needs of the future. To accomplish this, a more substantive shift is required, and SCaN is reshaping itself to be a customer-centric, service-oriented, high-performance leader in the space communications community. This paper outlines the SCaN One Team, One Mission, One Network approach, and provides a vision for future mission community experience that includes streamlined mission commitment interfaces and clear processes, dynamic network scheduling and load balancing, and higher efficiency data transport and delivery through the integration of cloud infrastructure and services.

Near Space Network↗
NASA NTRS1994

OOD/OOP experience in the Science Operations Center part of the ground system for X ray Timing Explorer mission

The Science Operations Center (SOC) for the X-ray Timing Explorer (XTE) mission is an important component of the XTE ground system. Its mandate includes: (1) command and telemetry for the three XTE instruments, using CCSDS standards; (2) monitoring of the real-time science operations, reconfiguration of the experiment and the instruments, and real-time commanding to address the targets of opportunity (TOO) and alternate observations; and (3) analysis, processing, and archival of the XTE telemetry, and the timely delivery of the data products to the principal investigator (PI) teams and the guest observers (GO). The SOC has two major components: the science operations facility (SOF) that addresses the first two objectives stated above and the guest observer facility (GOF) that addresses the third. The SOF has subscribed to the object oriented design and implementation; while the GOF uses the traditional approach in order to take advantage of the existing software developed in support of previous missions. This paper details the SOF development using the object oriented design (OOD), and its implementation using the object oriented programming (OOP) in C++ under Unix environment on client-server architecture using Sun workstations. It also illustrates how the object oriented (OO) and the traditional approaches coexist in SOF and GOF, the lessons learned, and how the OOD facilitated the distributed software development collaboratively by four different teams. Details are presented for the SOF system, its major subsystems, its interfaces with the rest of the XTE ground data system, and its design and implementation approaches.

Choudhary, Abdur Rahim↗