Search NASA⌕ Search

SEARCH · Search NASA

Results for “base editing”

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 253 records · Page 14

Software for Better Documentation of Other Software

The Literate Programming Extraction Engine is a Practical Extraction and Reporting Language- (PERL-)based computer program that facilitates and simplifies the implementation of a concept of self-documented literate programming in a fashion tailored to the typical needs of scientists. The advantage for the programmer is that documentation and source code are written side-by-side in the same file, reducing the likelihood that the documentation will be inconsistent with the code and improving the verification that the code performs its intended functions. The advantage for the user is the knowledge that the documentation matches the software because they come from the same file. This program unifies the documentation process for a variety of programming languages, including C, C++, and several versions of FORTRAN. This program can process the documentation in any markup language, and incorporates the LaTeX typesetting software. The program includes sample Makefile scripts for automating both the code-compilation (when appropriate) and documentation-generation processes into a single command-line statement. Also included are macro instructions for the Emacs display-editor software, making it easy for a programmer to toggle between editing in a code or a documentation mode.

Pinedo, John↗

NASA-STD-7012 Leak Test Requirements: Potential Reference for ASNT Nondestructive Testing Handbook for Leak Testing

Developed in 2018-2019, NASA-STD-7012 Leak Test Requirements, has been drafted based mostly on the NASA technical requirement documents applicable to the International Space Station (ISS) hardware and payloads that were developed over the years taking into consideration many known references such as Leakage Testing Handbook prepared by General Electric for the Jet Propulsion Laboratory, the ASTM International standards for leak testing, and last, but not least, the ASNT Nondestructive Testing Handbook for Leak Testing. Thus, NASA-STD-7012 has a reference to the above-mentioned handbook in the leak test method/technique descriptions. However, there are some technical details that are described differently in NASA standard and ASNT Handbook. Those technical details are mostly related to the classification of the leak test methods/techniques, and also to tracer gas to working fluid (gas or liquid) leakage rate conversion methodology, and to some definitions used in the text of both NASA standard and ASNT Handbook. Those differences are going to be briefly described in this paper to let ASNT leak test experts decide if they want to refer to NASA-STD-7012 while working on the next edition of the ASNT Handbook, Volume 2 for Leak Testing.

Lvovsky, Oleg M.↗

The HITRAN2016 Molecular Spectroscopic Database

This paper describes the contents of the 2016 edition of the HITRAN molecular spectroscopic compilation. The new edition replaces the previous HITRAN edition of 2012 and its updates during the intervening years. The HITRAN molecular absorption compilation is composed of five major components: the traditional line-by-line spectroscopic parameters required for high-resolution radiative-transfer codes, infrared absorption cross-sections for molecules not yet amenable to representation in a line-by-line form, collision-induced absorption data, aerosol indices of refraction, and general tables such as partition sums that apply globally to the data. The new HITRAN is greatly extended in terms of accuracy, spectral coverage, additional absorption phenomena, added line-shape formalisms, and validity. Moreover, molecules, isotopologues, and perturbing gases have been added that address the issues of atmospheres beyond the Earth. Of considerable note, experimental IR cross-sections for almost 300 additional molecules important in different areas of atmospheric science have been added to the database. The compilation can be accessed through www.hitran.org. Most of the HITRAN data have now been cast into an underlying relational database structure that offers many advantages over the long-standing sequential text-based structure. The new structure empowers the user in many ways. It enables the incorporation of an extended set of fundamental parameters per transition, sophisticated line-shape formalisms, easy user-defined output formats, and very convenient searching, filtering, and plotting of data. A powerful application programming interface making use of structured query language (SQL) features for higher-level applications of HITRAN is also provided.

HITRAN↗

Multidecadal Changes in Near-Global Cloud Cover and Estimated Cloud Cover Radiative Forcing

The first paper was Multidecadal changes in near-global cloud cover and estimated cloud cover radiative forcing, by J. R. Norris (2005, J. Geophys. Res. - Atmos., 110, D08206, doi: lO.l029/2004JD005600). This study examined variability in zonal mean surface-observed upper-level (combined midlevel and high-level) and low-level cloud cover over land during 1971-1 996 and over ocean during 1952-1997. These data were averaged from individual synoptic reports in the Extended Edited Cloud Report Archive (EECRA). Although substantial interdecadal variability is present in the time series, long-term decreases in upper-level cloud cover occur over land and ocean at low and middle latitudes in both hemispheres. Near-global upper-level cloud cover declined by 1.5%-sky-cover over land between 1971 and 1996 and by 1.3%-sky-cover over ocean between 1952 and 1997. Consistency between EECRA upper-level cloud cover anomalies and those from the International Satellite Cloud Climatology Project (ISCCP) during 1984-1 997 suggests the surface-observed trends are real. The reduction in surface-observed upper-level cloud cover between the 1980s and 1990s is also consistent with the decadal increase in all-sky outgoing longwave radiation reported by the Earth Radiation Budget Satellite (EMS). Discrepancies occur between time series of EECRA and ISCCP low-level cloud cover due to identified and probable artifacts in satellite and surface cloud data. Radiative effects of surface-observed cloud cover anomalies, called "cloud cover radiative forcing (CCRF) anomalies," are estimated based on a linear relationship to climatological cloud radiative forcing per unit cloud cover. Zonal mean estimated longwave CCRF has decreased over most of the globe. Estimated shortwave CCRF has become slightly stronger over northern midlatitude oceans and slightly weaker over northern midlatitude land areas. A long-term decline in the magnitude of estimated shortwave CCRF occurs over low-latitude land and ocean, but comparison with EMS all-sky reflected shortwave radiation during 1985-1997 suggests this decrease may be underestimated.

