Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “Troubleshooting”

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 181 records · Page 10

Planetary Protection Bioburden Analysis Program

This program is a Microsoft Access program that performed statistical analysis of the colony counts from assays performed on the Mars Science Laboratory (MSL) spacecraft to determine the bioburden density, 3-sigma biodensity, and the total bioburdens required for the MSL prelaunch reports. It also contains numerous tools that report the data in various ways to simplify the reports required. The program performs all the calculations directly in the MS Access program. Prior to this development, the data was exported to large Excel files that had to be cut and pasted to provide the desired results. The program contains a main menu and a number of submenus. Analyses can be performed by using either all the assays, or only the accountable assays that will be used in the final analysis. There are three options on the first menu: either calculate using (1) the old MER (Mars Exploration Rover) statistics, (2) the MSL statistics for all the assays, or This software implements penetration limit equations for common micrometeoroid and orbital debris (MMOD) shield configurations, windows, and thermal protection systems. Allowable MMOD risk is formulated in terms of the probability of penetration (PNP) of the spacecraft pressure hull. For calculating the risk, spacecraft geometry models, mission profiles, debris environment models, and penetration limit equations for installed shielding configurations are required. Risk assessment software such as NASA's BUMPERII is used to calculate mission PNP; however, they are unsuitable for use in shield design and preliminary analysis studies. The software defines a single equation for the design and performance evaluation of common MMOD shielding configurations, windows, and thermal protection systems, along with a description of their validity range and guidelines for their application. Recommendations are based on preliminary reviews of fundamental assumptions, and accuracy in predicting experimental impact test results. The software is programmed in Visual Basic for Applications for installation as a simple add-in for Microsoft Excel. The user is directed to a graphical user interface (GUI) that requires user inputs and provides solutions directly in Microsoft Excel workbooks. This work was done by Shannon Ryan of the USRA Lunar and Planetary Institute for Johnson Space Center. Further information is contained in a TSP (see page 1). MSC- 24582-1 Micrometeoroid and Orbital Debris (MMOD) Shield Ballistic Limit Analysis Program Lyndon B. Johnson Space Center, Houston, Texas Commercially, because it is so generic, Enigma can be used for almost any project that requires engineering visualization, model building, or animation. Models in Enigma can be exported to many other formats for use in other applications as well. Educationally, Enigma is being used to allow university students to visualize robotic algorithms in a simulation mode before using them with actual hardware. This work was done by David Shores and Sharon P. Goza of Johnson Space Center; Cheyenne McKeegan, Rick Easley, Janet Way, and Shonn Everett of MEI Technologies; Mark Manning of PTI; and Mark Guerra, Ray Kraesig, and William Leu of Tietronix Software, Inc. For further information, contact the JSC Innovation Partnerships Office at (281) 483-3809. MSC-24211-1 Spitzer Telemetry Processing System NASA's Jet Propulsion Laboratory, Pasadena, California The Spitzer Telemetry Processing System (SirtfTlmProc) was designed to address objectives of JPL's Multi-mission Image Processing Lab (MIPL) in processing spacecraft telemetry and distributing the resulting data to the science community. To minimize costs and maximize operability, the software design focused on automated error recovery, performance, and information management. The system processes telemetry from the Spitzer spacecraft and delivers Level 0 products to the Spitzer Science Center. SirtfTlmProc is a unique system with automated error notification and recovery, with a real-time continuous service that can go quiescent after periods of inactivity. The software can process 2 GB of telemetry and deliver Level 0 science products to the end user in four hours. It provides analysis tools so the operator can manage the system and troubleshoot problems. It automates telemetry processing in order to reduce staffing costs. This work was done by Alice Stanboli, Elmain M. Martinez, and James M. McAuley of Caltech for NASA's Jet Propulsion Laboratory. For more information, contact iaoffice @jpl.nasa.gov. This software is available for commercial licensing. Please contact Dan Broderick at Daniel.F. Broderick@jpl.nasa.gov. Refer to NPO-47803. NASA Tech Briefs, September 2013 29 This rapid response computer program predicts Orbiter Wing Leading Edge (WLE) damage caused by ice or foam impact during a Space Shuttle launch (Program "IMPACT2"). The program was developed after the Columbia accident in order to assess quickly WLE damage due to ice, foam, or metal impact (if any) during a Shuttle launch. IMPACT2 simulates an impact event in a few minutes for foam impactors, and in seconds for ice and metal impactors. The damage criterion is derived from results obtained from one sophisticated commercial program, which requires hours to carry out simulations of the same impact events. The program was designed to run much faster than the commercial program with prediction of projectile threshold velocities within 10 to 15% of commercial-program values. The mathematical model involves coupling of Orbiter wing normal modes of vibration to nonlinear or linear springmass models. IMPACT2 solves nonlinear or linear impact problems using classical normal modes of vibration of a target, and nonlinear/ linear time-domain equations for the projectile. Impact loads and stresses developed in the target are computed as functions of time. This model is novel because of its speed of execution. A typical model of foam, or other projectile characterized by material nonlinearities, impacting an RCC panel is executed in minutes instead of hours needed by the commercial programs. Target damage due to impact can be assessed quickly, provided that target vibration modes and allowable stress are known. This work was done by Robert Clark, Jr., Paul Cotter, and Constantine Michalopoulos of The Boeing Company for Johnson Space Center. For further information, contact the JSC Innovation Partnerships Office at (281) 483-3809. MSC-24988-1 Wing Leading Edge RCC Rapid Response Damage Prediction Tool (IMPACT2) Lyndon B. Johnson Space Center, Houston, Texas (3) the MSL statistics for only the accountable assays. Other options on the main menu include a data editing form and utility programs that produce various reports requested by the microbiologists and the project, and tools to generate the groupings for the final analyses. The analyses can be carried out in three ways: Each assay can be treated separately, the assays can be collectively treated for the whole zone as a group, or the assays can be collected in groups designated by the JPL Planetary Protection Manager. The latter approach was used to generate the final report because assays on the same equipment or similar equipment can be assumed to have been exposed to the same environment and cleaning. Thus, the statistics are improved by having a larger population, thereby reducing the standard deviation by the square root of N. For each method mentioned above, three reports are available. The first is a detailed report including all the data. This version was very useful in verifying the calculations. The second is a brief report that is similar to the full detailed report, but does not print out the data. The third is a grand total and summary report in which each assay requires only one line. For the first and second reports, most of the calculations are performed in the report section itself. For the third, all the calculations are performed directly in the query bound to the report. All the numerical results were verified by comparing them with Excel templates, then exporting the data from the Planetary Protection Analysis program to Excel.

