Search NASASearch

SEARCH · Search NASA

Results for “protocol processing”

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

Resource Tracking Model Updates and Trade Studies

The Resource tracking model has been updated to capture system manager and project manager inputs. Both the Trick/GUNNS RTM simulator and the RTM mass balance spreadsheet have been revised to address inputs from system managers and to refine the way mass balance is illustrated. The revisions to the RTM included addition of a Plasma Pyrolysis Assembly (PPA) to recover hydrogen from Sabatier reactor methane which was vented in the prior version of the RTM. The effect of the PPA on the overall balance of resources in an exploration vehicle is illustrated in the increased recycle of vehicle oxygen. Additionally simulation of EVAs conducted from the exploration module was added. Since the focus of the exploration module is to provide a habitat during deep space operations the EVA simulation approach to EVA is based on ISS EVA protocol and processes. Case studies have been run to show the relative effect of performance changes on vehicle resources.

Chambliss, Joe

Expanding NASA and Roscosmos Scientific Collaboration on the International Space Station

The International Space Station (ISS) is a world-class laboratory orbiting in space. NASA and Roscosmos have developed a strong relationship through the ISS Program Partnership, working together and with the other ISS Partners for more than twenty years. Since 2013, based on a framework agreement between the Program Managers, NASA and Roscosmos are building a joint program of collaborative research on ISS. This international collaboration is developed and implemented in phases. Initially, members of the ISS Program Science Forum from NASA and TsNIIMash (representing Roscosmos) identified the first set of NASA experiments that could be implemented in the "near term". The experiments represented the research categories of Technology Demonstration, Microbiology, and Education. Through these experiments, the teams from the "program" and "operations" communities learned to work together to identify collaboration opportunities, establish agreements, and jointly plan and execute the experiments. The first joint scientific activity on ISS occurred in January 2014, and implementation of these joint experiments continues through present ISS operations. NASA and TsNIIMash have proceeded to develop "medium term" collaborations, where scientists join together to improve already-proposed experiments. A major success is the joint One-Year Mission on ISS, with astronaut Scott Kelly and cosmonaut Mikhail Kornienko, who returned from ISS in March, 2016. The teams from the NASA Human Research Program and the RAS Institute for Biomedical Problems built on their considerable experience to design joint experiments, learn to work with each other's protocols and processes, and share medical and research data. New collaborations are being developed between American and Russian scientists in complex fluids, robotics, rodent research and space biology, and additional human research. Collaborations are also being developed in Earth Remote Sensing, where scientists will share data from imaging systems mounted on ISS as well as other orbiting spacecraft to improve our understanding of the Earth and its climate. NASA and Roscosmos continue to encourage international scientific cooperation and expanded use of the ISS Laboratory. "Long-term", larger collaborations will achieve scientific objectives that no single national science team or agency can achieve on its own. The joint accomplishments achieved so far have paved the way for a stronger international scientific community and improved results and benefits from ISS.

Hasbrook, Pete

Desert Research and Technology Studies (D-RATS) 2022 Test Report

The primary purpose of the 2022 Desert Research and Technology Studies (D-RATS 22) analog mission field test was to provide data and recommendations regarding how pressurized rover (PR) design, cabin configuration, driving modes, timeline constraints, and mission operations can be acceptably implemented to support future Artemis missions that include a PR. The goal of these evaluations was to provide first order feedback and data on design concepts currently being traded as options for future pressurized rover flight prototypes. The Japan Aerospace Exploration Agency (JAXA) may provide a PR for future Artemis missions. One of the primary objectives of D-RATS 2022 was to share with the JAXA PR team the processes and protocols by which NASA has learned to successfully evaluate rover concepts through integrated HITL evaluations over the past 20+ years, so that JAXA could apply any applicable lessons learned to their PR design, development, testing, and evaluation.

analog

An Approach to Verification and Validation of a Reliable Multicasting Protocol