Norris, Joel↗

Large Solar-Rejection Filter

NASA utilized Image Intensified Video Cameras for ATV data acquisition from a jet flying at 12.8 km. Afterwards the video was digitized and then analyzed with a modified commercial software package, Image Systems Trackeye. Astrometric results were limited by saturation, plate scale, and imposed linear plate solution based on field reference stars. Time-dependent fragment angular trajectories, velocities, accelerations, and luminosities were derived in each video segment. It was evident that individual fragments behave differently. Photometric accuracy was insufficient to confidently assess correlations between luminosity and fragment spatial behavior (velocity, deceleration). Use of high resolution digital video cameras in future should remedy this shortcoming. A scenically accurate description of matter interpreted as a substance made up of corpuscular constituents was established during the course of the 19th century. In this description, atoms--the building blocks of the matter--form molecules. The properties of the molecules were described by chemistry or thermodynamics depending on what characteristics of the matter were investigated. In both theories, the molecules can dissociate to atoms when the kinetic energies of the atoms exceed the strength of the chemical bonds. The number of atoms is always preserved in a closed system. This is not true, however, when the matter takes up much higher energies at relativistic scales. New particles can be produced at the expense of the kinetic energy. The number of particles is no longer preserved. There are other conserved quantities, however, these quantities, the charge, baryon number, lepton number, are associated with particles that are considered elementary today. The properties and behavior of these elementary particles is the subject of Particle Physics or High Energy Physics. Practice Page: A crewmember touching a positively charged surface was thought to be galvanically isolated from the vehicle ground analogous to a bird on a high voltage power wire. Recent analysis confirms that positive floating potentials, ionospheric currents to the EVA suit, can be hazardous. The analysis is wrong in that the ionospheric plasma itself can close the circuit. Parametric analysis of very low voltage exposures (2 to 15 volts) could cause pain and/or involuntary muscle tetani or spinal cord shock. NASA worked with the Naval Health Research Center Detachment Directed Energy Bioeffects Laboratory to examine the affects electrical hazards could have on extravehicular activity using two models. The results of the two computational models were combined to predict areas of the body in which neurons of different diameters would be excited. They predicted that physiologically active current could be conducted across the crew member causing catastrophic hazards. Future work to analyze additional current paths was proposed. The FUSE spectrum of BB Dor, observed in a high state, is modeled with an accretion disk with a very low inclination (possibly lower than 10 degrees). Assuming an average WD mass of 0.8 solar mass leads to a distance of the order of approximately 650pc, consistent with the extremely low galactic reddening in its direction, and a mass accretion rate of 10 (exp -9) solar mass a year. The spectrum presents some broad and deep silicon and sulfur absorption lines, indicating that these elements are over-abundant: silicon is 3 times solar, and sulfur is 20 times solar. The FUSE spectrum of BB Dor, observed in a high state, is modeled with an accretion disk with a very low inclination (possibly lower than 10 degrees). Assuming an average WD mass of 0.8 solar mass leads to a distance of the order of approximately 650pc, consistent with the extremely low galactic reddening in its direction, and a mass accretion rate of 10 (exp -9) solar mass a year. The spectrum presents some broad and deep silicon and sulfur absorption lines, indicating that these elements are over-abundant: silicon is times solar, and sulfur is 20 times solar. From its previously observed optical emission lines, P831-57 (WD 0334 6400 or Ret 1 in A Catalog and Atlas of Cataclysmic Variables: Living Edition) has been suspected to contain an accretion disk associated with a companion star in orbit around a subdwarf star with a temperature T is greater than 21,000K. P831-57 has therefore been classified as a nova-like. However, our present observations show it to be a DA + dMe binary. The analysis of its Far Ultraviolet Spectroscopic Explorer (FUSE) spectrum (continuum and lines) reveal an average mass white dwarf (Log(g) approximately equals 7.8 plus or minus 0.1)with a temperature T approximately equals 37,000 plus or minus 500K, an extremely low projected rotational velocity, and a distance of about 115 plus or minus 5pc. The photosphere contains C, N, Si, and S (at about 1% of solar abundances). The dMe star is seen as a flux excess in near-infrared photometry and appears to show occasional flaring of about one magnitude as seen in the Harvard plates. There is no evidence of periodic variability in the spectroscopic or photometric data. We find no evidence of a an accretion disk, instead we find evidence of wind accretion as the stellar carbon abundance (N(C)/N(H) = 2.5 x 10 (exp -6) is about ten times larger than predicted by radiative levitation for such a gravity and temperature. The power needs and solutions for the space exploration and lunar mobility program are discussed. Long term missions in space and on the lunar surface require high energy batteries. Rechargeable batteries for mobility systems and portable utility pallet are needed for successful exploration missions. Nanomaterial usage increases the energy density of the cells apart from increasing the power density. The symptoms and threats from acute mountain sickness (AMS) are discussed. The underlying assumptions concerning spacecraft atmosphere mean there is a potential risk to astronauts. The baseline worst case scenario is about 25% based on direct ascent to 8.0 psia with 32% O2. The practical mitigation approach is a staged depressurization scheme. Due to the uncertainty about potential AMS risk the flight surgeon should prepare, focused research should proceed, and current analytical efforts should continue. This slide presentation reviews the threat astronauts face from acute mountain sickness (AMS). The incidence of AMS is highly variable and the risk to astronauts is unclear. However, the potential risk is higher than current EAAs suggest and precautions should be implemented. Due to the uncertain nature of the risk flight surgeons should prepare, and focused research should proceed. Quasiparticle tunneling can be understood at low temperatures using a non-equilibrium kinetic theory. Low-temperature tunneling can be suppressed using existing techniques: island-lead gap engineering, lead cooling with SIN junctions, and quasiparticle traps. The slide presentation reviews the science goals and mission planning for the proposed Jupiter System Observer (JSO). The spacecraft would accommodate 9 instruments making the instrument payload more capable than any previously flown to Jupiter. The would-be mission includes study programs for Jupiter's satellites, interior, magnetosphere and atmosphere. The power needs and solutions for the space exploration and lunar mobility program are discussed. Long term missions in space and on the lunar surface require high energy batteries. Rechargeable batteries for mobility systems and portable utility pallet are needed for successful exploration missions. Nanomaterial usage increases the energy density of the cells apart from increasing the power density. This slide presentation reviews the power requirements for the space exploration and the lunar surface mobility programs. It includes information about the specifications for high energy batteries and the power requirements for lunar rovers,

Roberts, William↗

Fuzzy/Neural Software Estimates Costs of Rocket-Engine Tests

The Highly Accurate Cost Estimating Model (HACEM) is a software system for estimating the costs of testing rocket engines and components at Stennis Space Center. HACEM is built on a foundation of adaptive-network-based fuzzy inference systems (ANFIS) a hybrid software concept that combines the adaptive capabilities of neural networks with the ease of development and additional benefits of fuzzy-logic-based systems. In ANFIS, fuzzy inference systems are trained by use of neural networks. HACEM includes selectable subsystems that utilize various numbers and types of inputs, various numbers of fuzzy membership functions, and various input-preprocessing techniques. The inputs to HACEM are parameters of specific tests or series of tests. These parameters include test type (component or engine test), number and duration of tests, and thrust level(s) (in the case of engine tests). The ANFIS in HACEM are trained by use of sets of these parameters, along with costs of past tests. Thereafter, the user feeds HACEM a simple input text file that contains the parameters of a planned test or series of tests, the user selects the desired HACEM subsystem, and the subsystem processes the parameters into an estimate of cost(s).

Douglas, Freddie↗

Modeling Guidelines for Code Generation in the Railway Signaling Context

Modeling guidelines constitute one of the fundamental cornerstones for Model Based Development. Their relevance is essential when dealing with code generation in the safety-critical domain. This article presents the experience of a railway signaling systems manufacturer on this issue. Introduction of Model-Based Development (MBD) and code generation in the industrial safety-critical sector created a crucial paradigm shift in the development process of dependable systems. While traditional software development focuses on the code, with MBD practices the focus shifts to model abstractions. The change has fundamental implications for safety-critical systems, which still need to guarantee a high degree of confidence also at code level. Usage of the Simulink/Stateflow platform for modeling, which is a de facto standard in control software development, does not ensure by itself production of high-quality dependable code. This issue has been addressed by companies through the definition of modeling rules imposing restrictions on the usage of design tools components, in order to enable production of qualified code. The MAAB Control Algorithm Modeling Guidelines (MathWorks Automotive Advisory Board)[3] is a well established set of publicly available rules for modeling with Simulink/Stateflow. This set of recommendations has been developed by a group of OEMs and suppliers of the automotive sector with the objective of enforcing and easing the usage of the MathWorks tools within the automotive industry. The guidelines have been published in 2001 and afterwords revisited in 2007 in order to integrate some additional rules developed by the Japanese division of MAAB [5]. The scope of the current edition of the guidelines ranges from model maintainability and readability to code generation issues. The rules are conceived as a reference baseline and therefore they need to be tailored to comply with the characteristics of each industrial context. Customization of these recommendations has been performed for the automotive control systems domain in order to enforce code generation [7]. The MAAB guidelines have been found profitable also in the aerospace/avionics sector [1] and they have been adopted by the MathWorks Aerospace Leadership Council (MALC). General Electric Transportation Systems (GETS) is a well known railway signaling systems manufacturer leading in Automatic Train Protection (ATP) systems technology. Inside an effort of adopting formal methods within its own development process, GETS decided to introduce system modeling by means of the MathWorks tools [2], and in 2008 chose to move to code generation. This article reports the experience performed by GETS in developing its own modeling standard through customizing the MAAB rules for the railway signaling domain and shows the result of this experience with a successful product development story.

Ferrari, Alessio↗

Behavior of Spinning Space Vehicles with Onboard Liquids, 2nd Edition, Technical Report B8030

Although the fundamental principles of spin stabilization are well established, uncertainty regarding the potential for rapid nutation growth caused by onboard liquids is a continuing concern. NASA and other organizations regularly encounter the issue of rapid nutation growth due to energy dissipation by liquids on spinning vehicles. Of concern is the stability of spinning upper stages and of spacecraft that spin for part or all of their missions. Several missions have required last-minute hardware or operational changes to deal with rapid nutation divergences that were identified late in the program. In some instances, major schedule slips were barely averted. In at least two cases, it was determined that a spinning upper stage was not a viable option. Historically, the "slosh" issue has been addressed by each space vehicle project individually, if it has been addressed at all. Due to budgetary and programmatic constraints, individual projects are unable to address the problem globally. Hence, there has been little effort to collect available test and flight data and use that data to make a coherent, unified picture of the "slosh" effect and how to deal with it. To some extent, each project has had to "reinvent the wheel", which can be both costly and risky. This study is a step toward correcting the situation. Specifically, the goal was to identify and collect available flight and test data for spinning vehicles with onboard liquid propellants. A total of 149 flight data points and 1,692 test points were collected as part of this study. This data was analyzed, correlated, and is presented here in a normalized form. In most cases, the normalization involves a dimensionless nutation time constant that can be used to predict performance of other vehicles with the same type of tank. For some configurations, it was also possible to identify conditions that can lead to resonance between nutational motion and liquid modes. Gaps in the knowledge base are identified and approaches to filling those gaps are outlined. The data presented here has two different but related uses. First, it can be applied directly to current and future spacecraft programs. Second, it can provide truth models for testing analytical techniques. Experience has shown that purely analytical models of the liquid "slosh" effect on spinning vehicles are unreliable unless they are validated against flight or test data. To the author's knowledge, this report contains the most extensive and varied data set available. As such, it should be a good resource for anyone seeking to develop and validate improved analytical techniques. All of the original digital data sets have been archived on disk, with copies provided to NASA/KSC. With some restrictions, many of these data sets can be made available to researchers within the United States. Whenever possible, spacecraft are identified by name in this report. However, several organizations provided access to data with the explicit proviso that their programs not be identified and that parameters be presented only in normalized form. These constraints have been respected.

Hubert, Carl↗

Enhancement of the Earth Science and Remote Sensing Group's Website and Related Projects

The major problem addressed throughout the term was the need to update the group's current website, as it was outdated and required streamlining and modernization. The old Gateway to Astronaut Photography of the Earth website had multiple components, many of which involved searches through expansive databases. The amount of work required to update the website was large and due to a desired release date, assistance was needed to help build new pages and to transfer old information. Additionally, one of the tools listed on the website called Image Detective had been underutilized in the past. It was important to address why the public was not using the tool and how it could potentially become more of a resource for the team. In order to help with updating the website, it was necessary to first learn HTML. After assisting with small edits, I began creating new pages. I utilized the "view page source" and "developer" tools in the internet browser to observe how other websites created their features and to test changes without editing the code. I then edited the code to create an interactive feature on the new page. For the Image Detective Page I began an evaluation of the current page. I also asked my fellow interns and friends at my University to offer their input. I took all of the opinions into account and wrote up a document regarding my recommendations. The recommendations will be considered as I help to improve the Image Detective page for the updated website. In addition to the website, other projects included the need for additional, and updated image collections, along with various project requests. The image collections have been used by educators in the classroom and the impact crater collection was highly requested. The glaciers collection focused mostly on South American glaciers and needed to include more of the earth's many glaciers. The collections had not been updated or created due to the fact that related imagery had not been catalogued. The process of cataloging involves identifying the center point location of the image and feature identification. Other project needs included collecting night images of India in for publishing. Again, many of the images were not catalogued and the database was lacking in night time imagery for that region. The last project was to calculate the size of mega fans in South Africa. Calculating the fan sizes involved several steps. To expedite the study, calculations needed to be made after the base maps had been created. Using data files that included an outline of the mega fans on a topographic map, I opened the file in Photoshop, determined the number of pixels within the outlined area, created a one degree squared box, determined the pixels within the box, converted the pixels within the box to kilometers, and then calculated the fan size using this information. Overall, the internship has been a learning experience for me. I have learned how to use new programs and I developed new skills. These These skills can help me as I enter into the next phase of my career. Learning Photoshop and HTML in addition to coding in Dreamweaver are highly sought after skills that are used in a variety of fields. Additionally, the exposure to different aspects of the team and working with different people helped me to gain a broader set of skills and allowed me to work with people with different experiences. The various projects I have worked on this summer have directly benefitted the team whether it was completing projects they did not have the time to do, or by helping the team reach deadlines sooner. The new website will be the best place to see all of my work as it will include the newly designed pages and will feature my updates to collections.

Coffin, Ashley↗

Java-based Graphical User Interface for MAVERIC-II

A computer program entitled "Marshall Aerospace Vehicle Representation in C II, (MAVERIC-II)" is a vehicle flight simulation program written primarily in the C programming language. It is written by James W. McCarter at NASA/Marshall Space Flight Center. The goal of the MAVERIC-II development effort is to provide a simulation tool that facilitates the rapid development of high-fidelity flight simulations for launch, orbital, and reentry vehicles of any user-defined configuration for all phases of flight. MAVERIC-II has been found invaluable in performing flight simulations for various Space Transportation Systems. The flexibility provided by MAVERIC-II has allowed several different launch vehicles, including the Saturn V, a Space Launch Initiative Two-Stage-to-Orbit concept and a Shuttle-derived launch vehicle, to be simulated during ascent and portions of on-orbit flight in an extremely efficient manner. It was found that MAVERIC-II provided the high fidelity vehicle and flight environment models as well as the program modularity to allow efficient integration, modification and testing of advanced guidance and control algorithms. In addition to serving as an analysis tool for techno logy development, many researchers have found MAVERIC-II to be an efficient, powerful analysis tool that evaluates guidance, navigation, and control designs, vehicle robustness, and requirements. MAVERIC-II is currently designed to execute in a UNIX environment. The input to the program is composed of three segments: 1) the vehicle models such as propulsion, aerodynamics, and guidance, navigation, and control 2) the environment models such as atmosphere and gravity, and 3) a simulation framework which is responsible for executing the vehicle and environment models and propagating the vehicle s states forward in time and handling user input/output. MAVERIC users prepare data files for the above models and run the simulation program. They can see the output on screen and/or store in files and examine the output data later. Users can also view the output stored in output files by calling a plotting program such as gnuplot. A typical scenario of the use of MAVERIC consists of three-steps; editing existing input data files, running MAVERIC, and plotting output results.