Beaudet, Robert A.↗

Putting Integrated Systems Health Management Capabilities to Work: Development of an Advanced Caution and Warning System for Next-Generation Crewed Spacecraft Missions

Integrated System Health Management (ISHM) technologies have advanced to the point where they can provide significant automated assistance with real-time fault detection, diagnosis, guided troubleshooting, and failure consequence assessment. To exploit these capabilities in actual operational environments, however, ISHM information must be integrated into operational concepts and associated information displays in ways that enable human operators to process and understand the ISHM system information rapidly and effectively. In this paper, we explore these design issues in the context of an advanced caution and warning system (ACAWS) for next-generation crewed spacecraft missions. User interface concepts for depicting failure diagnoses, failure effects, redundancy loss, "what-if" failure analysis scenarios, and resolution of ambiguity groups are discussed and illustrated.

integrated system management↗

Amine Swingbed Payload Technology Demonstration

The Amine Swingbed Payload is a technology demonstration of an amine-based carbon dioxide (CO2) and water vapor (H2O) removal system in the U.S. Lab onboard the International Space Station (ISS). The technology utilizes the Carbon dioxide And Moisture Removal Amine Swingbed, or CAMRAS, which is the baseline technology for controlling CO2 and water vapor in the habitable spacecraft for Orion's Multi-Purpose Crew Vehicle (MPCV). For testing on the ISS, the payload also employs water-saving and air-saving subsystems to reduce resources normally vented to space vacuum. This presentation will describe the physical design of the payload, the operation and performance results of the payload during its on-orbit tests between May 2013 and February 2014, and future plans for the payload. Troubleshooting efforts and the resolution of specific anomalies encountered during the initial operation of the payload are also discussed.

Sweterlitsch, Jeffrey↗

Support of LAVA Integration and Testing

