Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “Interface modification”

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.

435 records · Page 25
All sourcesNASA NTRSDOE OSTI
NASA NTRS2014

CEO Sites Mission Management System (SMMS)

Late in fiscal year 2011, the Crew Earth Observations (CEO) team was tasked to upgrade its science site database management tool, which at the time was integrated with the Automated Mission Planning System (AMPS) originally developed for Earth Observations mission planning in the 1980s. Although AMPS had been adapted and was reliably used by CEO for International Space Station (ISS) payload operations support, the database structure was dated, and the compiler required for modifications would not be supported in the Windows 7 64-bit operating system scheduled for implementation the following year. The Sites Mission Management System (SMMS) is now the tool used by CEO to manage a heritage Structured Query Language (SQL) database of more than 2,000 records for Earth science sites. SMMS is a carefully designed and crafted in-house software package with complete and detailed help files available for the user and meticulous internal documentation for future modifications. It was delivered in February 2012 for test and evaluation. Following acceptance, it was implemented for CEO mission operations support in April 2012. The database spans the period from the earliest systematic requests for astronaut photography during the shuttle era to current ISS mission support of the CEO science payload. Besides logging basic image information (site names, locations, broad application categories, and mission requests), the upgraded database management tool now tracks dates of creation, modification, and activation; imagery acquired in response to requests; the status and location of ancillary site information; and affiliations with studies, their sponsors, and collaborators. SMMS was designed to facilitate overall mission planning in terms of site selection and activation and provide the necessary site parameters for the Satellite Tool Kit (STK) Integrated Message Production List Editor (SIMPLE), which is used by CEO operations to perform daily ISS mission planning. The CEO team uses the SMMS for three general functions - database queries of content and status, individual site creation and updates, and mission planning. The CEO administrator of the science site database is able to create or modify the content of sites and activate or deactivate them based on the requirements of the sponsors. The administrator supports and implements ISS mission planning by assembling, reporting, and activating mission-specific site selections for management; deactivating sites as requirements are met; and creating new sites, such as International Charter sites for disasters, as circumstances warrant. In addition to the above CEO internal uses, when site planning for a specific ISS mission is complete and approved, the SMMS can produce and export those essential site database elements for the mission into XML format for use by onboard Earth-location systems, such as Worldmap. The design, development, and implementation of the SMMS resulted in a superior database management system for CEO science sites by focusing on the functions and applications of the database alone instead of integrating the database with the multipurpose configuration of the AMPS. Unlike the AMPS, it can function and be modified within the existing Windows 7 environment. The functions and applications of the SMMS were expanded to accommodate more database elements, report products, and a streamlined interface for data entry and review. A particularly elegant enhancement in data entry was the integration of the Google Earth application for the visual display and definition of site coordinates for site areas defined by multiple coordinates. Transfer between the SMMS and Google Earth is accomplished with a Keyhole Markup Language (KML) expression of geographic data (see figures 3 and 4). Site coordinates may be entered into the SMMS panel directly for display in Google Earth, or the coordinates may be defined on the Google Earth display as a mouse-controlled polygonal definition and transferred back into the SMMS as KML input. This significantly reduces the possibility of errors in coordinate entries and provides visualization of the scale of the site being defined. CEO now has a powerful tool for managing and defining sites on the Earth's surface for both targets of astronaut photography or other onboard remote sensing systems. It can also record and track results by sponsor, collaborator, or type of study.

Trenchard, Mike↗
NASA NTRS2013

Application Program Interface for the Orion Aerodynamics Database

The Application Programming Interface (API) for the Crew Exploration Vehicle (CEV) Aerodynamic Database has been developed to provide the developers of software an easily implemented, fully self-contained method of accessing the CEV Aerodynamic Database for use in their analysis and simulation tools. The API is programmed in C and provides a series of functions to interact with the database, such as initialization, selecting various options, and calculating the aerodynamic data. No special functions (file read/write, table lookup) are required on the host system other than those included with a standard ANSI C installation. It reads one or more files of aero data tables. Previous releases of aerodynamic databases for space vehicles have only included data tables and a document of the algorithm and equations to combine them for the total aerodynamic forces and moments. This process required each software tool to have a unique implementation of the database code. Errors or omissions in the documentation, or errors in the implementation, led to a lengthy and burdensome process of having to debug each instance of the code. Additionally, input file formats differ for each space vehicle simulation tool, requiring the aero database tables to be reformatted to meet the tool s input file structure requirements. Finally, the capabilities for built-in table lookup routines vary for each simulation tool. Implementation of a new database may require an update to and verification of the table lookup routines. This may be required if the number of dimensions of a data table exceeds the capability of the simulation tools built-in lookup routines. A single software solution was created to provide an aerodynamics software model that could be integrated into other simulation and analysis tools. The highly complex Orion aerodynamics model can then be quickly included in a wide variety of tools. The API code is written in ANSI C for ease of portability to a wide variety of systems. The input data files are in standard formatted ASCII, also for improved portability. The API contains its own implementation of multidimensional table reading and lookup routines. The same aerodynamics input file can be used without modification on all implementations. The turnaround time from aerodynamics model release to a working implementation is significantly reduced

Robinson, Philip E.↗
NASA NTRS2002

Tip-Clearance Vortex Characterized With Three-Dimensional Digital Particle Image Velocimetry

An optical measurement technique known as Three-Dimensional Digital Particle Image Velocimetry (3-D DPIV) was used to characterize the tip clearance flow in NASA Glenn Research Center's low-speed axial compressor. 3-D DPIV is a technique in which a stereoscopic imaging system consisting of two cross-correlation cameras is used to record particles entrained in a flow as a laser light sheet is pulsed at two instances in time. Although 3-D DPIV has been used elsewhere, this is the first time it has been used to measure compressor tip clearance flows. In-house modifications of the DPIV system include the use of effective seeding technology and a novel system to perform a priori calibrations at all five measurement planes, greatly reducing facility run time. Computational fluid dynamics predictions, which are used to guide design changes toward improving the efficiency and operating range of turbomachinery, can be verified and improved by comparison with 3-D DPIV measurements of the actual tip clearance flow. This measurement campaign dealt with the characterization of the tip clearance vortex in the first stage of a four-stage axial compressor. The tip clearance vortex is formed in compressors operating with a clearance gap between the moving rotor blade tips and the stationary casing when a leakage flow, forced from the pressure side of the blade over the blade tip, forms a vortical structure on the suction side of the blade. 3-D DPIV is ideally suited to measure the clearance vortex for two reasons: (1) this technique captures the entire blade passage flow at one instant in time, so that wandering of the vortex during the measurement does not smear out velocity gradients in the flow field, and (2) the spanwise component of velocity changes sign across the vortex core, providing a more accurate measurement of the vortex location than was available with previous two-dimensional measurement approaches. These two attributes of the data will enable computational fluid dynamics researchers to validate their predictions to a level of accuracy not previously attainable. In an effort to understand the effects of this flow phenomenon on the operation of the low speed axial compressor, data were acquired at two mass flow coefficients: 0.395 (design operating point) and 0.35 (operating point just above stall). In order to identify the spatial extent, location, and magnitude of the tip clearance vortex for each mass flow condition, data were acquired at five equally spaced spanwise locations, from 90- to 100-percent span. The data presented shows a cross section of the tip clearance vortex at 94-percent span and a mass flow coefficient of 0.395, where the color contours represent the radial velocity component. The blue (flow towards the hub) and red (flow towards the casing) regions illustrate the extent of the tip clearance vortex. The interface between the blue and red regions delineates the location of the vortex core.

John, W. Trevor↗