Seo, Suk Jai↗

High Level Architecture Distributed Space System Simulation for Simulation Interoperability Standards Organization Simulation Smackdown

Modeling and Simulation plays a very important role in mission design. It not only reduces design cost, but also prepares astronauts for their mission tasks. The SISO Smackdown is a simulation event that facilitates modeling and simulation in academia. The scenario of this year s Smackdown was to simulate a lunar base supply mission. The mission objective was to transfer Earth supply cargo to a lunar base supply depot and retrieve He-3 to take back to Earth. Federates for this scenario include the environment federate, Earth-Moon transfer vehicle, lunar shuttle, lunar rover, supply depot, mobile ISRU plant, exploratory hopper, and communication satellite. These federates were built by teams from all around the world, including teams from MIT, JSC, University of Alabama in Huntsville, University of Bordeaux from France, and University of Genoa from Italy. This paper focuses on the lunar shuttle federate, which was programmed by the USRP intern team from NASA JSC. The shuttle was responsible for provide transportation between lunar orbit and the lunar surface. The lunar shuttle federate was built using the NASA standard simulation package called Trick, and it was extended with HLA functions using TrickHLA. HLA functions of the lunar shuttle federate include sending and receiving interaction, publishing and subscribing attributes, and packing and unpacking fixed record data. The dynamics model of the lunar shuttle was modeled with three degrees of freedom, and the state propagation was obeying the law of two body dynamics. The descending trajectory of the lunar shuttle was designed by first defining a unique descending orbit in 2D space, and then defining a unique orbit in 3D space with the assumption of a non-rotating moon. Finally this assumption was taken away to define the initial position of the lunar shuttle so that it will start descending a second after it joins the execution. VPN software from SonicWall was used to connect federates with RTI during testing and the Smackdown event. HLA software from Pitch Technology and MAK Technology were used to edit and extend FOM and provide HLA services for federation execution. The SISO Smackdown event for 2011 was held in Boston, Massachusetts. The federation execution lasted for one hour, and the event was very successful in catching the attention of university students and faculties.