The Lunar Advanced Volatile Analysis (LAVA) subsystem is a part of the Regolith and Environment Science & Oxygen and Lunar Volatile Analysis (RESOLVE) Payload that will fly to the lunar pole on the Resource Prospector Mission (RPM) in 2019. The purpose of the mission is to characterize the water on the surface and subsurface of the moon in various locations in order to map the distribution. This characterization of water will help to understand how feasible water is as a resource that can be used for drinking water, breathable air, and propellants in future missions. This paper describes the key support activities performed during a 10 week internship; specifically, troubleshooting the Near Infrared Spectrometer for the Surge Tank (NIRST) instrument count loss, contributing to a clamp to be used in the installation of Resistive Temperature Detectors (RTDs) to tubing, performing a failure analysis of the LAVA Fluid Subsystem (FSS), and finalizing trade studies for release.

Trade Study↗

OSIRIS-REx Touch-and-Go (TAG) Mission Design for Asteroid Sample Collection

The Origins Spectral Interpretation Resource Identification Security Regolith Explorer (OSIRIS-REx) mission is a NASA New Frontiers mission launching in September 2016 to rendezvous with the near-Earth asteroid Bennu in October 2018. After several months of proximity operations to characterize the asteroid, OSIRIS-REx flies a Touch-And-Go (TAG) trajectory to the asteroid's surface to collect at least 60 g of pristine regolith sample for Earth return. This paper provides mission and flight system overviews, with more details on the TAG mission design and key events that occur to safely and successfully collect the sample. An overview of the navigation performed relative to a chosen sample site, along with the maneuvers to reach the desired site is described. Safety monitoring during descent is performed with onboard sensors providing an option to abort, troubleshoot, and try again if necessary. Sample collection occurs using a collection device at the end of an articulating robotic arm during a brief five second contact period, while a constant force spring mechanism in the arm assists to rebound the spacecraft away from the surface. Finally, the sample is measured quantitatively utilizing the law of conservation of angular momentum, along with qualitative data from imagery of the sampling device. Upon sample mass verification, the arm places the sample into the Stardust-heritage Sample Return Capsule (SRC) for return to Earth in September 2023.

OSIRIS-REX TOUCH-AND-GO (TAG) MISSION DESIGN FOR A↗

Experimental Products Development Team (EPDT) Supporting New AWIPS : Capabilities - Part 2

In 2012, the Experimental Products Development Team (EPDT) was formed within NASA's Short-term Prediction Research and Transition (SPoRT) Center to create training for development of plug‐ins to extend the National Weather Service (NWS) Advanced Weather Interactive Processing System (AWIPS) version 2. The broader atmospheric science community had a need for AWIPS II development training being created at SPoRT and EPDT was expanded to include other groups who were looking for training. Since the expansion of the group occurred, EPDT has provided AWIPS II development training to over thirty participants spanning a wide variety of groups such as NWS Systems Engineering Center, NWS Meteorological Development Laboratory, and several NOAA Cooperative Institutes. Participants within EPDT solidify their learning experience through hands‐on learning and by participating in a "code-sprint" in which they troubleshoot existing and develop plug‐ins. The hands‐on learning workshop is instructor lead with participants completing exercises within the AWIPS II Development Environment. During the code sprints EPDT groups work on projects important to the community and have worked on various plug‐ins such as an RGB image recipe creation tool, and an mPing (crowd sourced precipitation type reporting system) ingest and display. EPDT has developed a well‐defined training regime which prepares participants to fully develop plug‐ins for the extendible AWIPS II architecture from ingest to the display of new data. SPoRT has hosted 2 learning workshops and 1 code sprint over the last two years, and continues to build and shape the EPDT group based on feedback from previous workshops. The presentation will provide an overview of EPDT current and future activities, and best practices developed within EPDT.

Burks, Jason E.↗

Internship Abstract - Aerosciences and Flight Mechanics Intern

