SEARCH · Engineering Papers

Results for “START Program”

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 793 records · Page 44

All sources NASA NTRS DOE OSTI

NASA NTRS2018

History and Status of ALSEP and the Apollo Lunar Data Project

A suite of automated scientific instruments (the Apollo Lunar Surface Experiment Package, or ALSEP) was installed at each of the landing sites of Apollo 12, 14, 15, 16, and 17 from 1969 to 1972. They operated from deployment until decommissioning on 30 September 1977. These data were continuously transmitted to Earth and saved on the Range Tapes, which were recorded at the Manned Space Flight Network stations. These data were also broken out by experiment and sent to the experiment Principal Investigators on what were called the P.I. Tapes. Starting in April 1973 the Range Tape data were stored in digital format on 7-track magnetic tapes, the ARCSAV Tapes. In February 1976, the handling of the Range Tapes was transferred to UT Galveston. They produced 9-track tapes referred to as the Work Tapes. Following the Apollo program the Range and ARCSAV tapes, which were never archived, were lost. The Work Tapes were archived at the National Space Science Data Center (NSSDC). Some investigators archived their individual experiment data with NSSDC as well, but much of the data had minimal documentation, were not in digital form, or were stored in difficult to translate formats. Data from many experiments were never delivered to the NSSDC. The Lunar Data Project was started to address the problem of both missing and not readily usable data. Our effort has resulted in recovery of some of the ARCSAV tapes, recovery and digitization of a large volume of Apollo scientific and technical documentation, and restoration of many ALSEP and other Apollo data collections. Restoration involves deciphering formats, assembling necessary ancillary data (metadata), and packaging data in digital format to be archived with the Planetary Data System (PDS). Recovery of the data from the ARCSAV tapes involved having the tapes read on special equipment and extracting the individual experiment data out of the integrated data stream. We will report on the history and status of the various recovery efforts.

Work Tapes↗

NASA NTRS1976

Voltage profile program for the Kennedy Space Center electric power distribution system

The Kennedy Space Center voltage profile program computes voltages at all busses greater than 1 Kv in the network under various conditions of load. The computation is based upon power flow principles and utilizes a Newton-Raphson iterative load flow algorithm. Power flow conditions throughout the network are also provided. The computer program is designed for both steady state and transient operation. In the steady state mode, automatic tap changing of primary distribution transformers is incorporated. Under transient conditions, such as motor starts etc., it is assumed that tap changing is not accomplished so that transformer secondary voltage is allowed to sag.

Source record↗

NASA NTRS1988

Superfluid Helium Tanker Study (SFHT)

The Superfluid Helium Tanker (SFHT) design is examined for minimum up front cost, a low life cycle cost, and the maximum flexibility/adaptability consistent with the above objectives. The logic flow started with the collection and analysis of user requirements. A configuration trade-off was made to determine the baseline concept for SFHT that most nearly met all of the program objectives. The next task was to develop the baseline concept for the fluid subsystem. With this accomplished the baseline tanker was designed. The commonality task was completed and the program plan and cost estimate will be completed.

Source record↗

NASA NTRS1992

The comet rendezvous asteroid flyby mission

The Comet Rendezvous Asteroid Flyby (CRAF) mission was approved for a New Start by the United States Congress in 1989. CRAF will be developed in parallel with the Cassini (Saturn orbiter/Titan probe) mission. The two missions have been combined into a joint program because of the substantial cost savings (approximately $500 M, or greater than 25 percent) which can be realized by using a common spacecraft design, several identical science instruments, a single management team, and a joint ground operations and data handling system for the two missions. CRAF and Cassini will be the first users of the new Mariner Mark 2 spacecraft which has been designed to carry out the next generation of planetary missions to the outer planets and to small bodies. CRAF is a joint mission between the United States, Germany, and Italy. Each partner will provide both engineering hardware and science experiments. Cassini is a joint mission between the United States, Germany, Italy, and the European Space Agency (ESA), with ESA providing the Titan atmospheric entry probe, called Huygens.

Weissman, Paul↗

NASA NTRS2004

Sounds Clear Enough

I'm a vice president at Line6, where we produce electronics for musical instruments. My company recently developed a guitar that can be programmed to sound like twenty-five different classic guitars - everything from a 1928 National 'Tricone' to a 1970 Martin. It is quite an amazing piece of technology. The guitar started as a research project because we needed to know if the technology was going to be viable and if the guitar design was going to be practical. I've been in this business for about twenty years now, and I still enjoy starting up projects whenever the opportunity presents itself. During the research phase, I headed up the project myself. Once we completed our preliminary research and made the decision to move into development, that's when I handed the project off - and that's where this story really begins.