Li, Zuqun↗

Early differentiation of the Moon: Experimental and modeling studies and experimental and modeling studies of massif anorthosites

NASA grant NAG9-329 was in effect from 3/1/89 to 8/31/94, the last 18 months being a no-cost extension. While the grant was in effect, the P.I., coworkers, and students gave 22 talks and poster sessions at professional meetings, published 12 articles in referred journals (one more is in press, and another is in review), and edited 2 workshop reports relevant to this project. Copies of all the publications are appended to this report. The major accomplishments during the grant period have derived from three quarters: 1) the application of quantitative models of fractional crystallization and partial melting to various problems in planetary science, such as the petrogenesis of picritic glasses and mare basalts and the implications of the SNC meteorites for martian evolution; 2) an experimental study of silicate liquid immiscibility relevant to early lunar differentiation and the petrogenesis of evolved highlands rocks; and 3) experimental studies of massif anorthosites and related rocks that provide terrestrial analogs for the proposed origin of lunar anorthosites by multistage processes. The low-pressure aspects of the quantitative models were developed by the P.I. in the 1980s with NASA support and culminated with a paper comparing the crystallization of terrestrial and lunar lavas. The basis for the high-pressure modifications to the quantitative models is a data set gleaned from high pressure melting experiments done at Lamont and is supplemented by published data from other labs that constrain the baric and compositional dependences of various liquidus phase boundaries such as olivine/orthopyroxene, relevant to the melting of the mantles of the terrestrial planets. With these models it is possible to predict not only the thermal and compositional evolution of magmatic liquids ranging in composition from lumar mare basalt to terrestrial calc-alkaline basalts, but also the small increments of fractional melting that are produced when mantle rises adiabatically. Copies of the crystallization/melting programs have been given to several colleagues in planetary science. Additionally, a series of computer graphics programs, based on the algorithms in the crystallization programs have been developed that display liquidus diagrams appropriate to input compositions.

