Search NASASearch

SEARCH · Search NASA

Results for “Sequence Function Data”

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 37 records · Page 2

The luminosity function at the end of the main sequence: Results of a deep, large-area, CCD survey for cool dwarfs

The luminosity function at the end of the main sequence is determined from V, R, and I data taken by the charge coupled devices (CCD)/Transit Instrument, a dedicated telescope surveying an 8.25 min wide strip of sky centered at delta = +28 deg, thus sampling Galactic latitudes of +90 deg down to -35 deg. A selection of 133 objects chosen via R - I and V - I colors has been observed spectroscopically at the 4.5 m Multiple Mirror Telescope to assess contributions by giants and subdwarfs and to verify that the reddest targets are objects of extremely late spectral class. Eighteen dwarfs of type M6 or later have been discovered, with the latest being of type M8.5. Data used for the determination of the luminosity function cover 27.3 sq. deg down to a completeness limit of R = 19.0. This luminosity function, computed at V, I, and bolometric magnitudes, shows an increase at the lowest luminosities, corresponding to spectral types later than M6- an effect suggested in earlier work by Reid & Gilmore and Legget & Hawkins. When the luminosity function is segregated into north Galactic and south Galactic portions, it is found that the upturn at faint magnitudes exists only in the southern sample. In fact, no dwarfs with M(sub I) is greater than or equal to 12.0 are found within the limiting volume of the 19.4 sq deg northern sample, in stark contrast to the smaller 7.9 sq deg area at southerly latitudes where seven such dwarfs are found. This fact, combined with the fact that the Sun is located approximately 10-40 pc north of the midplane, suggests that the latest dwarfs are part of a young population with a scale height much smaller than the 350 pc value generally adopted for other M dwarfs. These objects comprise a young population either because the lower metallicities prevelant at earlier epochs inhibited the formation of late M dwarfs or because the older counterparts of this population have cooled beyond current detection limits. The latter scenario would hold if these late-type M dwarfs are substellar. The luminosity function data together with an empirical derivation of the mass-luminosity relation (from Henry & McCarthy) are used to compute a mass function independent of theory. This mass function increases toward the end of the main sequence, but the observed density of M dwarfs is still insufficient to account for the missing mass. If the increases seen in the luminosity and mass functions are indicative of a large, unseen, substellar population, brown dwarfs may yet add significantly to the mass of the Galaxy.

Kirkpatrick, J. Davy

Space Suit Portable Life Support System (PLSS) 2.0 Pre-Installation Acceptance (PIA) Testing

Following successful completion of the space suit Portable Life Support System (PLSS) 1.0 development and testing in 2011, the second system-level prototype, PLSS 2.0, was developed in 2012 to continue the maturation of the advanced PLSS design which is intended to reduce consumables, improve reliability and robustness, and incorporate additional sensing and functional capabilities over the current Space Shuttle/International Space Station Extravehicular Mobility Unit (EMU) PLSS. PLSS 2.0 represents the first attempt at a packaged design comprising first generation or later component prototypes and medium fidelity interfaces within a flight-like representative volume. Pre-Installation Acceptance (PIA) is carryover terminology from the Space Shuttle Program referring to the series of test sequences used to verify functionality of the EMU PLSS prior to installation into the Space Shuttle airlock for launch. As applied to the PLSS 2.0 development and testing effort, PIA testing designated the series of 27 independent test sequences devised to verify component and subsystem functionality, perform in situ instrument calibrations, generate mapping data to define set-points for control algorithms, evaluate hardware performance against advanced PLSS design requirements, and provide quantitative and qualitative feedback on evolving design requirements and performance specifications. PLSS 2.0 PIA testing was carried out from 3/20/13 - 3/15/14 using a variety of test configurations to perform test sequences that ranged from stand-alone component testing to system-level testing, with evaluations becoming increasingly integrated as the test series progressed. Each of the 27 test sequences was vetted independently, with verification of basic functionality required before completion. Because PLSS 2.0 design requirements were evolving concurrently with PLSS 2.0 PIA testing, the requirements were used as guidelines to assess performance during the tests; after the completion of PIA testing, test data served to improve the fidelity and maturity of design requirements as well as plans for future advanced PLSS functional testing.

