SEARCH · Engineering Papers

Results for “File System”

Search indexed NASA NTRS and DOE OSTI research on propulsion, heat transfer, battery materials and energy systems. Follow report and document links to the original sources.

SourceResearch connectionFrom yearThrough year

Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.

At least 1,801 records · Page 100

All sources NASA NTRS DOE OSTI

NASA NTRS2021

Extending the Licklider Transmission Protocol to Multi-Band Links

Most deep space missions return data to Earth using links operating at a single frequency band. Indeed, their data requirements are low enough that bandwidth regulations do not constrain the system. In contrast, spacecraft such as Kepler or Europa Clipper are transitioning to a new operational paradigm where engineering and science data are transmitted through simultaneous links operating at different frequency bands (henceforth termed multi-band links). This ensures, for instance, that critical data is correctly received using a well characterized X-band link, while science data at a much larger data rate can be returned efficiently (both in terms of bandwidth and energy) through a Ka-band link.Having a spacecraft establish two simultaneous links with a ground station opens a large span of potential improvements for space communications and mission operations. In this paper, we consider the problem of running a Licklider Transmission Protocol (LTP) session over a multi-band link. LTP is an implementation of a selective Automatic Repeat reQuest (ARQ) protocol, i.e. it ensures correct delivery of data over an error prone link with potentially long propagation delays. To maximize its efficiency in deep space environments, LTP operates in deferred-ACK mode and is typically included as one of the core protocols in the Delay Tolerant Networking (DTN) suite.The contributions of this paper are as follows: First, we propose an extension to LTP for multi-band links (denoted MBLTP) and sketch how it can be implemented without modifying the current definition of LTP data units. Next, we develop bounds on the performance of MBLTP when transmitting a single data file over a multi-band link. Three metrics are considered, file expected delivery time, total energy spent and bundle jitter. The results of the analytic model are first benchmarked against simulations to ensure validity, and then compared against the performance of both traditional LTP and Parallel LTP (PLTP).We demonstrate that MBLTP can significantly reduce the latency and jitter with which data products are delivered to destination over a deep space link compared to LTP at moderate energy cost. Similarly, we also demonstrate that MBLTP outperforms PLTP in all considered metrics.

Sanchez Net, Marc↗

NASA NTRS2010

GSFC DORIS Contribution to ITRF2008

The NASA GSFC DORIS analysis center has provided weekly DORIS solutions from November 1992 to January 2009 (839 SINEX files) of station positions and Earth Orientation Parameters for inclusion in the DORIS contribution to ITRF2008. The NASA GSFC GEODYN orbit determination software was used to process the orbits and produce the normal equations. The weekly SINEX gscwd 10 submissions included DORIS data from Envisat, TOPEX!Poseidon, SPOT-2, SPOT-3, SPOT-4, SPOT-5. The orbits were mostly seven days in length (except for weeks with data gaps or maneuvers). The processing used the GRACE-derived EIGEN-GL04S1 gravity model, updated modeling for time-variable gravity, the GOT4.7 ocean tide model and tuned satellite-specific macromodels for SPOT -2, SPOT -3, SPOT -4, SPOT-5 and TOPEX/Poseidon. The University College London (UCL) radiation pressure model for Envisat improves nonconservative force modeling for this satellite, reducing the median residual empirical daily along-track accelerations from 3.75 x 10-9 m/s(exp 2) with the a priori macromodel to 0.99 x 10-9 m/s2 with the UCL model. For the SPOT and Envisat DORIS satellite orbits from 2003 to 2008, we obtain average RMS overlaps of 0.8-0.9 cm in the radial direction, 2.1-3.4 cm cross-track, and 1.7-2.3 cm along-track. The RMS orbit differences between Envisat DORIS-only and SLR & DORIS orbits are 1.1 cm radially, 6.4 cm along-track and 3.7 cm cross-track and are characterized by systematic along-track mean offsets due to the Envisat DORIS system time bias of +/- 5-1O micro s. We obtain a good agreement between the geometrically-determined geocenter parameters and geocenter parameters determined dynamically from analysis of the degree one terms of the geopotential. The intrinsic RMS weekly position repeatability with respect to the IDS-3 combination ranges from 2.5 to 3.0 cm in 1993-1994 to 1.5 cm in 2007-2008.

Le Bail, K.↗

NASA NTRS2013

A Validated Set of MIDAS V5 Task Network Model Scenarios to Evaluate Nextgen Closely Spaced Parallel Operations Concepts