Longhi, John↗

Analysis of Near Simultaneous Jimsphere and AMPS High Resolution Wind Profiles

The high-resolution wind profile of the Automated Meteorological Profiling System (HRAMPS) is the proposed replacement for the Jimsphere measurement system used to support NASA Shuttle launches from the Eastern Test Range (ETR). Samples of twenty-six ETR near simultaneous Jimsphere and HRAMPS wind profiles were obtained for Shuttle program HRAMPS certification studies. Shuttle systems engineering certification is to ensure that spacecraft and launch vehicle systems performance and safety evaluations for each launch (derived from flight simulations with Jimsphere wind profile data bases) retain their validity when HRAMPS profiles are used on day-of-launch (DOL) in trajectory and loads simulations to support the commit-to-launch decision. This paper describes a statistical analysis of the near simultaneous profiles. In principle the differences between a Jimsphere profile and an HRAMPS profile should be attributed to tracking technology (radar versus GPS tracking of a Jimsphere flight element) and the method for derivation of wind vectors from the raw tracking data. In reality, it is not technically feasible to track the same Jimsphere balloon with the two systems. The aluminized Mylar surface of the standard Jimsphere flight element facilitates radar tracking, but it interferes with HRAMPS during simultaneous tracking. Suspending a radar reflector from an HRAMPS flight element (Jimsphere without aluminized coating) does not produce satisfactory Jimsphere profiles because of intermittent radar returns. Thus, differences between the Jimsphere and HRAMPS profiles are also attributed to differences in the trajectories of separate flight elements. Because of small sample size and a test period limited to one winter season, test measurements during extreme high winds aloft could not have been expected and did not occur. It is during the highest winds that the largest differences between Jimsphere and HRAMPS would occur because the distance between flight elements would be larger. Jimsphere radar tracking noise increases as a function of balloon displacement downrange. The Jimsphere data processing compensates for tracking signal/noise degradation by increasing the smoothing interval. The Jimsphere wind profile effective resolution is a function of downrange distance and altitude, whereas the effective resolution of the HRAMPS should be independent of those variables. The procedure used for editing Jimsphere spikes in Shuttle DOL profiles was not implemented for the Jimsphere profile measurements during the AMPS field tests. For this analysis a code was developed that essentially mimics DOL Jimsphere spike editing. Jimsphere profiles have somewhat more noise in the wavelength range less than 200m defined as the noise floor. No differences between Jimsphere and HRAMPS wind profile pairs have been found that would support denial of HRAMPS certification for application in Shuttle DOL applications. The reliability of the HRAMPS system, which is an important certification issue, is not addressed in this study.