Mars is a hard place to land on, but my internship with NASA's Aerosciences & Flight Mechanics branch has shown me the ways in which men and women will one day land safely. I work on Mars Aerocapture, an aeroassist maneuver that reduces the fuel necessary to "capture" into Martian orbit before a descent. The spacecraft flies through the Martian atmosphere to lose energy through heating before it exits back into space, this time at a slower velocity and in orbit around Mars. Spacecraft will need to maneuver through the Martian atmosphere to accurately hit their orbit, and they will need to survive the generated heat. Engineering teams need simulation data to continue their designs, and the guidance algorithm that ensures a proper orbit insertion needs to be refined - two jobs that fell to me at the summer's start. Engineers within my branch have developed two concept aerocapture vehicles, and I run simulations on their behavior during the maneuver. I also test and refine the guidance algorithm. I spent the first few weeks familiarizing myself with the simulation software, troubleshooting various guidance bugs and writing code. Everything runs smoothly now, and I recently sent my first set of trajectory data to a Thermal Protection System group so they can incorporate it into their heat-bearing material designs. I hope to generate plenty of data in the next few weeks for various engineering groups before my internship ends mid-August. My major accomplishment so far is improving the guidance algorithm. It is a relatively new algorithm that promises higher accuracy and fuel efficiency, but it hasn't undergone extensive testing yet. I've had the opportunity to work with the principal developer - a professor at Iowa State University - to find and fix several issues. I was also assigned the task of expanding the branch's aerodynamic heating simulation software. I am excited to do this because engineers in the future will use my work to generate meaningful data and make design decisions. My internship has taught me to how to teach myself. There are no tutors, study sessions or professor office hours. When I am given an assignment I am expected to figure out how to accomplish it, and I have grown in my problem solving abilities. My summer experience has reinforced my drive to work at NASA, and I can definitely see myself working full time on the aerocapture project, or something similar.

Rangel, John↗

Moving Away from Ones and Zeros, Designing a Ground Data System Based on Higher Levels of Abstraction

Previous JPL ground systems have been designed with the Ground Data System (GDS) engineer in mind. The focus on these systems has been on packaging and delivery of low level information (frames, packets, telemetry values) to the end user. It was not that long ago when project teams would be huddled over a workstation, examining crude displays of telemetry bits organized in various ways, trying to determine the status of a spacecraft. Understanding the data often required additional levels of GDS expertise, or worse, transformation of the raw data into alternative formats followed by ingestion into other tools so that the data became meaningful. The primary focus was often to answer these types of questions: "Why did this particular frame fail Reed-Solomon decode? Why did this packet get marked as invalid? Why am I missing a block of telemetry from my query?" -- which are completely valid questions to ask from a GDS Engineer's point of view, and large families of tools have been designed to help answer these questions. But these are not the questions that most users care about - which are more like: "Why is the battery state of charge trending down? Show me a summary image report for the last traverse to the target. Show me a data accountability summary for the last DSN pass." Answers to these questions, which are what users are looking for, requires a higher level of abstraction and supporting tools than mining through ones and zeros. JPL has created a next generation capability called the Mission Data Processing and Control System (MPCS) which is designed to support this higher level of abstraction by providing customizable views of the ground system combining collections of lower level information into more meaningful ways. Instead of examining frames, packets, and individual telemetry data points -- MPCS is capable of providing comprehensive summary reports, product status, overall flight/ground event status, as well as payload health summaries. Based on these higher level views, end users can make tactical or strategic decisions, or drop into detailed analysis as needed. System designers need to continue building systems that support low level GDS troubleshooting - but the basic design of a GDS should be geared towards what end users actually need to see. This paper will describe the capabilities of MPCS that directly support these higher levels of abstraction, and which are being used today in missions such as the Mars Science Laboratory and other NASA missions.

MPCS↗

Structural CNT Composites: Developing a Carbon Nanotube Filament Winder - Part I

Carbon nanotube (CNT) based materials promise advances in the production of high strength and multifunctional components for aerospace and other applications. Specifically, in tension dominated applications, the latest CNT based filaments are yielding composite properties comparable to or exceeding composites from more established fibers such as Kevlar and carbon fiber. However, for the properties of these materials to be fully realized at the component level, suitable manufacturing processes have to be developed. These materials handle differently from conventional fibers, with different wetting characteristics and behavior under load. The limited availability of bulk forms also requires that the equipment be scaled down accordingly to tailor the process development approach to material availability. Here, the development of hardware and software for filament winding of carbon nanotube based tapes and yarns is described. This hardware features precision guidance of the CNT material and control of the winding tension over a wide range in an open architecture that allows for effective process control and troubleshooting during winding. Use of the filament winder to develop CNT based Composite Overwrapped Pressure Vessels (COPVs) shall also be discussed.

Sauti, Godfrey↗

Particle Streak Velocimetry of Supersonic Nozzle Flows