Watts, Carly

Space Suit Portable Life Support System (PLSS) 2.0 Pre-Installation Acceptance (PIA) Testing

Following successful completion of the space suit Portable Life Support System (PLSS) 1.0 development and testing in 2011, the second system-level prototype, PLSS 2.0, was developed in 2012 to continue the maturation of the advanced PLSS design. This advanced PLSS is intended to reduce consumables, improve reliability and robustness, and incorporate additional sensing and functional capabilities over the current Space Shuttle/International Space Station Extravehicular Mobility Unit (EMU) PLSS. PLSS 2.0 represents the first attempt at a packaged design comprising first generation or later component prototypes and medium fidelity interfaces within a flight-like representative volume. Pre-Installation Acceptance (PIA) is carryover terminology from the Space Shuttle Program referring to the series of test sequences used to verify functionality of the EMU PLSS prior to installation into the Space Shuttle airlock for launch. As applied to the PLSS 2.0 development and testing effort, PIA testing designated the series of 27 independent test sequences devised to verify component and subsystem functionality, perform in situ instrument calibrations, generate mapping data, define set-points, evaluate control algorithms, evaluate hardware performance against advanced PLSS design requirements, and provide quantitative and qualitative feedback on evolving design requirements and performance specifications. PLSS 2.0 PIA testing was carried out in 2013 and 2014 using a variety of test configurations to perform test sequences that ranged from stand-alone component testing to system-level testing, with evaluations becoming increasingly integrated as the test series progressed. Each of the 27 test sequences was vetted independently, with verification of basic functionality required before completion. Because PLSS 2.0 design requirements were evolving concurrently with PLSS 2.0 PIA testing, the requirements were used as guidelines to assess performance during the tests; after the completion of PIA testing, test data served to improve the fidelity and maturity of design requirements as well as plans for future advanced PLSS functional testing.

Anchondo, Ian

Maximum likelihood estimation of parameterized 3-D surfaces using a moving camera

A new approach is introduced to estimating object surfaces in three-dimensional space from a sequence of images. A surface of interest here is modeled as a 3-D function known up to the values of a few parameters. The approach will work with any parameterization. However, in work to date researchers have modeled objects as patches of spheres, cylinders, and planes - primitive objects. These primitive surfaces are special cases of 3-D quadric surfaces. Primitive surface estimation is treated as the general problem of maximum likelihood parameter estimation based on two or more functionally related data sets. In the present case, these data sets constitute a sequence of images taken at different locations and orientations. A simple geometric explanation is given for the estimation algorithm. Though various techniques can be used to implement this nonlinear estimation, researches discuss the use of gradient descent. Experiments are run and discussed for the case of a sphere of unknown location. These experiments graphically illustrate the various advantages of using as many images as possible in the estimation and of distributing camera positions from first to last over as large a baseline as possible. Researchers introduce the use of asymptotic Bayesian approximations in order to summarize the useful information in a sequence of images, thereby drastically reducing both the storage and amount of processing required.

Hung, Y.

The Mars mapper science and mission planning tool

The Mars Mapper Program (MOm) is an interactive tool for science and mission design developed for the Mars Observer Mission (MO). MOm is a function of the Planning and Sequencing Element of the MO Ground Data System. The primary users of MOm are members of the science and mission planning teams. Using MOm, the user can display digital maps of Mars in various projections and resolutions ranging from 1 to 256 pixels per degree squared. The user can overlay the maps with ground tracks of the MO spacecraft (S/C) and footprints and swaths of the various instruments on-board the S/C. Orbital and instrument geometric parameters can be computed on demand and displayed on the digital map or plotted in XY-plots. The parameter data can also be saved into files for other uses. MOm is divided into 3 major processes: Generator, Mapper, Plotter. The Generator Process is the main control which spawns all other processes. The processes communicate via sockets. At any one time, only 1 copy of MOm may operate on the system. However, up to 5 copies of each of the major processes may be invoked from the Generator. MOm is developed on the Sun SPARCStation 2GX with menu driven graphical user interface (GUI). The map window and its overlays are mouse-sensitized to permit on-demand calculations of various parameters along an orbit. The program is currently under testing and will be delivered to the MO Mission System Configuration Management for distribution to the MO community in 3/93.