Adelfang, S. I.↗

Seasonal Surface Spectral Emissivity Derived from VIIRS Data

Surface emissivity is essential for many remote-sensing applications including the retrieval of surface skin temperature from satellite-based infrared measurements, the determination of cloud detection thresholds, and the estimation of the surface longwave radiation emission, an important component of the energy budget of the surface-atmosphere interface. The CERES (Clouds and the Earth’s Radiant Energy System) Project is measuring broadband shortwave and longwave radiances and deriving cloud properties from the MODIS on Terra and Aqua and from the VIIRS on NOAA-19 and NOAA-20 orbiters to produce combined global radiation and cloud property data sets. Zhou et al. (IEEE Trans. Geosci. Remote Sens., 49, 2011) used Infrared Atmospheric Sounding Interferometer (IASI) data to create a high spectral resolution surface emissivity atlas for remote sensing and modeling applications. The IASI measures spectral radiances between 3.62 and 15.5 µm. The VIIRS I4 channel width is from 3.55 to 3.93 µm, while MODIS Band 20 is from 3.66 to 3.84 µm. Comparisons of top-of-atmosphere (TOA) radiance calculations with MODIS and VIIRS observations for these bands suggest that the IASI emissivity atlas near 3.7 µm may not be suitable for CERES cloud retrievals. In this paper, the IASI emissivities for the VIIRS and MODIS bands centered near 11µm are used to derive surface skin temperature from nighttime MODIS/VIIRS data. The Goddard Earth Observing System for Instrument Teams (GEOS-IT) numerical weather analyses provide temperature and water vapor profiles fused to correct the observed radiances for atmospheric absorption and emission. Global seasonal emissivity maps are then derived for the VIIRS and MODIS 3.7µm bands that are consistent with the derived skin temperatures and the observed TOA radiances. These seasonal climatology maps will be validated and used in CERES Edition 5 and other CERES-related cloud retrieval algorithms to provide improved clear-sky radiances and derived cloud properties.

Surface Emissivity↗

Seasonal Surface Spectral Emissivity Derived From MODIS Data

Surface emissivity is essential for many remote-sensing applications including the retrieval of surface skin temperature from satellite-based infrared measurements, the determination of cloud detection thresholds, and the estimation of the surface longwave radiation emission, an important component of the energy budget of the surface-atmosphere interface. The CERES (Clouds and the Earth’s Radiant Energy System) Project is measuring broadband shortwave and longwave radiances and deriving cloud properties from the MODIS on Terra and Aqua and from the VIIRS on NOAA-19 and NOAA-20 orbiters to produce combined global radiation and cloud property data sets. Zhou et al. (IEEE Trans. Geosci. Remote Sens., 49, 2011) used Infrared Atmospheric Sounding Interferometer (IASI) data to create a high spectral resolution surface emissivity atlas for remote sensing and modeling applications. The IASI measures spectral radiances between 3.62 and 15.5 μm. The VIIRS I4 channel width is from 3.55 to 3.93 μm, while MODIS Band 20 is from 3.66 to 3.84 m. Comparisons of top-of-atmosphere (TOA) radiance calculations with MODIS and VIIRS observations for these bands relative to bands in the mid-infrared suggest that the IASI emissivity atlas near 3.7 µm may not be suitable for CERES cloud retrievals. In this paper, the IASI emissivities for the VIIRS and MODIS bands centered near 11m are used to derive surface skin temperature from nighttime MODIS/VIIRS data. The Goddard Earth Observing System for Instrument Teams (GEOS-IT) numerical weather analyses provide temperature and water vapor profiles fused to correct the observed radiances for atmospheric absorption and emission. Global seasonal emissivity maps are then derived for the VIIRS and MODIS 3.7-m bands that are consistent with the derived skin temperatures and the observed TOA radiances. These seasonal climatology maps are validated and will be used in CERES Edition 5 and other CERES-related cloud retrieval algorithms to provide improved clear-sky radiances and derived cloud properties.

Surface Emissivity↗