A novel velocimetry technique to probe the exhaust flow of a laboratory scale combustor is being developed. The technique combines the advantages of standard particle velocimetry techniques and the ultra-fast imaging capabilities of a streak camera to probe high speed flows near continuously with improved spatial and velocity resolution. This "Particle Streak Velocimetry" technique tracks laser illuminated seed particles at up to 236 picosecond temporal resolution allowing time-resolved measurement of one-dimensional flows exceeding 2000 m/s as are found in rocket nozzles and many other applications. Developmental tests with cold nitrogen have been performed to validate and troubleshoot the technique with supersonic flows of much lower velocity and without background noise due to combusting flow. Flow velocities on the order of 500 m/s have been probed with titanium dioxide particles and a continuous-wave laser diode. Single frame images containing multiple streaks are analyzed to find the average slope of all incident particles corresponding to the centerline axial flow velocity. Long term objectives for these tests are correlation of specific impulse to theoretical combustion predictions and direct comparisons between candidate green fuels and the industry standard, monomethylhydrazine, each tested under identical conditions.

Willits, J. D.↗

Designing for Reliability and Robustness

Long duration spaceflight has a negative effect on the human body, and exercise countermeasures are used on-board the International Space Station (ISS) to minimize bone and muscle loss, combatting these effects. Given the importance of these hardware systems to the health of the crew, this equipment must continue to be readily available. Designing spaceflight exercise hardware to meet high reliability and availability standards has proven to be challenging throughout the time the crewmembers have been living on ISS beginning in 2000. Furthermore, restoring operational capability after a failure is clearly time-critical, but can be problematic given the challenges of troubleshooting the problem from 220 miles away. Several best-practices have been leveraged in seeking to maximize availability of these exercise systems, including designing for robustness, implementing diagnostic instrumentation, relying on user feedback, and providing ample maintenance and sparing. These factors have enhanced the reliability of hardware systems, and therefore have contributed to keeping the crewmembers healthy upon return to Earth. This paper will review the failure history for three spaceflight exercise countermeasure systems identifying lessons learned that can help improve future systems. Specifically, the Treadmill with Vibration Isolation and Stabilization System (TVIS), Cycle Ergometer with Vibration Isolation and Stabilization System (CEVIS), and the Advanced Resistive Exercise Device (ARED) will be reviewed, analyzed, and conclusions identified so as to provide guidance for improving future exercise hardware designs. These lessons learned, paired with thorough testing, offer a path towards reduced system down-time.

Svetlik, Randall G.↗

Modifying a Commercial Centrifuge to Reduce Electromagnetic Interference and Evaluating Functionality of Ultrasound Equipment

The Project Management and Engineering Branch (SF4) supports the Human Health and Performance Directorate (HH&P) and is responsible for developing and supporting human systems hardware for the International Space Station (ISS). When a principal investigator's (PI) medical research project on the ISS is accepted, SF4 develops the necessary hardware and software to transport to the ISS. The two projects I primarily worked on were the centrifuge and ultrasound projects. Centrifuge: One concern with spacecraft such as the ISS is electromagnetic interference (EMI) from onboard equipment, typically from radio waves (frequencies of ~3 kHz to ~300 GHz), which can negatively affect nearby circuitry. Standard commercial centrifuges produce EMI above safety limits, so my task was to help reduce EMI production from this equipment. Two centrifuges were tested: one unmodified as a control and one modified. To reduce EMI below safety limits, one centrifuge was modified to become a Faraday shield, in which significant electrical contact was made between all regions of the centrifuge housing. This included removing non-conductive paint, applying conductive fabric to the lid and foam sealer, adding a 10,000 μF decoupling capacitor across the power supply, and adding copper adhesive-mount gaskets to the housing interior. EMI testing of both centrifuges was performed in the EMI/EMC Control Test and Measurement Facility. EMI for both centrifuges was below safety limits for frequencies between 10 MHz and 15 GHz (pass); however, between 14 kHz and 10 MHz, EMI for the unmodified centrifuge exceeded safety limits (fail) as expected. Alternatively, for the modified centrifuge with the Faraday shield, EMI was below the safely limit of 55 dBμV/m for electromagnetic frequencies between 14 kHz and 10 MHz. This result indicates our modifications were successful. The successful EMI test allowed us to communicate with the vendor what modifications they needed to make to their commercial unit to meet our specifications and to understand what needs to be done in lab to the new centrifuge. Our modifications will provide a standard for readying centrifuges for future missions. Once the new modified centrifuge arrives by the vendor, it will need to undergo EMI testing again for validation. The centrifuge is also in the process of compatibility testing with a custom stowage drawer, which is an ongoing project in SF4. Both of these items will be payloads on future missions to the ISS for various research purposes. Ultrasound: ISS currently has an onboard ultrasound (Ultrasound 2 system) for research and medical purposes. Every piece of medical flight hardware has an equivalent ground-unit so instrumentation can be routinely evaluated and transported to the ISS if necessary. The ground-unit ultrasound equipment must be evaluated every six months using a task performance sheet (TPS). A TPS is a document, written by the appropriate scientists and engineers, which describes how to run equipment and is written in such a way that astronauts with unspecialized training can follow the tasks. I was responsible for performing six TPSs on a combination of three ultrasounds and two video power converters (VPCs). Performing a TPS involves checking out and computationally documenting each piece of equipment removed from storage locations, setting up hardware and software, performing tasks to verify functionality, returning equipment, and logging items back into the computerized system. My work revealed all ground-unit ultrasounds were functioning properly. Because of proper function, a discrepancy report (DR) did not have to be opened. The TPS was then passed along to the Quality Engineering (QE) for review and ultimately given to Quality Assurance (QA). Other projects: In addition to my main projects, I participated in other tasks including troubleshooting an EEG headband, volunteering for an ultrasound training research study, and conformal coating printed circuit boards. My internship at SF4 has helped me understand how space systems hardware development for the ISS fits into NASA's mission and vision.