Lo, Martin W.

Selecting a general-purpose data compression algorithm

The National Space Science Data Center's Common Data Formate (CDF) is capable of storing many types of data such as scalar data items, vectors, and multidimensional arrays of bytes, integers, or floating point values. However, regardless of the dimensionality and data type, the data break down into a sequence of bytes that can be fed into a data compression function to reduce the amount of data without losing data integrity and thus remaining fully reconstructible. Because of the diversity of data types and high performance speed requirements, a general-purpose, fast, simple data compression algorithm is required to incorporate data compression into CDF. The questions to ask are how to evaluate and compare compression algorithms, and what compression algorithm meets all requirements. The object of this paper is to address these questions and determine the most appropriate compression algorithm to use within the CDF data management package that would be applicable to other software packages with similar data compression needs.

Mathews, Gary Jason

Reconstructing Ancient Forms of Life

Progress in the past three months has occurred in two areas, reconstruction of ancestral proteins and improved understanding of chemical features that are likely to be universal in generic matter regardless of its genesis. Ancestral ribonucleases have been reconstructed, and an example has been developed that shows how physiological function can be assigned to in vitro behaviors observed in biological systems. Sequence data have been collected to permit the reconstruction of src homology 2 domains that underwent radiative divergence at the time of the radiative divergence of chordates. New studies have been completed that show how genetic matter (or its remnants) might be detected on Mars (or other non-terrean locations.) Last, the first in vitro selection experiments have been completed using a nucleoside library carrying positively charged functionality, illustrating the importance of non-standard nucleotides to those attempting to obtain evidence for an "RNA world" as an early episode of life on earth.

Benner, Steven A.

Simplifying operations with an uplink/downlink integration toolkit

The Operations Engineering Lab (OEL) at JPL has developed a simple, generic toolkit to integrate the uplink/downlink processes, (often called closing the loop), in JPL's Multimission Ground Data System. This toolkit provides capabilities for integrating telemetry verification points with predicted spacecraft commands and ground events in the Mission Sequence Of Events (SOE) document. In the JPL ground data system, the uplink processing functions and the downlink processing functions are separate subsystems that are not well integrated because of the nature of planetary missions with large one-way light times for spacecraft-to-ground communication. Our new closed-loop monitoring tool allows an analyst or mission controller to view and save uplink commands and ground events with their corresponding downlinked telemetry values regardless of the delay in downlink telemetry and without requiring real-time intervention by the user. An SOE document is a time-ordered list of all the planned ground and spacecraft events, including all commands, sequence loads, ground events, significant mission activities, spacecraft status, and resource allocations. The SOE document is generated by expansion and integration of spacecraft sequence files, ground station allocations, navigation files, and other ground event files. This SOE generation process has been automated within the OEL and includes a graphical, object-oriented SOE editor and real-time viewing tool running under X/Motif. The SOE toolkit was used as the framework for the integrated implementation. The SOE is used by flight engineers to coordinate their operations tasks, serving as a predict data set in ground operations and mission control. The closed-loop SOE toolkit allows simple, automated integration of predicted uplink events with correlated telemetry points in a single SOE document for on-screen viewing and archiving. It automatically interfaces with existing real-time or non real-time sources of information, to display actual values from the telemetry data stream. This toolkit was designed to greatly simplify the user's ability to access and view telemetry data, and also provide a means to view this data in the context of the commands and ground events that are used to interpret it. A closed-loop system can prove especially useful in small missions with limited resources requiring automated monitoring tools. This paper will discuss the toolkit implementation, including design trade-offs and future plans for enhancing the automated capabilities.

Murphy, Susan C.

A dynamic integrated test for the Space Shuttle

The dynamic integrated test (DIT) has been designed to perform a final checkout of the assembled Space Shuttle vehicle at Kennedy Space Center. The fact that the vehicle is not in a laboratory environment for the test represents a significant constraint in that the use of test equipment is extremely limited, and environment models cannot be used. In essence, the DIT causes the vehicle to believe that it is flying, so that hardware and software systems are exercised much as they would be for a real flight. This technique provides a tool for verifying such items as data bus activity patterns, critical timing sequences, software and hardware moding as a function of flight parameters, absence of EMI problems and other systems interactions which cannot be tested fully in the laboratory.