LunaNet Position, Navigation, and Timing Services and Signal, Enabling the Future of Lunar Exploration

The International Space Exploration Coordination Group established in 2018 the 3rd edition of the Global Exploration Roadmap (ISECG, 2018) that aims to achieve Mars human surface activities and identifies the exploration of the Moon as a critical intermediate step. A supplement covering updates on surface exploration scenarios was released in 2020 (ISECG, 2020). The Artemis Accords (NASA Artemis, 2020), first signed in October 2020, now includes over two dozen nations, in an agreement on the principles for best practices, including interoperability. September 2022 introduced the National Aeronautics and Space Administration’s (NASA) Moon to Mars Objectives highlighting recurring tenets of collaboration with international and industry partners and interoperability, along with infrastructure objectives for Position, Navigation, and Timing (PNT). The successful Artemis 1 mission paved the way to the ambitious plans to establish a sustainable human presence on the Moon. Just a few months after Artemis 1 launch (NASA, 2022), iSpace HAKUTO-R Mission1 (iSpace, 2022) launched, being the first-ever commercial mission, launched by a commercial launch service provider, aiming to land on the lunar surface. The NASA Artemis programme plans initial crewed landings and traverses in 2025, supported by the Lunar Gateway, followed by regular launches to build the lunar systems (NASA Artemis Plan, 2020), (NASA, 2022). NASA’s contracts with Commercial Lunar Payload Services (CLPS, (NASA, n.d.)) to deliver science and technology to the Moon, with launches starting in November 2023. The European Space Agency (ESA) Argonaut (ESA Argonaut, 2022) programme plans to have recurrent missions to bring payloads to the lunar surface, supporting lunar exploration. These are just a few examples of planned missions that will target the Earth’s natural satellite in the next decade, with forecasts of tens of missions per year (NSR, 2022), (Euroconsult, 2020). The large number of missions and the complexity of landing and operating are expected to demand a change of paradigm from the current Earth-based communication and navigation services. In recent years, several agencies have proposed to deploy cislunar communication and navigation services to support lunar missions (NASA LCRNS, 2022), (ESA Moonlight, 2022), (JAXA, 2022)). All these proposals seek to deploy service-providing satellites in lunar orbit to ease the user missions’ operations. The PNT services objective is to support all types of lunar users (e.g.: orbiters, landers, ascent vehicles, and surface crew and rovers). At the same time, NASA and ESA initiated an effort to define a common framework to ensure interoperability among different service providers: the LunaNet framework. The LunaNet Interoperability Specification (NASA and ESA, 2023) covers communication, PNT, and auxiliary services, by establishing a common set of requirements to ensure interoperability. This conference contribution will present the LunaNet PNT services, focusing on the Lunar Augmented Navigation Service (LANS) that resembles the Global Navigation Satellite System (GNSS) concept on Earth: constellations of satellites broadcasting a radio navigation signal synchronized to a common reference clock, with augmentations to accommodate users’ needs in an environment away from Earth. This includes a description of the high-level LANS concept and the basic principles defined to ensure interoperability. In addition, it will describe the common S-band PNT Augmented Forward Signal (AFS) and common messages to be adopted for compliance with the LunaNet framework, and the justification of the selected approach.

LunaNet↗

Investigating the Simulink Auto-Coding Process

Model based program design is the most clear and direct way to develop algorithms and programs for interfacing with hardware. While coding "by hand" results in a more tailored product, the ever-growing size and complexity of modern-day applications can cause the project work load to quickly become unreasonable for one programmer. This has generally been addressed by splitting the product into separate modules to allow multiple developers to work in parallel on the same project, however this introduces new potentials for errors in the process. The fluidity, reliability and robustness of the code relies on the abilities of the programmers to communicate their methods to one another; furthermore, multiple programmers invites multiple potentially differing coding styles into the same product, which can cause a loss of readability or even module incompatibility. Fortunately, Mathworks has implemented an auto-coding feature that allows programmers to design their algorithms through the use of models and diagrams in the graphical programming environment Simulink, allowing the designer to visually determine what the hardware is to do. From here, the auto-coding feature handles converting the project into another programming language. This type of approach allows the designer to clearly see how the software will be directing the hardware without the need to try and interpret large amounts of code. In addition, it speeds up the programming process, minimizing the amount of man-hours spent on a single project, thus reducing the chance of human error as well as project turnover time. One such project that has benefited from the auto-coding procedure is Ramses, a portion of the GNC flight software on-board Orion that has been implemented primarily in Simulink. Currently, however, auto-coding Ramses into C++ requires 5 hours of code generation time. This causes issues if the tool ever needs to be debugged, as this code generation will need to occur with each edit to any part of the program; additionally, this is lost time that could be spent testing and analyzing the code. This is one of the more prominent issues with the auto-coding process, and while much information is available with regard to optimizing Simulink designs to produce efficient and reliable C++ code, not much research has been made public on how to reduce the code generation time. It is of interest to develop some insight as to what causes code generation times to be so significant, and determine if there are architecture guidelines or a desirable auto-coding configuration set to assist in streamlining this step of the design process for particular applications. To address the issue at hand, the Simulink coder was studied at a foundational level. For each different component type made available by the software, the features, auto-code generation time, and the format of the generated code were analyzed and documented. Tools were developed and documented to expedite these studies, particularly in the area of automating sequential builds to ensure accurate data was obtained. Next, the Ramses model was examined in an attempt to determine the composition and the types of technologies used in the model. This enabled the development of a model that uses similar technologies, but takes a fraction of the time to auto-code to reduce the turnaround time for experimentation. Lastly, the model was used to run a wide array of experiments and collect data to obtain knowledge about where to search for bottlenecks in the Ramses model. The resulting contributions of the overall effort consist of an experimental model for further investigation into the subject, as well as several automation tools to assist in analyzing the model, and a reference document offering insight to the auto-coding process, including documentation of the tools used in the model analysis, data illustrating some potential problem areas in the auto-coding process, and recommendations on areas or practices in the current Ramses model that should be further investigated. Several skills were required to be built up over the course of the internship project. First and foremost, my Simulink skills have improved drastically, as much of my experience had been modeling electronic circuits as opposed to software models. Furthermore, I am now comfortable working with the Simulink Auto-coder, a tool I had never used until this summer; this tool also tested my critical thinking and C++ knowledge as I had to interpret the C++ code it was generating and attempt to understand how the Simulink model affected the generated code. I had come into the internship with a solid understanding of Matlab code, but had done very little in using it to automate tasks, particularly Simulink tasks; along the same lines, I had rarely used shell script to automate and interface with programs, which I gained a fair amount of experience with this summer, including how to use regular expression. Lastly, soft-skills are an area everyone can continuously improve on; having never worked with NASA engineers, which to me seem to be a completely different breed than what I am used to (commercial electronic engineers), I learned to utilize the wealth of knowledge present at JSC. I wish I had come into the internship knowing exactly how helpful everyone in my branch would be, as I would have picked up on this sooner. I hope that having gained such a strong foundation in Simulink over this summer will open the opportunity to return to work on this project, or potentially other opportunities within the division. The idea of leaving a project I devoted ten weeks to is a hard one to cope with, so having the chance to pick up where I left off sounds appealing; alternatively, I am interested to see if there are any opening in the future that would allow me to work on a project that is more in-line with my research in estimation algorithms. Regardless, this summer has been a milestone in my professional career, and I hope this has started a long-term relationship between JSC and myself. I really enjoy the thought of building on my experience here over future summers while I work to complete my PhD at Missouri University of Science and Technology.