This paper describes the process of implementing a complex communications protocol that provides reliable delivery of data in multicast-capable, packet-switching telecommunication networks. The protocol, called the Reliable Multicasting Protocol (RMP), was developed incrementally using a combination of formal and informal techniques in an attempt to ensure the correctness of its implementation. Our development process involved three concurrent activities: (1) the initial construction and incremental enhancement of a formal state model of the protocol machine; (2) the initial coding and incremental enhancement of the implementation; and (3) model-based testing of iterative implementations of the protocol. These activities were carried out by two separate teams: a design team and a V&V team. The design team built the first version of RMP with limited functionality to handle only nominal requirements of data delivery. In a series of iterative steps, the design team added new functionality to the implementation while the V&V team kept the state model in fidelity with the implementation. This was done by generating test cases based on suspected errant or offnominal behaviors predicted by the current model. If the execution of a test was different between the model and implementation, then the differences helped identify inconsistencies between the model and implementation. The dialogue between both teams drove the co-evolution of the model and implementation. Testing served as the vehicle for keeping the model and implementation in fidelity with each other. This paper describes (1) our experiences in developing our process model; and (2) three example problems found during the development of RMP.

Callahan, John R.

An approach to verification and validation of a reliable multicasting protocol

This paper describes the process of implementing a complex communications protocol that provides reliable delivery of data in multicast-capable, packet-switching telecommunication networks. The protocol, called the Reliable Multicasting Protocol (RMP), was developed incrementally using a combination of formal and informal techniques in an attempt to ensure the correctness of its implementation. Our development process involved three concurrent activities: (1) the initial construction and incremental enhancement of a formal state model of the protocol machine; (2) the initial coding and incremental enhancement of the implementation; and (3) model-based testing of iterative implementations of the protocol. These activities were carried out by two separate teams: a design team and a V&V team. The design team built the first version of RMP with limited functionality to handle only nominal requirements of data delivery. In a series of iterative steps, the design team added new functionality to the implementation while the V&V team kept the state model in fidelity with the implementation. This was done by generating test cases based on suspected errant or off-nominal behaviors predicted by the current model. If the execution of a test was different between the model and implementation, then the differences helped identify inconsistencies between the model and implementation. The dialogue between both teams drove the co-evolution of the model and implementation. Testing served as the vehicle for keeping the model and implementation in fidelity with each other. This paper describes (1) our experiences in developing our process model; and (2) three example problems found during the development of RMP.

Callahan, John R.

Suited Ground Vacuum Chamber Testing Decompression Sickness Tiger Team Report

Suited vacuum chamber testing is critical to flight crew training, sustaining engineering, and development engineering. Most suited vacuum chamber testing at NASA’s Johnson Space Center (JSC) involves crewmembers or human test subjects working at a hypobaric pressure of 4.3 psia, which requires that an oxygen prebreathe be performed prior to decompression to reduce the risk of decompression sickness (DCS). Since 1986, NASA’s policy has been to require a 4-hour resting prebreathe for hypobaric chamber exposures of 4.2 psia lasting greater than 30 minutes. There have been no reports of Type II (i.e., serious, potentially life-threatening) DCS at NASA while using this prebreathe protocol. Several chamber runs, believed to be approximately 5% of all runs, are believed to have been terminated due to Type I DCS symptoms that were performance impairing; however, detailed records of DCS symptoms during suited vacuum chamber runs are not available. The adequacy of the 4-hour prebreathe protocol, as well as the processes by which prebreathe protocols and policies are established, became the subject of significant discussion in April 2018 when medical planning was initiated for chamber runs that were scheduled to occur later in 2018 that would last 8 hours or more with high metabolic rates.

Abercromby, Andrew F. J.

Low Resolution Picture Transmission (LRPT) Demonstration System

Low-Resolution Picture Transmission (LRPT) is a proposed standard for direct broadcast transmission of satellite weather images. This standard is a joint effort by the European Organization for the Exploitation of Meteorological Satellites (EUMETSAT) and the National Oceanic Atmospheric Administration (NOAA). As a digital transmission scheme, its purpose is to replace the current analog Automatic Picture Transmission (APT) system for use in the Meteorological Operational (METOP) satellites. Goddard Space Flight Center has been tasked to build an LRPT Demonstration System (LDS). It's main objective is to develop or demonstrate the feasibility of a low-cost receiver utilizing a Personal Computer (PC) as the primary processing component and determine the performance of the protocol in the simulated Radio Frequency (RF) environment. The approach would consist of two phases. In the phase 1, a Commercial-off-the-Shelf (COTS) Modulator-Demodulator (MODEM) board that would perform RF demodulation would be purchased allowing the Central Processing Unit (CPU) to perform the Consultative Committee for Space Data Systems (CCSDS) protocol processing. Also since the weather images are compressed the PC would perform the decompression. Phase 1 was successfully demonstrated on December 1997. Phase 2 consists of developing a high-fidelity receiver, transmitter and environment simulator. Its goal is to find out how the METOP Specification performs in a simulated noise environment in a cost-effective receiver. The approach would be to produce a receiver using as much software as possible to perform front-end processing to take advantage of the latest high-speed PCs. Thus the COTS MODEM used in Phase 1 is performing RF demodulation along with data acquisition providing data to the receiving software. Also, environment simulator is produced using the noise patterns generated by Institute for Telecommunications Sciences (ITS) from their noise environment study.