Brody, S.

Halogen occultation experiment (HALOE) performance verification test procedure

The Performance Verification Test Procedure is given for the Halogen Occultation Experiment (HALOE) instrument, which is being developed in house at the Langley Research Center for the Upper Atmosphere Research Satellite (UARS). This procedure is used for comprehensive performance testing of the HALOE instrument which occurs before, during, and after flight environmental tests. The radiometric performance tests include noise, drift, linearity, instantaneous field-of-view, cal wheel gas cell characterization, and self thermal emissions. Pointer/tracker performance tests include sun sensor performance, gimbal performance, control system performance, and boresight alignment. In addition, the instrument is tested functionally in simulated orbit sequences and all command operating modes are exercised. The data analysis required for each test is specified and pass/fail criteria are given where applicable. This test will fully demonstrate the HALOE instrument's ability to achieve science mission requirements. The HALOE instrument is a gas correlation radiometer that measures vertical distribution of eight upper atmospheric constituents: O3, HCl, HF, NO, CH4, H2O, NO2, and CO2.

Mauldin, L. E., III

Biological Information Signal Processor

Biological Information Signal Processor (BISP) is computing system analyzing data on deoxyribonucleic acid (DNA) sequences for molecular genetic analysis. Includes coprocessors, specialized microprocessors complementing present and future computers by performing rapidly most-time-consuming DNA-sequence-analyzing functions, establishing relationships (alignments) between both global sequences and defining patterns in multiple sequences. Also includes state-of-art software and data-base systems on both conventional and parallel computer systems to augment analytical abilities of developmental coprocessors.

Chow, Edward T.

Distributed integrated instrumentation and control system

The operation and capabilities of a new integrated instrumentation and control system are described. The system will, under one main program, both acquire data from a conducted test and automatically control the test sequence. The system layout has a multiplexer front end and control-function electronics at the test area, while the system control computer, recording devices, and monitors are located remotely. The system's data, control, and communication signals are transmitted via fiber-optic lines. Diagrams are presented illustrating the control and data displays.

Hagood, Don

Autonomous Real Time Requirements Tracing

One of the more challenging aspects of software development is the ability to verify and validate the functional software requirements dictated by the Software Requirements Specification (SRS) and the Software Detail Design (SDD). Insuring the software has achieved the intended requirements is the responsibility of the Software Quality team and the Software Test team. The utilization of Timeliner-TLX(sup TM) Auto- Procedures for relocating ground operations positions to ISS automated on-board operations has begun the transition that would be required for manned deep space missions with minimal crew requirements. This transition also moves the auto-procedures from the procedure realm into the flight software arena and as such the operational requirements and testing will be more structured and rigorous. The autoprocedures would be required to meet NASA software standards as specified in the Software Safety Standard (NASASTD- 8719), the Software Engineering Requirements (NPR 7150), the Software Assurance Standard (NASA-STD-8739) and also the Human Rating Requirements (NPR-8705). The Autonomous Fluid Transfer System (AFTS) test-bed utilizes the Timeliner-TLX(sup TM) Language for development of autonomous command and control software. The Timeliner-TLX(sup TM) system has the unique feature of providing the current line of the statement in execution during real-time execution of the software. The feature of execution line number internal reporting unlocks the capability of monitoring the execution autonomously by use of a companion Timeliner-TLX(sup TM) sequence as the line number reporting is embedded inside the Timeliner-TLX(sup TM) execution engine. This negates I/O processing of this type data as the line number status of executing sequences is built-in as a function reference. This paper will outline the design and capabilities of the AFTS Autonomous Requirements Tracker, which traces and logs SRS requirements as they are being met during real-time execution of the targeted system. It is envisioned that real time requirements tracing will greatly assist the movement of autoprocedures to flight software enhancing the software assurance of auto-procedures and also their acceptance as reliable commanders.

Plattsmier, George

Autonomous Real Time Requirements Tracing