The Closely Spaced Parallel Operations (CSPO) scenario is a complex, human performance model scenario that tested alternate operator roles and responsibilities to a series of off-nominal operations on approach and landing (see Gore, Hooey, Mahlstedt, Foyle, 2013). The model links together the procedures, equipment, crewstation, and external environment to produce predictions of operator performance in response to Next Generation system designs, like those expected in the National Airspaces NextGen concepts. The task analysis that is contained in the present report comes from the task analysis window in the MIDAS software. These tasks link definitions and states for equipment components, environmental features as well as operational contexts. The current task analysis culminated in 3300 tasks that included over 1000 Subject Matter Expert (SME)-vetted, re-usable procedural sets for three critical phases of flight; the Descent, Approach, and Land procedural sets (see Gore et al., 2011 for a description of the development of the tasks included in the model; Gore, Hooey, Mahlstedt, Foyle, 2013 for a description of the model, and its results; Hooey, Gore, Mahlstedt, Foyle, 2013 for a description of the guidelines that were generated from the models results; Gore, Hooey, Foyle, 2012 for a description of the models implementation and its settings). The rollout, after landing checks, taxi to gate and arrive at gate illustrated in Figure 1 were not used in the approach and divert scenarios exercised. The other networks in Figure 1 set up appropriate context settings for the flight deck.The current report presents the models task decomposition from the tophighest level and decomposes it to finer-grained levels. The first task that is completed by the model is to set all of the initial settings for the scenario runs included in the model (network 75 in Figure 1). This initialization process also resets the CAD graphic files contained with MIDAS, as well as the embedded operator models that comprise MIDAS. Following the initial settings, the model progresses to begin the first tasks required of the two flight deck operators, the Captain (CA) and the First Officer (FO). The task sets will initialize operator specific settings prior to loading all of the alerts, probes, and other events that occur in the scenario. As a note, the CA and FO were terms used in developing this model but the CA can also be thought of as the Pilot Flying (PF), while the FO can be considered the Pilot-Not-Flying (PNF)or Pilot Monitoring (PM). As such, the document refers to the operators as PFCA and PNFFO respectively.

task network model↗

NASA NTRS2015

Telescience Resource Kit (TReK)

Telescience Resource Kit (TReK) is one of the Huntsville Operations Support Center (HOSC) remote operations solutions. It can be used to monitor and control International Space Station (ISS) payloads from anywhere in the world. It is comprised of a suite of software applications and libraries that provide generic data system capabilities and access to HOSC services. The TReK Software has been operational since 2000. A new cross-platform version of TReK is under development. The new software is being released in phases during the 2014-2016 timeframe. The TReK Release 3.x series of software is the original TReK software that has been operational since 2000. This software runs on Windows. It contains capabilities to support traditional telemetry and commanding using CCSDS (Consultative Committee for Space Data Systems) packets. The TReK Release 4.x series of software is the new cross platform software. It runs on Windows and Linux. The new TReK software will support communication using standard IP protocols and traditional telemetry and commanding. All the software listed above is compatible and can be installed and run together on Windows. The new TReK software contains a suite of software that can be used by payload developers on the ground and onboard (TReK Toolkit). TReK Toolkit is a suite of lightweight libraries and utility applications for use onboard and on the ground. TReK Desktop is the full suite of TReK software -most useful on the ground. When TReK Desktop is released, the TReK installation program will provide the option to choose just the TReK Toolkit portion of the software or the full TReK Desktop suite. The ISS program is providing the TReK Toolkit software as a generic flight software capability offered as a standard service to payloads. TReK Software Verification was conducted during the April/May 2015 timeframe. Payload teams using the TReK software onboard can reference the TReK software verification. TReK will be demonstrated on-orbit running on an ISS provided T61p laptop. Target Timeframe: September 2015 -2016. The on-orbit demonstration will collect benchmark metrics, and will be used in the future to provide live demonstrations during ISS Payload Conferences. Benchmark metrics and demonstrations will address the protocols described in SSP 52050-0047 Ku Forward section 3.3.7. (Associated term: CCSDS File Delivery Protocol (CFDP)).

Lippincott, Jeff↗

NASA NTRS2015

Global Precipitation Measurement (GPM) Mission: Precipitation Processing System (PPS) GPM Mission Gridded Text Products Provide Surface Precipitation Retrievals

