SEARCH · Engineering Papers
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.
The intent of this presentation is to give status to multiple audience types on the SpaceCube data processing technology at GSFC. SpaceCube has grown to support multiple missions inside and outside of NASA, and we are being requested to give technology overviews in various forums.
The Integrated Medical Model (IMM) was designed to forecast relative changes for a specified set of crew health and mission success risk metrics by using a probabilistic (stochastic process) model based on historical data, cohort data, and subject matter expert opinion. A probabilistic approach is taken since exact (deterministic) results would not appropriately reflect the uncertainty in the IMM inputs. Once the IMM was conceptualized, a plan was needed to rigorously assess input information, framework and code, and output results of the IMM, and ensure that end user requests and requirements were considered during all stages of model development and implementation. METHODS: In 2008, the IMM team developed a comprehensive verification and validation (VV) plan, which specified internal and external review criteria encompassing 1) verification of data and IMM structure to ensure proper implementation of the IMM, 2) several validation techniques to confirm that the simulation capability of the IMM appropriately represents occurrences and consequences of medical conditions during space missions, and 3) credibility processes to develop user confidence in the information derived from the IMM. When the NASA-STD-7009 (7009) was published, the IMM team updated their verification, validation, and credibility (VVC) project plan to meet 7009 requirements and include 7009 tools in reporting VVC status of the IMM. RESULTS: IMM VVC updates are compiled recurrently and include 7009 Compliance and Credibility matrices, IMM VV Plan status, and a synopsis of any changes or updates to the IMM during the reporting period. Reporting tools have evolved over the lifetime of the IMM project to better communicate VVC status. This has included refining original 7009 methodology with augmentation from the NASA-STD-7009 Guidance Document. End user requests and requirements are being satisfied as evidenced by ISS Program acceptance of IMM risk forecasts, transition to an operational model and simulation tool, and completion of service requests from a broad end user consortium including Operations, Science and Technology Planning, and Exploration Planning. CONCLUSIONS: The VVC approach established by the IMM project of combining the IMM VV Plan with 7009 requirements is comprehensive and includes the involvement of end users at every stage in IMM evolution. Methods and techniques used to quantify the VVC status of the IMM have not only received approval from the local NASA community but have also garnered recognition by other federal agencies seeking to develop similar guidelines in the medical modeling community.
This software is an implementation of the Licklider Transmission Protocol (LTP), a communications protocol intended to support the Bundle Protocol in Delay-Tolerant Network (DTN) operations. LTP is designed to provide retransmission-based reliability over links characterized by extremely long message round-trip times and/or frequent interruptions in connectivity. Communication in interplanetary space is the most prominent example of this sort of environment, and LTP is principally aimed at supporting long-haul reliable transmission over deep-space RF links. Like any reliable transport service employing ARQ (Automatic Repeat re-Quests), LTP is stateful. In order to assure the reception of a block of data it has sent, LTP must retain for possible retransmission all portions of that block which might not have been received yet. In order to do so, it must keep track of which portions of the block are known to have been received so far, and which are not, together with any additional information needed for purposes of retransmitting part, or all, of the block. Long round-trip times mean substantial delay between the transmission of a block of data and the reception of an acknowledgement from the block s destination, signaling arrival of the block. If LTP postponed transmission of additional blocks of data until it received acknowledgement of the arrival of all prior blocks, valuable opportunities to use what little deep space transmission bandwidth is available would be forever lost. For this reason, LTP is based in part on a notion of massive state retention. Any number of requested transmission conversations (sessions) may be concurrently in flight at various displacements along the link between two LTP engines, and the LTP engines must necessarily retain transmission status and retransmission resources for all of them. Moreover, if any of the data of a given block are lost en route, it will be necessary to retain the state of that transmission during an additional round trip while the lost data are retransmitted; even multiple retransmission cycles may be necessary. LTP's possible multiplicity of sessions per association makes it necessary for each segment of application data to include an additional demultiplexing token: a session ID that uniquely identifies the session in which the segment was issued and, implicitly, the block of data being conveyed by this session. This software comprises a prototype implementation developed by Johns Hopkins University APL in cooperation with JPL, together with adaptations that improve the robustness, correctness, and operability of that implementation.
A proposed packet telemetry system employing automatic retransmission request (ARQ) mode of error control is characterized. Limitations of the present multiplexing/demultiplexing approach are considered, and the use of the proposed system in near-earth satellites in the 1980s is suggested. Onboard processing and an adaptive multiplexing technique are described, as is an elastic buffer, required because the instantaneous data rate will be different from the telemetry transmission rate. The telemetry packets would be encoded into a powerful error-detection block code. A mechanism involving temporary buffering in a long shift register will permit retransmission request from the ground station for packets received in error. The ARQ mode of operation should ensure essentially error-free transmission at lower signal-to-noise ratios and at considerably higher transmission rates than are usually used.
The University of Alaska Fairbanks (UAF) Alaska Hydrokinetic Energy Research Center was tasked with developing a real-time data telemetry / remote power generation system to monitor frazil ice conditions in the Kvichak River in support of the U.S. Department of Energy funded "Next Generation MHK River Power System Optimized for Performance, Durability and Survivability" project. A real-time telemetry system was requested because of the short time span between the end of the frazil ice season when the instruments would be recovered, limited vessel availability and the project end-date. To meet the project objectives, UAF designed and assembled a remote power/real-time data telemetry system that included an auto start propane generator, a small PV array, a small battery bank and line-of-sight radios as well as two sonar systems to monitor river velocity and water column acoustic backscatter strength. Both sonars included internal batteries for powering the instruments in case of failure of the shore based power system. The sonars, deployed in ~5 m of water on the bed of the Kvichak River, adjacent to the Village of Igiugig, Alaska were tethered to shore via a waterproof armored cable that conveyed power to the subsurface instruments and data from the instruments to the shore based telemetry system. The instruments were programmed to record data internally as well as to transmit data serially over the cables to the shore based system. The system was in-place between November, 2016 and June, 2017. While the real-time data telemetry system was not successful and the remote power generation power system was only partially successful, the system design included sufficient redundant power in the form of internal instrument batteries to enable the collection of nearly three months of overlapping velocity and backscatter data (from November through February) and a record of acoustic backscatter strength spanning the entire ~150 day frazil ice season between November, 2016 and ~April, 2017. This submission includes the overwinter ice study plan, raw data, and report.
Opportunities for multi-point measurements, greater revisit frequency, failure robustness, and improved cost effectiveness motivate consideration of Distributed Spacecraft Missions (DSMs) for future Earth science missions. However, careful analysis is required to assess the distributed sensing capabilities of a constellation compared to more mature monolithic spacecraft while also considering other important dimensions such as cost and risk. The large combinatorial DSM design space limits existing mission analysis tools and exploration methods which emphasize monolithic design variables. The Trade-space Analysis Tool for Constellations (TAT-C) under development at Goddard seeks to enumerate and evaluate alternative mission architectures to minimize cost and maximize scientific return for pre-defined goals during pre-phase A analysis.Similar to other model-centric engineering efforts, efficient data management is a significant challenge for DSM mission analysis. In TAT-C, a Knowledge Base (KB) is envisioned as a cumulative central repository of information and meta-information about DSMs. Initial KB concepts store related data for reuse within or across mission analyses; however, over time, the KB is envisioned to be an important layer to coordinate actions of both human analysts and automated design agents to search a large design space for desirable mission alternatives. Preliminary KB research builds on a modern web technology stack to provide the following functionality: 1) storage of trade-space search requests which set requirements and constraints for DSM concepts, 2) storage of analysis results which quantify performance metrics for evaluated DSM concepts, 3) a RESTful application programming interface (API) for scripted access to data from TAT-C modules, 4) web-based graphical user interface (GUI) for manual access to underlying data, and 5) access control and management restrictions relevant to data protection and security. These efforts have culminated in a prototype KB used by the research team during TAT-C development to assess opportunities for future work.
A system, apparatus and method are provided in which a range of virtual memory addresses and a copy of that range are mapped to the same first system address range in a data processing system until an address in the virtual memory address range, or its copy, is written to. The common system address range includes a number of divisions. Responsive to a write request to an address in a division of the common address range, a second system address range is generated. The second system address range is mapped to the same physical addresses as the first system address range, except that the division containing the address to be written to and its corresponding division in the second system address range are mapped to different physical addresses. First layer mapping data may be stored in a range table buffer and updated when the second system address range is generated.
With the rapid increase in vehicle electrification, there is a need for up-to-date, publicly available national data to understand end user charging and driving patterns, as well as vehicle and infrastructure performance, to inform research planning. Energetics worked with various partners to collect and analyze plug-in electric vehicle (PEV) and electric vehicle supply equipment (EVSE) data from 2019 to 2022. All sensitive attributes have been removed from this publicly available dataset. Researchers from one of the partner national labs under non-disclosure agreement (NDA) can request access to additional attributes by reaching out to evwattsdata@energetics.com.
Effective operation of the Hanford Tank Waste Treatment and Immobilization Plant (WTP) will require information collected from sampling and/or monitoring to maintain environmental compliance, product quality, and operating efficiency. The U.S. Department of Energy (DOE) – Office of River Protection (ORP) recognizes the potential long-term benefit of developing real-time, in-line monitoring (RTIM) at the WTP to improve the current strategy of collecting tens of thousands of samples and analyzing them. In-line monitoring can decrease processing time associated with waiting for sample analysis, reduce workers’ exposure to radiation and chemical hazards, decrease secondary waste volumes, potentially improve product quality, and provide production support and enhance overall operational control. The Assistant Manager, WTP chartered an Integrated Technical Team (ITT), which includes personnel from the Savannah River National Laboratory (SRNL), Bechtel National, Inc., and DOE-ORP, to evaluate the capability and potential benefits of replacing routine sample collection requirements with real-time, in-line monitoring. The initial focus of the ITT is the Direct Feed Low Activity Waste (DFLAW) Program. This work scope is being performed in multiple phases. Phase 1 is Requirements and Opportunities Analysis, Phase 2 is Applications and Benefits Determination, and Phase 3 is Qualification and Demonstration. Phase 1 included 6 tasks and was completed by SRNL in 2017. The tasks in Phase 1 were: (1) determining the functional requirements for determining analytes and properties of streams, (2) determining the technical basis for process control, (3) determining the sampling points within the Low Activity Waste (LAW) facility and Effluent Management Facility (EMF), (4) data quality and management, (5) process control challenges, and (6) preparing a Preliminary Analysis Plan. DOE-ORP was briefed on the findings from the Phase 1 tasks and requested that Phase 2 work focus on establishing a basis for a materials balance approach that minimized process sampling. The Phase 2 work scope contains tasks to evaluate a materials balance only approach as well as continuing scoping evaluations for instruments that could be used for RTIM. The Phase 2 work scope was completed by both SRNL and Pacific Northwest National Laboratory (PNNL). The tasks performed in Phase 2 were: 1. Overall program administration and technical oversight 2. Evaluation of a Material Balance Approach, a. Evaluation of uncertainty of this approach compared to uncertainty of current methods b. Evaluation of automating the material balance within the framework of existing control software, c. Development of the methodology to obtain and evaluate data during cold commissioning to support a material balance approach, and d. Development of a framework to utilize during presentation of the revised approach to stakeholders and regulators. 3. Screening Evaluations of Instruments to Supplement the Material Balance Approach, a. AP-105 melter condensate evaluations, and b. Screening testing with simulants. 4. Evaluation of the current DFLAW feed qualification program to identify analytes that could be eliminated, a. Inorganic analytes, b. Radionuclides, and c. Organic analytes. This report describes the results of Task 3b, Screening testing with simulants. The Savannah River National Laboratory requested demonstrations of commercially available analytical instruments by the vendors or laboratory demonstration. The techniques tested included: Raman spectroscopy, Infrared spectroscopy (IR), laser induced breakdown spectroscopy (LIBS), X-Ray Fluorescence Spectroscopy (XRF), and ion-selective electrochemical probes. Additionally, the instrumentation would need to be durable enough to withstand the environment of the plant, preferably with little to no maintenance. The insertion point of the instrument would be dependent upon the instrumentation.
The U.S. Department of Energy (DOE) Office of Legacy Management conducted annual sampling at the Rulison, Colorado, Site for the Long-Term Hydrologic Monitoring Program (LTHMP) on May 20–22 and 27, 2015. Several of the land owners were not available to allow access to their respective properties, which created the need for several sample collection trips. This report documents the analytical results of the Rulison monitoring event and includes the trip report and the data validation package (Appendix A). The groundwater and surface water monitoring were shipped to the GEL Group Inc. laboratories for analysis. All requested analyses were successfully completed. Samples were analyzed for gamma-emitting radionuclides by high- resolution gamma spectrometry. Tritium was analyzed using two methods, the conventional tritium method, which has a detection limit on the order of 400 picocuries per liter (pCi/L), and the enriched method (for selected samples), which has a detection limit on the order of 3 pCi/L.
The Thermal-Epithermal eXperiments (TEX) – Hafnium (TEX-Hf) experiments were completed in October 2022 at the DOE National Criticality Experiments Research Center (NCERC) at the Nevada National Security Site (NNSS). This measurement campaign provides seven unique configurations that can be used to validate the neutron absorption and scattering cross sections of hafnium in a highly enriched uranium (HEU) system. Hafnium is a strong neutron absorber important for marine propulsion systems. Mike Zerkle of the Naval Nuclear Laboratory (NNL) states, “The experiments were requested by Naval Reactors to provide a suite of unclassified, clean, and well-characterized benchmarks to drive improvements to hafnium nuclear data.” The experiments were a collaboration between Los Alamos National Laboratory (LANL), Lawrence Livermore National Laboratory (LLNL), and NNL, funded by the Nuclear Criticality Safety Program (NCSP). The Hf was procured directly by NNL and provided for the experiment.
Following are examples of a 4 to 2 to 1 merge of proton bunches in RHIC obtained by running the simulation code rhic2mrg23. As the code runs, the user is prompted to enter several numbers. For these examples, RF harmonic number 1440.0 is entered. An RF frequency of 112.597 696 626 MHz at this harmonic is entered. This gives a proton energy of 100 GeV. The merge simulation starts with a uniform distribution of unbunched protons. 2.0 eV-s is entered for the longitudinal emittance of the distribution. The code will recommend a voltage to capture the unbunched protons into 4 harmonic 1440 buckets. A capture voltage of 142.390 kV is recommended. 144.0 kV is entered. It is desirable to capture the protons as “adiabatically” as possible. A capture time of 3318 ms is recommended by the code. 3320.0 ms is entered. A 4 to 2 merge time of 1659 ms is recommended by the code. 1660.0 ms is entered. A 2 to 1 merge time twice that of the 4 to 2 merge is recommended by the code. 3320.0 ms is entered. The code requests a “time fraction” FQMRG to be entered. This is a number (from 0.1 to 1.0) that determines the time at which data are recorded during the 4 to 2 merge. The number 0.5 is entered. This encodes the recording of data halfway through the 4 to 2 merge.
Following are examples of a 4 to 2 to 1 merge of proton bunches in AGS obtained by running the simulation code ags2mrg23. As the code runs, the user is prompted to enter several numbers. For these examples, RF harmonic number 12.0 is entered. An RF frequency of 4.453 913 448 73 MHz at this harmonic is entered. This gives proton G γ = 45.5. The merge simulation starts with a uniform distribution of unbunched protons. 2.0 eV-s is entered for the longitudinal emittance of the distribution. The code will recommend a voltage to capture the unbunched protons into 4 harmonic 12 buckets. A capture voltage of 0.0527 kV is recommended. 0.053 kV is entered. It is desirable to capture the protons as “adiabatically” as possible. Because of the long synchrotron period (372 ms), a capture time of 74,707 ms is recommended by the code. A shorter time, 10,000 ms, is entered to reduce the running time of the code. A 4 to 2 merge time of 37,353 ms is recommended by the code. 4000.0 ms is entered. A 2 to 1 merge time twice that of the 4 to 2 merge is recommended by the code. 8000.0 ms is entered. The code requests a “time fraction” FQMRG to be entered. This is a number (from 0.1 to 1.0) that determines the time at which data are recorded during the 4 to 2 merge. The number 0.5 is entered. This encodes the recording of data halfway through the 4 to 2 merge.
Aerosol Light Absorption at 532 nm using Photothermal Interferometry Time resolution: 10 sec Data normalized to STP Location: Memphis (TN) or Pasco (WA) Calibration: NO2 DateTime_PTI: UTC Absorption coefficient (PTI): Mm-1 Comments or requests are to be directed to Art Sedlacek (sedlacek@bnl.gov)
A functional description of the new LANDSAT-4 World Reference System (WRS) with an overview of the main orbital parameters and instrument coverages is presented to provide the data user with the primary information required to understand LANDSAT-4 orbital characteristics, to effectively use the WRS indexing scheme, and to request specific geographic coverage on the desired observation dates.
This report presents the results of maneuverability tests of an O3U-1 observation airplane. This investigation is the third in a series of similar investigations requested by the Bureau of Aeronautics (Navy) for the purpose of comparing the maneuverability of different airplane types and to provide quantitative data for use in establishing a criterion or method for rating the maneuverability of an airplane. The two former investigations were conducted with the fighter types designated F6C-3 and F6C-4 and have been reported previously. Measurement of the air speed, the angular velocity, the linear acceleration, and positions of the controls were made during abrupt single-control maneuvers with three stop positions for each control, during steady horizontal turns for the determination of minimum radius, and during 180 degree turns by various methods. Flight-path coordinates in two dimensions were determined for the 180 degree turns by means of a special camera obscura designed for the previous investigation of the F6C-4 airplane. All maneuvers were performed at an altitude of approximately 3,000 feet.
The migration of the Project Integration Architecture (PIA) to the distributed object environment of the Common Object Request Broker Architecture (CORBA) brings with it the nearly unavoidable requirements of multiaccessor, asynchronous operations. In order to maintain the integrity of data structures in such an environment, it is necessary to provide a locking mechanism capable of protecting the complex operations typical of the PIA architecture. This paper reports on the implementation of a locking mechanism to treat that need. Additionally, the ancillary features necessary to make the distributed lock mechanism work are discussed.
The Kepler Mission is designed to survey our region of the Milky Way galaxy to discover hundreds of Earth-sized and smaller planets in or near the habitable zone. The Kepler photometer is an array of 42 CCDs (charge-coupled devices) in the focal plane of a 95-cm Schmidt camera onboard the Kepler spacecraft. Each 50x25-mm CCD has 2,200 x 1,024 pixels. The CCDs accumulate photons and are read out every six seconds to prevent saturation. The data is integrated for 30 minutes, and then the pixel data is transferred to onboard storage. The data is subsequently encoded and transmitted to the ground. During End-to-End Information System (EEIS) testing of the Kepler Mission System (KMS), there was a need to verify that the pixels requested by the science team operationally were correctly collected, encoded, compressed, stored, and transmitted by the FS, and subsequently received, decoded, uncompressed, and displayed by the Ground Segment (GS) without the outputs of any CCD modules being flipped, mirrored, or otherwise corrupted during the extensive FS and GS processing. This would normally be done by projecting an image on the focal plane array (FPA), collecting the data in a flight-like way, and making a comparison between the original data and the data reconstructed by the science data system. Projecting a focused image onto the FPA through the telescope would normally involve using a collimator suspended over the telescope opening. There were several problems with this approach: the collimation equipment is elaborate and expensive; as conceived, it could only illuminate a limited section of the FPA (.25 percent) during a given test; the telescope cover would have to be deployed during testing to allow the image to be projected into the telescope; the equipment was bulky and difficult to situate in temperature-controlled environments; and given all the above, test setup, execution, and repeatability were significant concerns. Instead of using this complicated approach of projecting an optical image on the FPA, the Kepler project developed a method using known defect features in the CCDs to verify proper collection and reassembly of the pixels, thereby avoiding the costs and risks of the optical projection approach. The CCDs composing the Kepler FPA, as all CCDs, had minor defects. At ambient temperature, some pixels look far brighter than they should. These ghot h pixels have a higher rate of charge leakage than the others due to manufacturing variations. They are usually stable over time, and appear at temperatures above 5 oC. The hot pixels on the Kepler FPA were mapped before photometer assembly during module testing. Selected hot pixels were used as target gstars h for the purposes of EEIS testing. gDead h pixels are permanently off, producing a permanently black pixel. These can also be used if there is some illumination of the FPA. During EEIS testing, Dark Current Full Frame Images (FFIs) taken at room temperature were used to create the hot pixel maps for all 84 Kepler photometer CCD channels. Data from two separate nights were used to create two hot pixel maps per channel, which were cross-correlated to remove cosmic ray events which appear to be hot pixels. These hot pixel maps obtained during EEIS testing were compared to the maps made during module testing to verify that the end-to-end data flow was correct.