Greening, Gage J.↗

Monitoring of the Atmosphere on the International Space Station with the Air Quality Monitor

During the early years of human spaceflight, short duration missions allowed for monitoring of the spacecraft environment to be performed via archival sampling, in which samples were returned to Earth for analysis. With the construction of the International Space Station (ISS) and the accompanying extended mission durations, the need for enhanced, real-time monitors became apparent. The Volatile Organic Analyzer (VOA) operated on ISS for 7 years, where it assessed trace volatile organic compounds in the cabin air. The large and fixed-position VOA was eventually replaced with the smaller Air Quality Monitor (AQM). Since March 2013, the atmosphere of the U.S. Operating Segment (USOS) has been monitored in near real-time by a pair of AQMs. These devices consist of a gas chromatograph (GC) coupled with a differential mobility spectrometer (DMS) and currently target detection list of 22 compounds. These targets are of importance to both crew health and the Environmental Control and Life Support Systems (ECLSS) on ISS. Data is collected autonomously every 73 hours, though the units can be controlled remotely from mission control to collect data more frequently during contingency or troubleshooting operations. Due to a nominal three-year lifetime on-orbit, the initial units were replaced in February 2016. This paper will focus on the preparation and use of the AQMs over the past several years. A description of the technical aspects of the AQM will be followed by lessons learned from the deployment and operation of the first set of AQMs. These lessons were used to improve the already-excellent performance of the instruments prior to deployment of the replacement units. Data trending over the past several years of operation on ISS will also be discussed, including data obtained during a survey of the USOS modules. Finally, a description of AQM use for contingency and investigative studies will be presented.

Wallace William T.↗

Development of a 13 kW Hall Thruster Propulsion System Performance Model for AEPS

The Advanced Electric Propulsion System (AEPS) program will develop a flight 13kW Hall thruster propulsion system based on NASA's HERMeS thruster. The AEPS system includes the Hall Thruster, the Power Processing Unit (PPU) and the Xenon Flow Controller (XFC). These three primary components must operate together to ensure that the system generates the required combinations of thrust and specific impulse at the required system efficiencies for the desired system lifetime. At the highest level, the AEPS system will be integrated into the spacecraft and will receive power, propellant, and commands from the spacecraft. Power and propellant flow rates will be determined by the throttle set points commanded by the spacecraft. Within the system, the major control loop is between the mass flow rate and thruster current, with time-dependencies required to handle all expected transients, and additional, much slower interactions between the thruster and cathode temperatures, flow controller and PPU. The internal system interactions generally occur on shorter timescales than the spacecraft interactions, though certain failure modes may require rapid responses from the spacecraft. The AEPS system performance model is designed to account for all these interactions in a way that allows evaluation of the sensitivity of the system to expected changes over the planned mission as well as to assess the impacts of normal component and assembly variability during the production phase of the program. This effort describes the plan for the system performance model development, correlation to NASA test data, and how the model will be used to evaluate the critical internal and external interactions. The results will ensure the component requirements do not unnecessarily drive the system cost or overly constrain the development program. Finally, the model will be available to quickly troubleshoot any future unforeseen development challenges.