Fong, Wai

An approach to verification and validation of a reliable multicasting protocol: Extended Abstract

This paper describes the process of implementing a complex communications protocol that provides reliable delivery of data in multicast-capable, packet-switching telecommunication networks. The protocol, called the Reliable Multicasting Protocol (RMP), was developed incrementally using a combination of formal and informal techniques in an attempt to ensure the correctness of its implementation. Our development process involved three concurrent activities: (1) the initial construction and incremental enhancement of a formal state model of the protocol machine; (2) the initial coding and incremental enhancement of the implementation; and (3) model-based testing of iterative implementations of the protocol. These activities were carried out by two separate teams: a design team and a V&V team. The design team built the first version of RMP with limited functionality to handle only nominal requirements of data delivery. This initial version did not handle off-nominal cases such as network partitions or site failures. Meanwhile, the V&V team concurrently developed a formal model of the requirements using a variant of SCR-based state tables. Based on these requirements tables, the V&V team developed test cases to exercise the implementation. In a series of iterative steps, the design team added new functionality to the implementation while the V&V team kept the state model in fidelity with the implementation. This was done by generating test cases based on suspected errant or off-nominal behaviors predicted by the current model. If the execution of a test in the model and implementation agreed, then the test either found a potential problem or verified a required behavior. However, if the execution of a test was different in the model and implementation, then the differences helped identify inconsistencies between the model and implementation. In either case, the dialogue between both teams drove the co-evolution of the model and implementation. We have found that this interactive, iterative approach to development allows software designers to focus on delivery of nominal functionality while the V&V team can focus on analysis of off nominal cases. Testing serves as the vehicle for keeping the model and implementation in fidelity with each other. This paper describes (1) our experiences in developing our process model; and (2) three example problems found during the development of RMP. Although RMP has provided our research effort with a rich set of test cases, it also has practical applications within NASA. For example, RMP is being considered for use in the NASA EOSDIS project due to its significant performance benefits in applications that need to replicate large amounts of data to many network sites.

Callahan, John R.

Communication-Gateway Software For NETEX, DECnet, And TCP/IP

Communications gateway software, GATEWAY, provides process-to-process communication between remote applications programs in different protocol domains. Communicating peer processes may be resident on any paired combination of NETEX, DECnet, or TCP/IP hosts. Provides necessary mapping from one protocol to another and facilitates practical intermachine communications in cost-effective manner by eliminating need to standardize on single protocol or to implement multiple protocols in host computers. Written in Ada.

Keith, B.

The development and application of composite complexity models and a relative complexity metric in a software maintenance environment

A great deal of effort is now being devoted to the study, analysis, prediction, and minimization of software maintenance expected cost, long before software is delivered to users or customers. It has been estimated that, on the average, the effort spent on software maintenance is as costly as the effort spent on all other software costs. Software design methods should be the starting point to aid in alleviating the problems of software maintenance complexity and high costs. Two aspects of maintenance deserve attention: (1) protocols for locating and rectifying defects, and for ensuring that noe new defects are introduced in the development phase of the software process; and (2) protocols for modification, enhancement, and upgrading. This article focuses primarily on the second aspect, the development of protocols to help increase the quality and reduce the costs associated with modifications, enhancements, and upgrades of existing software. This study developed parsimonious models and a relative complexity metric for complexity measurement of software that were used to rank the modules in the system relative to one another. Some success was achieved in using the models and the relative metric to identify maintenance-prone modules.

Hops, J. M.

Overview of the Digitization Workflow Post Image Acquisition of Apollo Lunar and Antarctic Meteorite Samples Using Agisoft Photoscan for the NASA 3D Astromaterials Virtual Samples Collection