Zak, Alan↗

NASA NTRS2004

The Biotechnology Facility for International Space Station

The primary mission of the Cellular Biotechnology Program is to advance microgravity as a tool in basic and applied cell biology. The microgravity environment can be used to study fundamental principles of cell biology and to achieve specific applications such as tissue engineering. The Biotechnology Facility (BTF) will provide a state-of-the-art facility to perform cellular biotechnology research onboard the International Space Station (ISS). The BTF will support continuous operation, which will allow performance of long-duration experiments and will significantly increase the on-orbit science throughput. With the BTF, dedicated ground support, and a community of investigators, the goals of the Cellular Biotechnology Program at Johnson Space Center are to: Support approximately 400 typical investigator experiments during the nominal design life of BTF (10 years). Support a steady increase in investigations per year, starting with stationary bioreactor experiments and adding rotating bioreactor experiments at a later date. Support at least 80% of all new cellular biotechnology investigations selected through the NASA Research Announcement (NRA) process. Modular components - to allow sequential and continuous experiment operations without cross-contamination Increased cold storage capability (+4 C, -80 C, -180 C). Storage of frozen cell culture inoculum - to allow sequential investigations. Storage of post-experiment samples - for return of high quality samples. Increased number of cell cultures per investigation, with replicates - to provide sufficient number of samples for data analysis and publication of results in peer-reviewed scientific journals.

Goodwin, Thomas↗

NASA NTRS2009

Rocketdyne - J-2 Saturn V 2nd and 3rd Stage Engine

The J-2 engine was unique in many respects. Technology was not nearly as well-developed in oxygen/hydrogen engines at the start of the J-2 project. As a result, it experienced a number of "teething" problems. It was used in two stages on the Saturn V vehicle in the Apollo Program, as well as on the later Skylab and Apollo/Soyuz programs. In the Apollo Program, it was used on the S-II stage, which was the second stage of the Saturn V vehicle. There were five J-2 engines at the back end of the S-II Stage. In the S-IV-B stage, it was a single engine, but that single engine had to restart. The Apollo mission called for the entire vehicle to reach orbital velocity in low Earth orbit after the first firing of the Saturn-IV-B stage and, subsequently, to fire a second time to go on to the moon. The engine had to be man-rated (worthy of transporting humans). It had to have a high thrust rate and performance associated with oxygen/hydrogen engines, although there were some compromises there. It had to gimbal for thrust vector control. It was an open-cycle gas generator engine delivering up to 230,000 pounds of thrust.

Coffman, Paul↗

NASA NTRS2015

From Pixels to Planets

The Kepler Mission was launched in 2009 as NASAs first mission capable of finding Earth-size planets in the habitable zone of Sun-like stars. Its telescope consists of a 1.5-m primary mirror and a 0.95-m aperture. The 42 charge-coupled devices in its focal plane are read out every half hour, compressed, and then downlinked monthly. After four years, the second of four reaction wheels failed, ending the original mission. Back on earth, the Science Operations Center developed the Science Pipeline to analyze about 200,000 target stars in Keplers field of view, looking for evidence of periodic dimming suggesting that one or more planets had crossed the face of its host star. The Pipeline comprises several steps, from pixel-level calibration, through noise and artifact removal, to detection of transit-like signals and the construction of a suite of diagnostic tests to guard against false positives. The Kepler Science Pipeline consists of a pipeline infrastructure written in the Java programming language, which marshals data input to and output from MATLAB applications that are executed as external processes. The pipeline modules, which underwent continuous development and refinement even after data started arriving, employ several analytic techniques, many developed for the Kepler Project. Because of the large number of targets, the large amount of data per target and the complexity of the pipeline algorithms, the processing demands are daunting. Some pipeline modules require days to weeks to process all of their targets, even when run on NASA's 128-node Pleiades supercomputer. The software developers are still seeking ways to increase the throughput. To date, the Kepler project has discovered more than 4000 planetary candidates, of which more than 1000 have been independently confirmed or validated to be exoplanets. Funding for this mission is provided by NASAs Science Mission Directorate.

supercomputers↗

NASA NTRS2020