Stanley, Steven↗

Position Paper - pFLogger: The Parallel Fortran Logging framework for HPC Applications

In the context of high performance computing (HPC), software investments in support of text-based diagnostics, which monitor a running application, are typically limited compared to those for other types of IO. Examples of such diagnostics include reiteration of configuration parameters, progress indicators, simple metrics (e.g., mass conservation, convergence of solvers, etc.), and timers. To some degree, this difference in priority is justifiable as other forms of output are the primary products of a scientific model and, due to their large data volume, much more likely to be a significant performance concern. In contrast, text-based diagnostic content is generally not shared beyond the individual or group running an application and is most often used to troubleshoot when something goes wrong. We suggest that a more systematic approach enabled by a logging facility (or logger) similar to those routinely used by many communities would provide significant value to complex scientific applications. In the context of high-performance computing, an appropriate logger would provide specialized support for distributed and shared-memory parallelism and have low performance overhead. In this paper, we present our prototype implementation of pFlogger a parallel Fortran-based logging framework, and assess its suitability for use in a complex scientific application.

Fortran↗

POSITION PAPER - pFLogger: The Parallel Fortran Logging Framework for HPC Applications

In the context of high performance computing (HPC), software investments in support of text-based diagnostics, which monitor a running application, are typically limited compared to those for other types of IO. Examples of such diagnostics include reiteration of configuration parameters, progress indicators, simple metrics (e.g., mass conservation, convergence of solvers, etc.), and timers. To some degree, this difference in priority is justifiable as other forms of output are the primary products of a scientific model and, due to their large data volume, much more likely to be a significant performance concern. In contrast, text-based diagnostic content is generally not shared beyond the individual or group running an application and is most often used to troubleshoot when something goes wrong. We suggest that a more systematic approach enabled by a logging facility (or 'logger') similar to those routinely used by many communities would provide significant value to complex scientific applications. In the context of high-performance computing, an appropriate logger would provide specialized support for distributed and shared-memory parallelism and have low performance overhead. In this paper, we present our prototype implementation of pFlogger - a parallel Fortran-based logging framework, and assess its suitability for use in a complex scientific application.

Clune, Thomas L.↗

Implementing Reliability Centered Maintenance (RCM) with State of the Art PT&I Technologies

Building on the work that was started two decades ago, Jacobs Space Operations Group has utilized state of the art PTI technologies to assess the current condition of the assets they manage under the Test and Operations Support Contract (TOSC). Specifically, the Asset Management department leveraged the benefits of ultrasound technology to quantify a motor issue in the Liquid Oxygen Storage Area, and troubleshoot the sources prior to loading the tank to perform Verification and Validation (VV) activities. This technology was efficient, easy to implement, and provided system engineers with data on a possible source of the problem. In situations where legacy motors are exhibiting unexpected noises, it may seem easier to remove and refurbish the motor and replace the bearings because that solution resolves most of the common causes of the noise. However, that solution would have involved additional spending and may not have solved issues stemming from the foundation, if those existed. By utilizing the ultrasound equipment provided by UE Systems, the sound profiles allowed Jacobs TOSC team to determine that the issue resembled a faulty bearing. After replacing the bearing, the unexpected noise ceased.

Reliability Centered Maintenance↗

pFlogger: The Parallel Fortran Logging Utility

In the context of high performance computing (HPC), software investments in support of text-based diagnostics, which monitor a running application, are typically limited compared to those for other types of IO. Examples of such diagnostics include reiteration of configuration parameters, progress indicators, simple metrics (e.g., mass conservation, convergence of solvers, etc.), and timers. To some degree, this difference in priority is justifiable as other forms of output are the primary products of a scientific model and, due to their large data volume, much more likely to be a significant performance concern. In contrast, text-based diagnostic content is generally not shared beyond the individual or group running an application and is most often used to troubleshoot when something goes wrong. We suggest that a more systematic approach enabled by a logging facility (or 'logger)' similar to those routinely used by many communities would provide significant value to complex scientific applications. In the context of high-performance computing, an appropriate logger would provide specialized support for distributed and shared-memory parallelism and have low performance overhead. In this paper, we present our prototype implementation of pFlogger - a parallel Fortran-based logging framework, and assess its suitability for use in a complex scientific application.

Clune, Tom↗