The 3D Virtual Astromaterials Samples (3DVAS) collection is a multi-year funded project to create a digital database of sixty Apollo Lunar and Antarctic Meteorite samples following non-destructive documentation conservation protocols. After initial image processing, the photos are evaluated and processed using unique structure-from-motion photogrammetric techniques in a high performance modelling software designed to create a 3D model from 2D images: Agisoft Photoscan Pro. Agisoft Photoscan Pro uses image processing algorithms and techniques originating in computer vision to resolve 3D models for accurate and detailed visualization of a subject. The software provides a stepwise process that is tailored per model based on spatial and specular reflectance properties, for example. The process includes: photo alignment, creation of a dense point cloud, mesh, and finally texture. Photo alignment is dependent on model properties. The 3DVAS process requires a special rotation platform with calibrated photogrammetric targets, specific distance rotation protocols, and a contrasting background for alignment and scale accuracy. As a result of the photographic process, alignment will complete with two mirrored hemispheres that, in a sense, represent the 2D images overlapping to create a 3D model. Each dense point cloud is analyzed with provided statistical measures in a gradual selection process to eliminate outliers. The point cloud is reduced to include only data valuable to the final model. When a precise dense point cloud is achieved, a mesh and texture are applied. Each model is scaled with scale bar accuracies within 100 microns. Each sample has its own intimate process for modelling; there is no standard for the parameters required in the final creation of a high resolution model. By processing multiple samples, a skill is gained in practice to allow a close definition of the original sample and will result in the most detailed version of the sample shell. This process completes one-fifth of the 3DVAS protocol for providing accurate digital documentation. Each model shell is merged with X-ray Computed Tomography data to create a full volumetric sample. All 3DVAS data will be served on NASA's Astromaterials Acquisition and Curation website with an early subset of data available in 2019 and the 3D Virtual Astromaterials Samples Collection launch in 2020.

Thomas, Andi B.

James Webb Space Telescope - L2 Communications for Science Data Processing

JWST is the first NASA mission at the second Lagrange point (L2) to identify the need for data rates higher than 10 megabits per second (Mbps). JWST will produce approximately 235 Gigabits of science data every day that will be downlinked to the Deep Space Network (DSN). To get the data rates desired required moving away from X-band frequencies to Ka-band frequencies. To accomplish this transition, the DSN is upgrading its infrastructure. This new range of frequencies are becoming the new standard for high data rate science missions at L2. With the new frequency range, the issues of alternatives antenna deployment, off nominal scenarios, NASA implementation of the Ka-band 26 GHz, and navigation requirements will be discussed in this paper. JWST is also using Consultative Committee for Space Data Systems (CCSDS) standard process for reliable file transfer using CCSDS File Delivery Protocol (CFDP). For JWST the use of the CFDP protocol provides level zero processing at the DSN site. This paper will address NASA implementations of Ground Stations in support of Ka-band 26 GHz and lesson learned from implementing a file base (CFDP) protocol operational system.

Johns, Alan

Flexible Revision Of Data-Processing Communications

Distributed Objects Protocol Layer (DOPL) software system implements protocol for communications among software objects programmed in C++ computer language. DOPL is application-program interface (API). Enables communication of data without regard for which specific computer(s) and operating system(s) is (are) in use. No extension of the C++ language necessary for use of DOPL.

Burleigh, Scott C.

Enhanced International Space Station Ku-Band Telemetry Service

The International Space Station (ISS) is in an operational configuration. To fully utilize the ISS and take advantage of the modern protocols and updated Ku-band access, the Huntsville Operations Support Center (HOSC) has designed an approach to extend the Kuband forward link access for payload investigators to their on-orbit payloads. This dramatically increases the ground to ISS communications for those users. This access also enables the ISS flight controllers operating in the Payload Operations and Integration Center to have more direct control over the systems they are responsible for managing and operating. To extend the Ku-band forward link to the payload user community the development of a new command server is necessary. The HOSC subsystems were updated to process the Internet Protocol Encapsulated packets, enable users to use the service based on their approved services, and perform network address translation to insure that the packets are forwarded from the user to the correct payload repeating that process in reverse from ISS to the payload user. This paper presents the architecture, implementation, and lessons learned. This will include the integration of COTS hardware and software as well as how the device is incorporated into the operational mission of the ISS. Thus, this paper also discusses how this technology can be applicable to payload users of the ISS.

Cecil, Andrew J.

Purifying Nucleic Acids from Samples of Extremely Low Biomass