Is Structured Agile an Oxymoron? Tales from Implementing and Executing Agile in a US Government Environment

To paraphrase a famous quote, "No plan survives contact with the reality." Software (SW) development is often a classic example of this: whatever the plan was for a particular development, it often does not survive contact with technical realities, budget realities, program realities and schedule realities. Traditionally, SW development has followed a waterfall methodology with requirements being rigorously specified before the design, which was completed before the coding and unit testing started, which were in turn finished before validation and verification started. This model of SW engineering derives much from the HW engineering of large systems, and has been the standard methodology used in US government software acquisitions and systems for decades, with highly variable results. US Government SW requirements are built around Waterfall concepts, which assume that the plan will survive contact with reality, or at least that modifications to the plan are relatively small, and relatively few.Because of the inefficiencies and difficulties inherent in Waterfall, the commercial SW world started using a different SW development methodology called Agile more than 20 years ago. Agile believes that a plan should evolve and learn rapidly in response to the realities encountered. At its core, there are a few key elements of Agile:- A small team of people which is highly flexible and adaptive. The team collaborates and interoperates through sophisticated development architectures and release environments- An iterative, incremental development and release approach which is based upon the concept that knowledge comes from experience within the team, and that the team makes decisions based upon what it knows- A team culture which prizes transparency, inspection and adaptation. These values are necessary so that the team experience and decision making is transparent and responsive to the realities encountered during development and testingSo, how to use Agile in a US Government environment? GMSEC (Goddard Mission Services Evolution Center) develops satellite ground system software for NASA and other US Government agencies. The SW developed by the team contains a large code base of many applications used within satellite mission operations centers. It spans the full gamut of SW development types: from SW which is in a classic maintenance and sustainment mode, to new developments with a fairly well understood scope and approach, to new developments whose scope and approach are quite unclear and which require significant research and prototyping. Team members move between all of these different types of SW development. Waterfall was inadequate to the programmatic and technical needs of the team, as well as the various types of SW development being done. The software plan was not surviving contact with the technical and programmatic realities experienced by the team. To address this, the team started a small pilot project in 2016 to test the use of Agile within a small subset of the team for a new web services application. In early 2018, the use of Agile was expanded to the whole team and all the software, but we had to fulfill the NASA SW development requirements. And we needed to do this while still remaining true to the key Agile elements of transparency, inspection and adaption. In order to do this, the team worked very closely with the Software Process Improvement (SPI) team at NASA Goddard, as well as NASA engineering manageme

Beech, Theresa W.↗

NASA NTRS1984

Modification to shock fitting program

A modified form of the Lepping - Argentiero single spacecraft, shock normal determination procedure is presented. The modified method incorporates a simple predictor-corrector algorithm which allows a faster convergence rate and the use of average values of the parameters for the starting vector.

Acuna, M. H.↗

NASA NTRS2005

Vehicle Integrated Performance Analysis, the VIPA Experience: Reconnecting with Technical Integration

Today's NASA is facing significant challenges and changes. The Exploration initiative indicates a large increase in projects with limited increase in budget. The Columbia report has criticized NASA for its lack of insight and technical integration impacting its ability to provide safety. The Aldridge report is advocating NASA find new ways of doing business. Very early in the Space Launch Initiative (SLI) program a small team of engineers at MSFC were asked to propose a process for performing a system level assessment of a launch vehicle. The request was aimed primarily at providing insight and making NASA a "smart buyer." Out of this effort the VIPA team was created. The difference between the VIPA effort and many integration attempts is that VIPA focuses on using experienced people from various disciplines and a process which focuses them on a technically integrated assessment. Most previous attempts have focused on developing an all encompassing software tool. In addition, VIPA anchored its process formulation in the experience of its members and in early developmental Space Shuttle experience. The primary reference for this is NASA-TP-2001-210092, "Launch Vehicle Design Process: Characterization, Technical Integration, and Lessons Learned," and discussions with its authors. The foundations of VIPA's process are described. The VIPA team also recognized the need to drive detailed analysis earlier in the design process. Analyses and techniques typically done in later design phases, are brought forward using improved computing technology. The intent is to allow the identification of significant sensitivities, trades, and design issues much earlier in the program. This process is driven by the T-model for Technical Integration described in the aforementioned reference. VIPA's approach to performing system level technical integration is discussed in detail. Proposed definitions are offered to clarify this discussion and the general systems integration dialog. VIPA's capabilities and process can now be used to significantly enhance the development and monitoring of realizable project requirements. This is done through the use of VIPA's V-model. Starting with a given concept, VIPA's assessment validates the concept's stated performance, identifies significant issues either with the concept or the requirements, and then re-integrates these issues to determine impacts. This process is discussed along with a description of how it may be integrated into a program's insight and review process. The VIPA process has been employed successfully on several projects including SLI, Orbital Space Plane (OSP), and several heavy lift concepts for Exploration. It has also been proposed for use on the Jupiter Icy Moon (JIMO) spacecraft. The VIPA process has gained favor with both engineering and project organizations for being responsive and insightful. Selected results from these assessments will be presented.