One of the more challenging aspects of software development is the ability to verify and validate the functional software requirements dictated by the Software Requirements Specification (SRS) and the Software Detail Design (SDD). Insuring the software has achieved the intended requirements is the responsibility of the Software Quality team and the Software Test team. The utilization of Timeliner-TLX(sup TM) Auto-Procedures for relocating ground operations positions to ISS automated on-board operations has begun the transition that would be required for manned deep space missions with minimal crew requirements. This transition also moves the auto-procedures from the procedure realm into the flight software arena and as such the operational requirements and testing will be more structured and rigorous. The autoprocedures would be required to meet NASA software standards as specified in the Software Safety Standard (NASASTD- 8719), the Software Engineering Requirements (NPR 7150), the Software Assurance Standard (NASA-STD-8739) and also the Human Rating Requirements (NPR-8705). The Autonomous Fluid Transfer System (AFTS) test-bed utilizes the Timeliner-TLX(sup TM) Language for development of autonomous command and control software. The Timeliner- TLX(sup TM) system has the unique feature of providing the current line of the statement in execution during real-time execution of the software. The feature of execution line number internal reporting unlocks the capability of monitoring the execution autonomously by use of a companion Timeliner-TLX(sup TM) sequence as the line number reporting is embedded inside the Timeliner-TLX(sup TM) execution engine. This negates I/O processing of this type data as the line number status of executing sequences is built-in as a function reference. This paper will outline the design and capabilities of the AFTS Autonomous Requirements Tracker, which traces and logs SRS requirements as they are being met during real-time execution of the targeted system. It is envisioned that real time requirements tracing will greatly assist the movement of autoprocedures to flight software enhancing the software assurance of auto-procedures and also their acceptance as reliable commanders

Plattsmier, George I.

An object-oriented data reduction system in Fortran

A data reduction system for the AAO two-degree field project is being developed using an object-oriented approach. Rather than use an object-oriented language (such as C++) the system is written in Fortran and makes extensive use of existing subroutine libraries provided by the UK Starlink project. Objects are created using the extensible N-dimensional Data Format (NDF) which itself is based on the Hierarchical Data System (HDS). The software consists of a class library, with each class corresponding to a Fortran subroutine with a standard calling sequence. The methods of the classes provide operations on NDF objects at a similar level of functionality to the applications of conventional data reduction systems. However, because they are provided as callable subroutines, they can be used as building blocks for more specialist applications. The class library is not dependent on a particular software environment thought it can be used effectively in ADAM applications. It can also be used from standalone Fortran programs. It is intended to develop a graphical user interface for use with the class library to form the 2dF data reduction system.

Bailey, J.

ISSYS: An integrated synergistic Synthesis System

Integrated Synergistic Synthesis System (ISSYS), an integrated system of computer codes in which the sequence of program execution and data flow is controlled by the user, is discussed. The commands available to exert such control, the ISSYS major function and rules, and the computer codes currently available in the system are described. Computational sequences frequently used in the aircraft structural analysis and synthesis are defined. External computer codes utilized by the ISSYS system are documented. A bibliography on the programs is included.

Dovi, A. R.

Microelectronics Instrument Products Shock and Vibration Electro-Optics: Acceptance Data Package - Section B

The motor/encoder (henceforth referred to as the UUT) test sequence began with a baseline functional evaluation, which demonstrated that the motor satisfied the operating torque, cogging torque, winding resistance, and mechanical requirements of SOW. In addition, the encoder electrical requirements were verified, as well as the alignment of the encoder outputs relative to the motor shaft position. There were no discrepancies observed in this portion of the test. The UUT was then exposed to a number of environments, including thermal vacuum, thermal cycling, random and sine vibration, and mechanical shock. During the thermal environments, the performance of the UUT under load was verified at specified points in the cycles, as described in ATP 20049. In addition, the UUT was bench tested between the two thermal environments. No anomalies were observed during the thermal tests. The vibration and shock tests were performed by East-West Technology Corporation, West Babylon, New York. The UUT was delivered to the lab in a sealed vibration fixture in order to maintain the cleanliness levels required by the SOW. In addition, a three ounce load was attached to the motor shaft. The attachment method of this load caused damage to the shaft and bearing during random vibration of S/N 0003 on April 28, 1995, and is described further in NCR 00168.

Source record