Gualdoni, Matthew J.↗

Lunanet Position, Navigation, and Timing Services and Signals, Enabling the Future of Lunar Exploration

The International Space Exploration Coordination Group established in 2018 the 3rd edition of the Global Exploration Roadmap (ISECG, 2018) that aims to achieve Mars human surface activities and identifies the exploration of the Moon as a critical intermediate step. A supplement covering updates on surface exploration scenarios was released in 2020 (ISECG, 2020). The Artemis Accords (NASA Artemis, 2020), first signed in October 2020, now includes over two dozen nations, in an agreement on the principles for best practices, including interoperability. In September 2022 the National Aeronautics and Space Administration (NASA) introduced the Moon to Mars Objectives highlighting recurring tenets of collaboration with international and industry partners and interoperability, along with infrastructure objectives for Position, Navigation, and Timing (PNT). The successful Artemis 1 mission paved the way to the ambitious plans to establish a sustainable human presence on the Moon. Just a few months after Artemis 1 launch (NASA, 2022), iSpace HAKUTO-R Mission1 (iSpace, 2022) launched, being the first-ever mission launched by a commercial launch service provider aiming to land on the lunar surface. The NASA Artemis program plans initial crewed landings and surface traverses in 2025, supported by the Lunar Gateway. Regular launches will follow to build the lunar systems for a sustained presence as presented in the Artemis Plan (NASA Artemis Plan, 2020), (NASA, 2022). NASA’s contracts with commercial providers through the Commercial Lunar Payload Services program (CLPS, (NASA, n.d.)) will deliver science and technology demonstration missions to the Moon starting in November 2023. The European Space Agency (ESA) Argonaut (ESA Argonaut, 2022) program plans to have recurrent missions to bring payloads to the lunar surface, supporting lunar exploration. These are just a few examples of planned missions that will target Earth’s natural satellite in the next decade, with forecasts of tens of missions per year (NSR, 2022), (Euroconsult, 2020). The large number of missions and the complexity of landing and operating are expected to demand a change of paradigm from the current Earth-based communication and navigation services, that may be combined with onboard sensors. In recent years, several agencies have proposed to deploy cislunar communication and navigation services to support lunar missions (NASA LCRNS, 2022), (ESA Moonlight, 2022), (JAXA, 2022)). All these proposals seek to deploy service-providing satellites in lunar orbit to ease the user missions’ operations. The PNT services objective is to support all types of lunar users (e.g.: orbiters, landers, ascent vehicles, surface crew, rovers, and deployed science payloads). At the same time, NASA and ESA initiated an effort to define a common framework to ensure interoperability among different service providers: the LunaNet framework. The LunaNet Interoperability Specification (NASA and ESA, 2023) covers communication, PNT, and auxiliary services, by establishing a common set of requirements to ensure interoperability. This conference contribution will present the LunaNet PNT services, focusing on the Lunar Augmented Navigation Service (LANS) that would be provided by a system that resembles the Global Navigation Satellite System (GNSS) concept on Earth: constellations of satellites broadcasting a radio navigation signal synchronized to a common reference clock, with augmentations to accommodate users’ needs in an environment away from Earth. This paper includes a description of the high-level LANS concept, and the basic principles defined to ensure interoperability. In addition, it will describe the common S-band PNT Augmented Forward Signal (AFS) and common messages to be adopted for compliance with the LunaNet framework, and the justification of the selected approach.

LunaNet↗