McGhee, David S.↗

NASA NTRSDate not supplied

Axisymmetric Two-Dimensional Modeling of No Vent Filling of a Cryogenic Tank using Generalized Fluid System Simulation Program

Filling a tank with cryogenic fluid is more challenging than filling a tank with water or any other fluid that is in liquid state at atmospheric condition. Filling a tank with cryogenic fluid is a two-step process. First the tank and the transfer line mustbe chilled. Liquid cryogens start flowing into the tank only after the tank and transfer lines are chilled to the fluid saturation temperature. In normal gravity, cryogenic tanks are usually filled from the bottom at nearly atmospheric pressure. The vapor, caused by heat transfer from the warm tank walls, is allowed to vent from the top of the tank while the tank is being filled. Filling a cryogenic tank in the absence of gravity is more challenging because in a non-stratified environment liquid propellantmay not settle at the tank bottom as it does on earth. There is a strong possibility that liquid propellant may exit through the vent valve, which is typically located at the top of the tank to vent propellant vapor. There are several methodsof filling atank in space: Charge-Hold-Vent method [1], Vented-Chill / No-Vent-Fill (VCNVF)[2],and No Vent Fill with TVS assisted injector [3].This paper addressesnumerical modelingofthe No Vent Fill (NVF) processwhere a TVS (Thermodynamic Vent System) augmented injector was used with the vent valve closed during the entire filling process. NVF tests were conducted in the CRYOgenic Orbital Testbed (CRYOTE) tankat NASA/Marshall Space Flight Centerin 2018.The Generalized Fluid System Simulation Program (GFSSP), a general-purpose flow network code [4] was used to simulate the chilland fill process.

Cryogenics↗

NASA NTRS2002

High Resolution X-ray Imaging

NAG5-5020 covered a period of 7.5 years during which a great deal of progress was made in x-ray optical techniques under this grant. We survived peer review numerous times during the effort to keep the grant going. In 1994, when the grant started we were actively pursuing the application of spherical mirrors to improving x-ray telescopes. We had found that x-ray detectors were becoming rapidly more sophisticated and affordable, but that x-ray telescopes were only being improved through the intense application of money within the AXAF program. Clearly new techniques for the future were needed. We were successful in developing and testing at the HELSTF facility in New Mexico a four reflection coma-corrected telescope made from spheres. We were able to demonstrate 0.3 arcsecond resolution, almost to the diffraction limit of the system. The community as a whole was, at that time, not particularly interested in looking past AXAF (Chandra) and the effort needed to evolve. Since we had reached the diffraction limit using non-Wolter optics we then decided to see if we could build an x-ray interferometer in the laboratory. In the lab the potential for improved resolution was substantial. If synthetic aperture telescopes could be built in space, then orders of magnitude improvement would become feasible. In 1998 NASA, under the direction of Dr Nick White of Goddard, started a study to assess the potential and feasibility of x-ray interferometry in space. My work became of central interest to the committee because it indicated that such was possible. In early 1999 we had the breakthrough that allowed us build a practical interferometer. By using flats and hooking up with the Marshall Space Flight Center facilities we were able to demonstrate fringes at 1.25keV on a one millimeter baseline. This actual laboratory demonstration provided the solid proof of concept that NASA needed. As the year progressed the future of x-ray astronomy jelled around the Maxim program. Maxim is a set of two major x-ray astronomy missions based on the concepts I developed and demonstrated under this SR&T grant. The first Maxim is to image the sky at 100 micro-arcsecond resolution. That is one thousand times higher resolution than Hubble. The full Maxim has the ultimate goal of imaging the event horizon of a black hole in an active galactic nucleus (ALAN). This will require 0.1 micro-arcsecond resolution - one million times higher than Hubble! Nonetheless, using the techniques developed under this grant, it has become possible. Maxim Pathfinder is now in the NASA planning for a new start in approximately 20 10. The full Maxim is carried as a vision mission for the post 2015 timeframe. Finally, this grant is the evolved version of the SR&T grant we carried during the 1980s and up to 1994. At that point in time this grant was also working on x-ray optics, but concentrating on x-ray spectroscopy. The techniques developed by 1990 were not chosen for use on Chandra or XMM-Newton because they were too new. During the last year, however, the Constellation-X mission recognized the need for better spectroscopy techniques and tapped our expertise. We were able to support the initial work on Con-X through this program. It now appears that the off-plane mount will be used in Con-X, increasing performance and decreasing cost and risk.