A new method is able to circumvent the bias to which one commercial DNA extraction method falls prey with regard to the lysing of certain types of microbial cells, resulting in a truncated spectrum of microbial diversity. By prefacing the protocol with glass-bead-beating agitation (mechanically lysing a much more encompassing array of cell types and spores), the resulting microbial diversity detection is greatly enhanced. In preliminary studies, a commercially available automated DNA extraction method is effective at delivering total DNA yield, but only the non-hardy members of the bacterial bisque were represented in clone libraries, suggesting that this method was ineffective at lysing the hardier cell types. To circumvent such a bias in cells, yet another extraction method was devised. In this technique, samples are first subjected to a stringent bead-beating step, and then are processed via standard protocols. Prior to being loaded into extraction vials, samples are placed in micro-centrifuge bead tubes containing 50 micro-L of commercially produced lysis solution. After inverting several times, tubes are agitated at maximum speed for two minutes. Following agitation, tubes are centrifuged at 10,000 x g for one minute. At this time, the aqueous volumes are removed from the bead tubes and are loaded into extraction vials to be further processed via extraction regime. The new method couples two independent methodologies in such as way as to yield the highest concentration of PCR-amplifiable DNA with consistent and reproducible results and with the most accurate and encompassing report of species richness.

La Duc, Myron

Software forecasting as it is really done: A study of JPL software engineers

This paper presents a summary of the results to date of a Jet Propulsion Laboratory internally funded research task to study the costing process and parameters used by internally recognized software cost estimating experts. Protocol Analysis and Markov process modeling were used to capture software engineer's forecasting mental models. While there is significant variation between the mental models that were studied, it was nevertheless possible to identify a core set of cost forecasting activities, and it was also found that the mental models cluster around three forecasting techniques. Further partitioning of the mental models revealed clustering of activities, that is very suggestive of a forecasting lifecycle. The different forecasting methods identified were based on the use of multiple-decomposition steps or multiple forecasting steps. The multiple forecasting steps involved either forecasting software size or an additional effort forecast. Virtually no subject used risk reduction steps in combination. The results of the analysis include: the identification of a core set of well defined costing activities, a proposed software forecasting life cycle, and the identification of several basic software forecasting mental models. The paper concludes with a discussion of the implications of the results for current individual and institutional practices.

Griesel, Martha Ann

Eight microprocessor-based instrument data systems in the Galileo Orbiter spacecraft

Instrument data systems consist of a microprocessor, 3K bytes of Read Only Memory and 3K bytes of Random Access Memory. It interfaces with the spacecraft data bus through an isolated user interface with a direct memory access bus adaptor, and/or parallel data from instrument devices such as registers, buffers, analog to digital converters, multiplexers, and solid state sensors. These data systems support the spacecraft hardware and software communication protocol, decode and process instrument commands, generate continuous instrument operating modes, control the instrument mechanisms, acquire, process, format, and output instrument science data.

Barry, R. C.

NSI directed to continue SPAN's functions

During a series of network management retreats in June and July 1990, representatives from NASA Headquarters Codes O and S agreed on networking roles and responsibilities for their respective organizations. The representatives decided that NASA Science Internet (NSI) will assume management of both the Space Physics Analysis Network (SPAN) and the NASA Science Network (NSN). SPAN is now known as the NSI/DECnet, and NSN is now known as the NSI/IP. Some management functions will be distributed between Ames Research Center (ARC) and Goddard Space Flight Center (GSFC). NSI at ARC has the lead role for requirements generation and networking engineering. Advanced Applications and the Network Information Center is being developed at GSFC. GSFC will lead the NSI User Services, but NSI at Ames will continue to provide the User Services during the transition. The transition will be made as transparent as possible for the users. DECnet service will continue, but is now directly managed by NSI at Ames. NSI will continue to work closely with routing center managers at other NASA centers, and has formed a transition team to address the change in management. An NSI/DECnet working group had also been formed as a separate engineering group within NSI to plan the transition to Phase 5, DECnet's approach to Open System Integration (OSI). Transition is not expected for a year or more due to delays in produce releases. Plans to upgrade speeds in tail circuits and the backbone are underway. The proposed baseline service for new connections is up to 56 Kbps; 9.6 Kbps lines will gradually be upgraded as requirements dictate. NSI is in the process of consolidating protocol traffic, tail circuits, and the backbone. Currently NSI's backbone is fractional T1; NSI will go to full T1 service as soon as it is feasible.

Rounds, Fred