In February 2015, the Global Precipitation Measurement (GPM) mission core satellite will complete its first year in space. The core satellite carries a conically scanning microwave imager called the GPM Microwave Imager (GMI), which also has 166 GHz and 183 GHz frequency channels. The GPM core satellite also carries a dual frequency radar (DPR) which operates at Ku frequency, similar to the Tropical Rainfall Measuring Mission (TRMM) Precipitation Radar, and a new Ka frequency. The precipitation processing system (PPS) is producing swath-based instantaneous precipitation retrievals from GMI, both radars including a dual-frequency product, and a combined GMIDPR precipitation retrieval. These level 2 products are written in the HDF5 format and have many additional parameters beyond surface precipitation that are organized into appropriate groups. While these retrieval algorithms were developed prior to launch and are not optimal, these algorithms are producing very creditable retrievals. It is appropriate for a wide group of users to have access to the GPM retrievals. However, for researchers requiring only surface precipitation, these L2 swath products can appear to be very intimidating and they certainly do contain many more variables than the average researcher needs. Some researchers desire only surface retrievals stored in a simple easily accessible format. In response, PPS has begun to produce gridded text based products that contain just the most widely used variables for each instrument (surface rainfall rate, fraction liquid, fraction convective) in a single line for each grid box that contains one or more observations.This paper will describe the gridded data products that are being produced and provide an overview of their content. Currently two types of gridded products are being produced: (1) surface precipitation retrievals from the core satellite instruments GMI, DPR, and combined GMIDPR (2) surface precipitation retrievals for the partner constellation satellites. Both of these gridded products are generated for a.25 degree x.25 degree hourly grid, which are packaged into daily ASCII (American Standard Code for Information Interchange) files that can downloaded from the PPS FTP (File Transfer Protocol) site. To reduce the download size, the files are compressed using the gzip utility.This paper will focus on presenting high-level details about the gridded text product being generated from the instruments on the GPM core satellite. But summary information will also be presented about the partner radiometer gridded product. All retrievals for the partner radiometer are done using the GPROF2014 algorithmusing as input the PPS generated inter-calibrated 1C product for the radiometer.

precipitation↗

NASA NTRS1995

Quick Look Report of Acceleration Measurements on Mir Space Station During Mir-16

The NASA Microgravity Science and Applications Division (MSAD) sponsors the Space Acceleration Measurement System (SAMS) to support microgravity science experiments with microgravity acceleration measurements. In the past, SAMS was flown exclusively on the NASA Orbiters. MSAD is currently sponsoring science experiments participating in the Shuttle-Mir Science Program in cooperation with the Russians on the Mir space station. Included in the complement of MSAD experiments and equipment is a SAMS unit installed on the Mir space station. On 25 August 1994, the SAMS unit was launched on a Russia Progress vehicle to the Mir space station. The SAMS unit will support science experiments from the U.S. and Russia in a manner similar to the Orbiter missions by measuring the microgravity environments during the experiment operations. In October 1994, the SAMS unit recorded data on Mir for over fifty-three hours in seven different time periods to survey possible locations for future experiments. This report presents a quick look at the data and the microgravity environment during the time periods in which SAMS data were acquired. The Mir acceleration data were examined to ascertain gross attributes of the data. This report does not present an exhaustive examination of all possible activities due to the short time available to prepare this quick look report and due to the absence of complete timeline information during the SAMS recording time periods. Appendices A, B and C provide plots of the SAMS data for an overview of the microgravity environment at the times that data were recorded. Appendix D describes the procedures to access SAMS data by file transfer protocol (ftp) utilizing the internet. Appendix E contains a user comment sheet.

Delombard, Richard↗

NASA NTRS1997

Intelligent System Development Using a Rough Sets Methodology

The purpose of this research was to examine the potential of the rough sets technique for developing intelligent models of complex systems from limited information. Rough sets a simple but promising technology to extract easily understood rules from data. The rough set methodology has been shown to perform well when used with a large set of exemplars, but its performance with sparse data sets is less certain. The difficulty is that rules will be developed based on just a few examples, each of which might have a large amount of noise associated with them. The question then becomes, what is the probability of a useful rule being developed from such limited information? One nice feature of rough sets is that in unusual situations, the technique can give an answer of 'I don't know'. That is, if a case arises that is different from the cases the rough set rules were developed on, the methodology can recognize this and alert human operators of it. It can also be trained to do this when the desired action is unknown because conflicting examples apply to the same set of inputs. This summer's project was to look at combining rough set theory with statistical theory to develop confidence limits in rules developed by rough sets. Often it is important not to make a certain type of mistake (e.g., false positives or false negatives), so the rules must be biased toward preventing a catastrophic error, rather than giving the most likely course of action. A method to determine the best course of action in the light of such constraints was examined. The resulting technique was tested with files containing electrical power line 'signatures' from the space shuttle and with decompression sickness data.

Anderson, Gray T.↗

NASA NTRS2018

Using the cFS Command and Data Dictionary (CCDD) to Automate Software Development on Habulous