Cash, Webster↗

NASA NTRS2010

Technical Excellence and Communication: The Cornerstones for Successful Safety and Mission Assurance Programs

The paper describes the role of technical excellence and communication in the development and maintenance of safety and mission assurance programs. The Marshall Space Flight Center (MSFC) Safety and Mission Assurance (S&MA) organization is used to illustrate philosophies and techniques that strengthen safety and mission assurance efforts and that contribute to healthy and effective organizational cultures. The events and conditions leading to the development of the MSFC S&MA organization are reviewed. Historic issues and concerns are identified. The adverse effects of resource limitations and risk assessment roles are discussed. The structure and functions of the core safety, reliability, and quality assurance functions are presented. The current organization s mission and vision commitments serve as the starting points for the description of the current organization. The goals and objectives are presented that address the criticisms of the predecessor organizations. Additional improvements are presented that address the development of technical excellence and the steps taken to improve communication within the Center, with program customers, and with other Agency S&MA organizations.

Malone, Roy W.↗

NASA NTRS1979

Performance deterioration based on in-service engine data: JT9D jet engine diagnostics program

Results of analyses of engine performance deterioration trends and levels with respect to service usage are presented. Thirty-two JT9D-7A engines were selected for this purpose. The selection of this engine fleet provided the opportunity of obtaining engine performance data starting before the first flight through initial service such that the trend and levels of engine deterioration related to both short and long term deterioration could be more carefully defined. The performance data collected and analyzed included in-flight, on wing (ground), and test stand prerepair and postrepair performance calibrations with expanded instrumentation where feasible. The results of the analyses of these data were used to: (1) close gaps in previously obtained historical data as well as augment the historical data with more carefully obtained data; (2) refine preliminary models of performance deterioration with respect to usage; (3) establish an understanding of the relationships between ground and altitude performance deterioration trends; (4) refine preliminary recommendations concerning means to reduce and control deterioration; and (5) identify areas where additional effort is required to develop an understanding of complex deterioration issues.

Sallee, G. P.↗

NASA NTRS1984

Modification to shock fitting program

A modified form of the Lepping-Argentiero single spacecraft, shock normal determination procedure is presented. The modified method incorporates a simple predictor-corrector algorithm which allows a faster convergence rate and the use of average values of the parameters for the starting vector.

Acuna, M. H.↗

NASA NTRS1974

Task 12 data dump (phase 2) OME integrated thrust chamber test report

The characteristics and performance of the orbit maneuvering engine for the space shuttle are discussed. Emphasis is placed on the regeneratively cooled thrust chamber of the engine. Tests were conducted to determine engine operating parameters during the start, shutdown, and restart. Characteristics of the integrated thrust chamber and the performance and thermal conditions for blowdown operation without supplementary boundary layer cooling were investigated. The results of the test program are presented.

Tobin, R. D.↗

NASA NTRS1981

Numerical experiments on galaxy formation. I - Introduction and first results

The large, fully three-dimensional n-body programs designed for numerical experiments on the dynamics of galaxies have been used for investigations of protogalactic collapses. The dynamical aspects of galaxy formation dominate in this approach. The present experiments start from a large rotating gaseous mass that is made up of many gas clouds. The large mass collapses because it is out of equilibrium. Stars form as the collapse proceeds. The problem is formulated, limiting-case examples are described, and results from simple 'first cut' models are given. Results with no star formation are contrasted with results for very rapid star formation. All models with gas formed thin disklike structures; some were circular, while others were oval. The principal result from the simple models is that stars continue to form rapidly even after the gas has been depleted to unacceptably low levels (1% of the galactic mass in gas).

Miller, R. H.↗