Final paper is attached. The NASA developed Core Flight System (cFS) is a reusable software architecture that has been used on multiple spaceflight missions. By using this framework, missions are able to reuse code from other missions, as well as leverage deployment onto similar computer architectures (i.e. not "reinvent the wheel" on each new mission). The success in the cFS concept can be seen in the large number of projects using cFS at FSW-2018. The Habulous project is an Earth-based testbed, used for hardware and software that may one day be used on a future space habitat unit, with many participating groups from various NASA centers and aerospace organizations around the country. The distributed nature of the various teams mean that defining (and following) an interface definition is critical on the project. Additionally, since various groups use various types of computer hardware (32/64-bit, big/little endian, Linux/VxWorks/Windows) many additional complications exist in interfacing all the various components into a final integrated system. cFS is used on the majority the flight software (FSW) in running in Habulous. But some subsystems have elected to not use cFS, and use a software bridge (called SBN_lib) to interact with the other cFS nodes in Habulous. In order to most efficiently develop the FSW, a central database is used to define and store each message sent by cFS. A Command and Data Dictionary (CDD) is something nearly universal on spacecraft, but as a team we worked to develop the CDD before the SW development was complete, and not treat it like "as built" documentation. To manage the CDD, the cFS Command and Data Dictionary (CCDD) tool was chosen (available from NASA as open source software). The CCDD tool has successfully been used to automate/autocode a large amount of software used on Habulous, as we are hoping to use it to define even more items in the future (time-triggered Ethernet (TTE) network maps, CPU scheduling). Additionally, Habulous has been exploring the use of cFS on wildly heterogeneous CPUs, and how to coordinate all those various machines using/extending the software bus â€“ network (SBN) application in cFS, as well as TTE to coordinate message passing between various synchronized machines. The major topics to be covered in the presentation are: (1) Updating to the CCSDS_v2 extended headers (and using CPU# as subsystem ID). (2) Managing all the message identification numbers for each cFS message sent/received on any of the various CPUs. (3) Using the CCDD information to automatically generate the C-header files that define the structure for all software bus (SB) commands/telemetry messages. (4) Using the CCDD to automatically generate XML Telemetry and Command Exchange (XTCE) files, which streams display production/integration/testing in a web based display architecture (5) Extending/customizing SBN to pass messages among computers on multiple networks. (6) Using "Protobetter" inside SBN to manage different endian-ness/architectures. (7) Using SBN_lib to allow non-cFS node to communicate with cFS nodes. (8) Developing TTE network and schedule tables for all the various CPUs to use.

Hirsh, Robert L.↗

NASA NTRSDate not supplied

Advances to a Global Agroclimatology Solar Insolation and Meteorological Parameter Data Base: Improved Solar Irradiance up to Hourly Temporal Resolution

A primary objective of NASA’s Prediction of Worldwide Energy Resource (POWER) project is to facilitate the use of NASA Earth Science data holdings within the energy, agricultural, and architectural industries. To this end daily averaged solar data from several NASA projects and metrological data from a NASA assimilation model have long been reformatted and via a user friendly web based data portal (https://power.larc.nasa.gov) at the native resolution of each data products. Potential users can access solar and metrological data in a column formatted DSSAT ASCII format by entering single site specific coordinates or from an area by entering the appropriate area coordinates. Upgrades to the POWER data portal have been implemented that result in a complete upgrade of the base solar insolation data products. From the years 1984 through 2000, a new version of the NASA/GEWEX Surface Radiation Budget (SRB) and Clouds is utilized that reduces the RMS relative to surface measurements. Additionally, Clouds and the Earth’s Radiant Energy System (CERES) SYNoptic 1x1 Degree (SYN1Deg) data products are utilized starting from January 1, 2001 through 3 months of real-time. The CERES Fast Longwave and SHortwave radiative Fluxes (FLASHFlux) is still used to provided daily data spanning from the end of SYN1Deg to within 7 days of real-time. Meteorological parameters now are taken from the NASA Modern Era Retrospective-analysis for Research and Applications (MERRA-2) data set which provides higher resolution data products (hourly and 0.5 x 625 degree) covering the entire globe. Besides updating the solar and meteorological data products, this new version features new data products such as photosynthetically active radiation (PAR), more cloud information, estimates of soil temperatures and improved options for long-term climatological data requests. More than 36+ years daily time slices are included in the combined solar and meteorological data sets. However, perhaps the most important innovation of the POWER GIS-enabled Web Services is the provision of hourly solar and meteorological data products beginning in Jan 1, 2001. The hourly values will enable more detailed modeling and crop analysis that incorporates the diurnal variability of these parameters. The new capability is made possible by utilizing both the CERES SYN1Deg and MERRA-2 data products that include parameters at these resolutions. An assessment of both the meteorological and the solar irradiance data are based upon comparisons with globally distributed surface observations. The meteorological observations from the National Center for Environmental Information’s “Integrated Surface Database” as well as the “Global Summary of the Day” (GSOD) data files. The estimates of solar insolation are compared to the Baseline Solar Radiation Network (BSRN) and other high quality surface measurement networks. Results from the uncertainty assessments demonstrates that the NASA’s meteorological and solar irradiance data can represent a viable alternative to surface observations, particularly in data sparse regions of the world.

solar irradiance↗

NASA NTRS1992

Code inspection instructional validation

The Shuttle Data Systems Branch (SDSB) of the Flight Data Systems Division (FDSD) at Johnson Space Center contracted with Southwest Research Institute (SwRI) to validate the effectiveness of an interactive video course on the code inspection process. The purpose of this project was to determine if this course could be effective for teaching NASA analysts the process of code inspection. In addition, NASA was interested in the effectiveness of this unique type of instruction (Digital Video Interactive), for providing training on software processes. This study found the Carnegie Mellon course, 'A Cure for the Common Code', effective for teaching the process of code inspection. In addition, analysts prefer learning with this method of instruction, or this method in combination with other methods. As is, the course is definitely better than no course at all; however, findings indicate changes are needed. Following are conclusions of this study. (1) The course is instructionally effective. (2) The simulation has a positive effect on student's confidence in his ability to apply new knowledge. (3) Analysts like the course and prefer this method of training, or this method in combination with current methods of training in code inspection, over the way training is currently being conducted. (4) Analysts responded favorably to information presented through scenarios incorporating full motion video. (5) Some course content needs to be changed. (6) Some content needs to be added to the course. SwRI believes this study indicates interactive video instruction combined with simulation is effective for teaching software processes. Based on the conclusions of this study, SwRI has outlined seven options for NASA to consider. SwRI recommends the option which involves creation of new source code and data files, but uses much of the existing content and design from the current course. Although this option involves a significant software development effort, SwRI believes this option will produce the most effective results.

Orr, Kay↗

NASA NTRS2000

Developing CORBA-Based Distributed Scientific Applications from Legacy Fortran Programs

Recent progress in distributed object technology has enabled software applications to be developed and deployed easily such that objects or components can work together across the boundaries of the network, different operating systems, and different languages. A distributed object is not necessarily a complete application but rather a reusable, self-contained piece of software that co-operates with other objects in a plug-and-play fashion via a well-defined interface. The Common Object Request Broker Architecture (CORBA), a middleware standard defined by the Object Management Group (OMG), uses the Interface Definition Language (IDL) to specify such an interface for transparent communication between distributed objects. Since IDL can be mapped to any programming language, such as C++, Java, Smalltalk, etc., existing applications can be integrated into a new application and hence the tasks of code re-writing and software maintenance can be reduced. Many scientific applications in aerodynamics and solid mechanics are written in Fortran. Refitting these legacy Fortran codes with CORBA objects can increase the codes reusability. For example, scientists could link their scientific applications to vintage Fortran programs such as Partial Differential Equation(PDE) solvers in a plug-and-play fashion. Unfortunately, CORBA IDL to Fortran mapping has not been proposed and there seems to be no direct method of generating CORBA objects from Fortran without having to resort to manually writing C/C++ wrappers. In this paper, we present an efficient methodology to integrate Fortran legacy programs into a distributed object framework. Issues and strategies regarding the conversion and decomposition of Fortran codes into CORBA objects are discussed. The following diagram shows the conversion and decomposition mechanism we proposed. Our goal is to keep the Fortran codes unmodified. The conversion- aided tool takes the Fortran application program as input and helps programmers generate C/C++ header file and IDL file for wrapping the Fortran code. Programmers need to determine by themselves how to decompose the legacy application into several reusable components based on the cohesion and coupling factors among the functions and subroutines. However, programming effort still can be greatly reduced because function headings and types have been converted to C++ and IDL styles. Most Fortran applications use the COMMON block to facilitate the transfer of large amount of variables among several functions. The COMMON block plays the similar role of global variables used in C. In the CORBA-compliant programming environment, global variables can not be used to pass values between objects. One approach to dealing with this problem is to put the COMMON variables into the parameter list. We do not adopt this approach because it requires modification of the Fortran source code which violates our design consideration. Our approach is to extract the COMMON blocks and convert them into a structure-typed attribute in C++. Through attributes, each component can initialize the variables and return the computation result back to the client. We have tested successfully the proposed conversion methodology based on the f2c converter. Since f2c only translates Fortran to C, we still needed to edit the converted code to meet the C++ and IDL syntax. For example, C++/IDL requires a tag in the structure type, while C does not. In this paper, we identify the necessary changes to the f2c converter in order to directly generate the C++ header and the IDL file. Our future work is to add GUI interface to ease the decomposition task by simply dragging and dropping icons.

Sang, Janche↗

NASA NTRS2004

Records Management: Preserving the Past to Make the Future

As an intern in the Records Management Office at NASA, I have learned the importance of records management and teamwork. I work in building 60 with Kevin Coleman, the Records and Forms Manager and History Officer, and Deborah Demaline, the senior records specialist. Prior to my internship, I had never paid attention to records and their role in operating a business. However, after my first assignment of identifying files and filling out a C-277 form, I realized the importance of preserving each file. Since NASA is a government agency, keeping our records in a safe and easily accessible area is a major priority. As the records have accumulated over the years, and the destruction of records has been put on hold due to the fairly recent tobacco litigation; the amount of NASA s records has been quickly accumulating. Currently, our records are stored at Plum Brook in Sandusky, Ohio. Recently, rain has leaked through the bunkers and caused damage to some of our records boxes. Plum Brook has been experiencing difficulty in finding the funds to repair the damage. NASA Glenn is reluctant to give Plum Brook more money because the staff at the Sandusky site has not shown us a detailed summary of what they are doing with the funds we give them annually. Even though storing our records at Plum Brook comes with little cost, there are plenty other companies that offer a records storage area and a special software database for easy record retrieval. My assignment is to do a feasibility study on these companies to see how they compare in providing the appropriate criteria for NASA Glenn's needs. Other research I am doing is on which companies will allow us to convert our physical records into an electronic database for quicker retrieval and to eliminate the cost of storing our records in a facility altogether. The two studies have required me to not only work closely with the Records Management Department, but also the Information Technology staff. It has been important for me to thoroughly understand the criteria both departments here at NASA Glenn need in order to make the system effective for the entire organization. The interaction that I am experiencing with different organizations within NASA Glenn and the various companies we are looking at has enhanced my communication skills. Without proficient communication skills, it is difficult to seek how each company meets all of NASA's standards. This includes webx conferences, teleconferences, face-to-face meetings, knowing the appropriate time to ask questions, knowing what those appropriate questions are, and most importantly, being a good listener. During the meetings and conferences I attend, I ensure that I understand where each party is coming from and listen carefully to the points people make. In addition to working with the feasibility study, I will later work on a marketing plan to encourage employees to take care in storing their records and learn the importance of the History Office. Also, the department is trying to develop a special presentation for new employees during their orientation. Assisting Deborah Demaline in taking inventory at Plum Brook is another task that must be done to ensure that the records have been properly placed.

Petro, Kathryn↗

NASA NTRS1994

Technology Benefit Estimator (T/BEST): User's Manual

The Technology Benefit Estimator (T/BEST) system is a formal method to assess advanced technologies and quantify the benefit contributions for prioritization. T/BEST may be used to provide guidelines to identify and prioritize high payoff research areas, help manage research and limited resources, show the link between advanced concepts and the bottom line, i.e., accrued benefit and value, and to communicate credibly the benefits of research. The T/BEST software computer program is specifically designed to estimating benefits, and benefit sensitivities, of introducing new technologies into existing propulsion systems. Key engine cycle, structural, fluid, mission and cost analysis modules are used to provide a framework for interfacing with advanced technologies. An open-ended, modular approach is used to allow for modification and addition of both key and advanced technology modules. T/BEST has a hierarchical framework that yields varying levels of benefit estimation accuracy that are dependent on the degree of input detail available. This hierarchical feature permits rapid estimation of technology benefits even when the technology is at the conceptual stage. As knowledge of the technology details increases the accuracy of the benefit analysis increases. Included in T/BEST's framework are correlations developed from a statistical data base that is relied upon if there is insufficient information given in a particular area, e.g., fuel capacity or aircraft landing weight. Statistical predictions are not required if these data are specified in the mission requirements. The engine cycle, structural fluid, cost, noise, and emissions analyses interact with the default or user material and component libraries to yield estimates of specific global benefits: range, speed, thrust, capacity, component life, noise, emissions, specific fuel consumption, component and engine weights, pre-certification test, mission performance engine cost, direct operating cost, life cycle cost, manufacturing cost, development cost, risk, and development time. Currently, T/BEST operates on stand-alone or networked workstations, and uses a UNIX shell or script to control the operation of interfaced FORTRAN based analyses. T/BEST's interface structure works equally well with non-FORTRAN or mixed software analysis. This interface structure is designed to maintain the integrity of the expert's analyses by interfacing with expert's existing input and output files. Parameter input and output data (e.g., number of blades, hub diameters, etc.) are passed via T/BEST's neutral file, while copious data (e.g., finite element models, profiles, etc.) are passed via file pointers that point to the expert's analyses output files. In order to make the communications between the T/BEST's neutral file and attached analyses codes simple, only two software commands, PUT and GET, are required. This simplicity permits easy access to all input and output variables contained within the neutral file. Both public domain and proprietary analyses codes may be attached with a minimal amount of effort, while maintaining full data and analysis integrity, and security. T/BESt's sotware framework, status, beginner-to-expert operation, interface architecture, analysis module addition, and key analysis modules are discussed. Representative examples of T/BEST benefit analyses are shown.

Generazio, Edward R.↗

NASA NTRS2004

Book Out! An Inventory Story

The NASA Glenn Library is a science and engineering research library providing the most current books, journals, CD-ROM's and documents to support the study of aeronautics, space propulsion and power, communications technology, materials and structures and microgravity science. The GRC technical library also supports the research and development efforts of all scientists and engineers on site via full text electronic files, literature searching, technical reports, etc. As an intern in the NASA Glenn Library, I attempt to support these objectives through efficiently and effectively fulfilling the assignment that was given to me. The assignment that was relegated to me was to catalog National Advisory Committee for Aeronautics, NASA Technical Documents into NASA Galaxie. This process consists of holdings being added to existing Galaxie records, upgrades and editing done to the bibliographic records when needed, adding URL's into Galaxie when they were missing from the record. NASA ASAP and Digidoc was used to locate URL's of PDF's that were not in Galaxie. A spreadsheet of documents with no URL's were maintained. Also, a subject channel of web, fill-text, paid and free, journal and other subject specific pages were developed and expanded fiom current content of intranet pages. To expand upon the second half of my assignment, I was given the project of taking inventory of the library s book collection. I kept record of the books that were not accounted for on a master list I was given to work fiom and submitted them for correction and addition. I also made sure the books were placed in the appropriate order and made corrections to any discrepancies that existed between the master list and what was on the shelf. Upon completion of this assignment, I will have verified that 21,113 books were in the correct location, order and have the correct corresponding serial number and barcode. In conclusion, as of this date I have input around 750 documents into NASA Galaxie, inputting about half of the NASA Technical Documents into the system. The rest of my tenure in this program will consist of finishing the other half of the reports. In regard to the second assignment, I still have about three-quarters of the collection to record and correct.

Panait, Claudia M.↗

NASA NTRS2014

3D Printing In Zero-G ISS Technology Demonstration

The National Aeronautics and Space Administration (NASA) has a long term strategy to fabricate components and equipment on‐demand for manned missions to the Moon, Mars, and beyond. To support this strategy, NASA and Made in Space, Inc. are developing the 3D Printing In Zero‐G payload as a Technology Demonstration for the International Space Station (ISS). The 3D Printing In Zero‐G experiment ('3D Print') will be the first machine to perform 3D printing in space. The greater the distance from Earth and the longer the mission duration, the more difficult resupply becomes; this requires a change from the current spares, maintenance, repair, and hardware design model that has been used on the International Space Station (ISS) up until now. Given the extension of the ISS Program, which will inevitably result in replacement parts being required, the ISS is an ideal platform to begin changing the current model for resupply and repair to one that is more suitable for all exploration missions. 3D Printing, more formally known as Additive Manufacturing, is the method of building parts/objects/tools layer‐by‐layer. The 3D Print experiment will use extrusion‐based additive manufacturing, which involves building an object out of plastic deposited by a wire‐feed via an extruder head. Parts can be printed from data files loaded on the device at launch, as well as additional files uplinked to the device while on‐orbit. The plastic extrusion additive manufacturing process is a low‐energy, low‐mass solution to many common needs on board the ISS. The 3D Print payload will serve as the ideal first step to proving that process in space. It is unreasonable to expect NASA to launch large blocks of material from which parts or tools can be traditionally machined, and even more unreasonable to fly up multiple drill bits that would be required to machine parts from aerospace‐grade materials such as titanium 6‐4 alloy and Inconel. The technology to produce parts on demand, in space, offers unique design options that are not possible through traditional manufacturing methods while offering cost-effective, high‐precision, low‐unit on‐demand manufacturing. Thus, Additive Manufacturing capabilities are the foundation of an advanced manufacturing in space roadmap. The 3D Printing In Zero‐G experiment will demonstrate the capability of utilizing Additive Manufacturing technology in space. This will serve as the enabling first step to realizing an additive manufacturing, print‐on‐demand "machine shop" for long‐duration missions and sustaining human exploration of other planets, where there is extremely limited ability and availability of Earth‐based logistics support. Simply put, Additive Manufacturing in space is a critical enabling technology for NASA. It will provide the capability to produce hardware on‐demand, directly lowering cost and decreasing risk by having the exact part or tool needed in the time it takes to print. This capability will also provide the much‐needed solution to the cost, volume, and up‐mass constraints that prohibit launching everything needed for long‐duration or long‐distance missions from Earth, including spare parts and replacement systems. A successful mission for the 3D Printing In Zero‐G payload is the first step to demonstrate the capability of printing on orbit. The data gathered and lessons learned from this demonstration will be applied to the next generation of additive manufacturing technology on orbit. It is expected that Additive Manufacturing technology will quickly become a critical part of any mission's infrastructure.

Werkheiser, Niki↗

NASA NTRS2003

Exploration of Advanced Probabilistic and Stochastic Design Methods

The primary objective of the three year research effort was to explore advanced, non-deterministic aerospace system design methods that may have relevance to designers and analysts. The research pursued emerging areas in design methodology and leverage current fundamental research in the area of design decision-making, probabilistic modeling, and optimization. The specific focus of the three year investigation was oriented toward methods to identify and analyze emerging aircraft technologies in a consistent and complete manner, and to explore means to make optimal decisions based on this knowledge in a probabilistic environment. The research efforts were classified into two main areas. First, Task A of the grant has had the objective of conducting research into the relative merits of possible approaches that account for both multiple criteria and uncertainty in design decision-making. In particular, in the final year of research, the focus was on the comparison and contrasting between three methods researched. Specifically, these three are the Joint Probabilistic Decision-Making (JPDM) technique, Physical Programming, and Dempster-Shafer (D-S) theory. The next element of the research, as contained in Task B, was focused upon exploration of the Technology Identification, Evaluation, and Selection (TIES) methodology developed at ASDL, especially with regards to identification of research needs in the baseline method through implementation exercises. The end result of Task B was the documentation of the evolution of the method with time and a technology transfer to the sponsor regarding the method, such that an initial capability for execution could be obtained by the sponsor. Specifically, the results of year 3 efforts were the creation of a detailed tutorial for implementing the TIES method. Within the tutorial package, templates and detailed examples were created for learning and understanding the details of each step. For both research tasks, sample files and tutorials are attached in electronic form with the enclosed CD.

Marvis, Dimitri N.↗

NASA NTRS2003

Exploration of Advanced Probabilistic and Stochastic Design Methods

Mavris, Dimitri N.↗

NASA NTRS2000

Test Cases for the Benchmark Active Controls: Spoiler and Control Surface Oscillations and Flutter

As a portion of the Benchmark Models Program at NASA Langley, a simple generic model was developed for active controls research and was called BACT for Benchmark Active Controls Technology model. This model was based on the previously-tested Benchmark Models rectangular wing with the NACA 0012 airfoil section that was mounted on the Pitch and Plunge Apparatus (PAPA) for flutter testing. The BACT model had an upper surface spoiler, a lower surface spoiler, and a trailing edge control surface for use in flutter suppression and dynamic response excitation. Previous experience with flutter suppression indicated a need for measured control surface aerodynamics for accurate control law design. Three different types of flutter instability boundaries had also been determined for the NACA 0012/PAPA model, a classical flutter boundary, a transonic stall flutter boundary at angle of attack, and a plunge instability near M = 0.9. Therefore an extensive set of steady and control surface oscillation data was generated spanning the range of the three types of instabilities. This information was subsequently used to design control laws to suppress each flutter instability. There have been three tests of the BACT model. The objective of the first test, TDT Test 485, was to generate a data set of steady and unsteady control surface effectiveness data, and to determine the open loop dynamic characteristics of the control systems including the actuators. Unsteady pressures, loads, and transfer functions were measured. The other two tests, TDT Test 502 and TDT Test 5 18, were primarily oriented towards active controls research, but some data supplementary to the first test were obtained. Dynamic response of the flexible system to control surface excitation and open loop flutter characteristics were determined during Test 502. Loads were not measured during the last two tests. During these tests, a database of over 3000 data sets was obtained. A reasonably extensive subset of the data sets from the first two tests have been chosen for Test Cases for computational comparisons concentrating on static conditions and cases with harmonically oscillating control surfaces. Several flutter Test Cases from both tests have also been included. Some aerodynamic comparisons with the BACT data have been made using computational fluid dynamics codes at the Navier-Stokes level (and in the accompanying chapter SC). Some mechanical and active control studies have been presented. In this report several Test Cases are selected to illustrate trends for a variety of different conditions with emphasis on transonic flow effects. Cases for static angles of attack, static trailing-edge and upper-surface spoiler deflections are included for a range of conditions near those for the oscillation cases. Cases for trailing-edge control and upper-surface spoiler oscillations for a range of Mach numbers, angle of attack, and static control deflections are included. Cases for all three types of flutter instability are selected. In addition some cases are included for dynamic response measurements during forced oscillations of the controls on the flexible mount. An overview of the model and tests is given, and the standard formulary for these data is listed. Some sample data and sample results of calculations are presented. Only the static pressures and the first harmonic real and imaginary parts of the pressures are included in the data for the Test Cases, but digitized time histories have been archived. The data for the Test Cases are also available as separate electronic files.

Bennett, Robert M.↗

Refine your search to explore more results.