Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “Generation scheduling”

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 901 records · Page 50
All sourcesNASA NTRSDOE OSTI
NASA NTRS2015

An Overview of Production and Validation of the SMAP Passive Soil Moisture Product

The Soil Moisture Active Passive (SMAP) mission is an L-band mission scheduled for launch in Jan. 2015. The SMAP instruments consist of a radar and a radiometer to obtain complementary information from space for soil moisture and freeze/thaw state research and applications. By utilizing novel designs in antenna construction, retrieval algorithms, and acquisition hardware, SMAP provides a capability for global mapping of soil moisture and freeze/thaw state with unprecedented accuracy, resolution, and coverage. This improvement in hydrosphere state measurement is expected to advance our understanding of the processes that link the terrestrial water, energy and carbon cycles, improve our capability in flood prediction and drought monitoring, and enhance our skills in weather and climate forecast. For swath-based soil moisture measurement, SMAP generates three operational geophysical data products: (1) the radiometer-only soil moisture product (L2_SM_P) posted at 36-kilometer resolution, (2) the radar-only soil moisture product (L2_SM_A) posted at 3-kilometers resolution, and (3) the radar-radiometer combined soil moisture product (L2_SM_AP) posted at 9-kilometers resolution. Each product draws on the strengths of the underlying sensor(s) and plays a unique role in hydroclimatological and hydrometeorological applications. A full suite of SMAP data products is given in Table 1.

passive microwave↗
NASA NTRS2018

Use of Shuttle Heritage Hardware in Space Launch System (SLS) Application-Structural Assessment

NASA is moving forward with the development of the next generation system of human spaceflight to meet the Nation's goals of human space exploration. To meet these goals, NASA is aggressively pursuing the development of an integrated architecture and capabilities for safe crewed and cargo missions beyond low-Earth orbit. Two important tenets critical to the achievement of NASA's strategic objectives are Affordability and Safety. The Space Launch System (SLS) is a heavy-lift launch vehicle being designed/developed to meet these goals. The SLS Block 1 configuration (Figure 1) will be used for the first Exploration Mission (EM-1). It utilizes existing hardware from the Space Shuttle inventory, as much as possible, to save cost and expedite the schedule. SLS Block 1 Elements include the Core Stage, "Heritage" Boosters, Heritage Engines, and the Integrated Spacecraft and Payload Element (ISPE) consisting of the Launch Vehicle Stage Adapter (LVSA), the Multi-Purpose Crew Vehicle (MPCV) Stage Adapter (MSA), and an Interim Cryogenic Propulsion Stage (ICPS) for Earth orbit escape and beyond-Earth orbit in-space propulsive maneuvers. When heritage hardware is used in a new application, it requires a systematic evaluation of its qualification. In addition, there are previously-documented Lessons Learned (Table -1) in this area cautioning the need of a rigorous evaluation in any new application. This paper will exemplify the systematic qualification/assessment efforts made to qualify the application of Heritage Solid Rocket Booster (SRB) hardware in SLS. This paper describes the testing and structural assessment performed to ensure the application is acceptable for intended use without having any adverse impact to Safety. It will further address elements such as Loads, Material Properties and Manufacturing, Testing, Analysis, Failure Criterion and Factor of Safety (FS) considerations made to reach the conclusion and recommendation.

Aggarwal, Pravin↗
NASA NTRS2019

Scenario Complexity for Unmanned Aircraft System Traffic

This work introduces an approach to estimate the complexity of a low-altitude air traffic scenario involving multiple UASs using mathematical programming. Given a set of multi-point UAS flight trajectories, vehicle dynamics, and a conflict resolution algorithm, an abstract model is developed such that it can be solved quickly using a mathematical programming optimization software without running high-fidelity simulations that can be computationally expensive and may not suit real-time apA quick and accurate assessment of complexity for a given traffic scenario can help plan and schedule flights to alleviate traffic bottleneck and mitigate operation risks, especially for unmanned aerial system traffic management where high traffic density or complexity is expected. This work introduces a traffic scenario complexity metric that was constructed based on the number of potential conflicts weighted by the conflict resolution cost associated. The cost associated with a conflict is calculated based on the corresponding conflict resolution maneuvers. To obtain the conflict resolution maneuvers, a MILP-based optimization was formulated with the vehicle model and conflict management parameters incorporated. To evaluate the complexity metrics, an approach of using measurements from high-fidelity simulations was proposed. The scenario complexity measurements for 920 random-generated scenarios were obtained through high-fidelity simulations and treated as the ground truth. Two statistics methods: Pearson and Alternative Conditional Expectations were applied for analysis. The results showed that the number of flights has low correlation with the scenario complexity according to the correlation coefficients calculated by both methods. The Alternative Conditional Expectations method shows that the proposed scenario complexity metric has better correlation with the ground truth than the number of potential conflicts.plications. In the abstract model, each vehicle is represented by a time-varied vector associated with position, speed, and heading information. The total extra distance that aircraft need to divert from their original routes to avoid collisions is computed and used to setup a quadratic programming formula. The metrics including the number of conflicts and extra distances travelled by all vehicles are then utilized to estimate the complexity of a given UAS flight scenario. Results and verification against high-fidelity simulations will be provided in the final draft.

traffic complexity↗
NASA NTRS1992

The 10 kW power electronics for hydrogen arcjets

A combination of emerging mission considerations such as 'launch on schedule', resource limitations, and the development of higher power spacecraft busses has resulted in renewed interest in high power hydrogen arcjet systems with specific impulses greater than 1000 s for Earth-space orbit transfer and maneuver applications. Solar electric propulsion systems with about 10 kW of power appear to offer payload benefits at acceptable trip times. This work outlines the design and development of 10 kW hydrogen arcjet power electronics and results of arcjet integration testing. The power electronics incorporated a full bridge switching topology similar to that employed in state of the art 5 kW power electronics, and the output filter included an output current averaging inductor with an integral pulse generation winding for arcjet ignition. Phase shifted, pulse width modulation with current mode control was used to regulate the current delivered to arcjet, and a low inductance power stage minimized switching transients. Hybrid power Metal Oxide Semiconductor Field Effect Transistors were used to minimize conduction losses. Switching losses were minimized using a fast response, optically isolated, totem-pole gate drive circuit. The input bus voltage for the unit was 150 V, with a maximum output voltage of 225 V. The switching frequency of 20 kHz was a compromise between mass savings and higher efficiency. Power conversion efficiencies in excess of 0.94 were demonstrated, along with steady state load current regulation of 1 percent. The power electronics were successfully integrated with a 10 kW laboratory hydrogen arcjet, and reliable, nondestructive starts and transitions to steady state operation were demonstrated. The estimated specific mass for a flight packaged unit was 2 kg/kW.

Hamley, John A.↗
NASA NTRS2011

LADEE Satellite Modeling and Simulation Development

As human activity on and around the Moon increases, so does the likelihood that our actions will have an impact on its atmosphere. The Lunar Atmosphere and Dust Environment Explorer (LADEE), a NASA satellite scheduled to launch in 2013, will orbit the Moon collecting composition, density, and time variability data to characterize the current state of the lunar atmosphere. LADEE will also test the concept of the "Modular Common Bus" spacecraft architecture, an effort to reduce both development time and cost by designing reusable, modular components for use in multiple missions with similar requirements. An important aspect of this design strategy is to both simulate the spacecraft and develop the flight code in Simulink, a block diagram-style programming language that allows easy algorithm visualization and performance testing. Before flight code can be tested, however, a realistic simulation of the satellite and its dynamics must be generated and validated. This includes all of the satellite control system components such as actuators used for force and torque generation and sensors used for inertial orientation reference. My primary responsibilities have included designing, integrating, and testing models for the LADEE thrusters, reaction wheels, star trackers, and rate gyroscopes.

Adams, Michael↗
NASA NTRS1996

Petabyte Class Storage at Jefferson Lab (CEBAF)

By 1997, the Thomas Jefferson National Accelerator Facility will collect over one Terabyte of raw information per day of Accelerator operation from three concurrently operating Experimental Halls. When post-processing is included, roughly 250 TB of raw and formatted experimental data will be generated each year. By the year 2000, a total of one Petabyte will be stored on-line. Critical to the experimental program at Jefferson Lab (JLab) is the networking and computational capability to collect, store, retrieve, and reconstruct data on this scale. The design criteria include support of a raw data stream of 10-12 MB/second from Experimental Hall B, which will operate the CEBAF (Continuous Electron Beam Accelerator Facility) Large Acceptance Spectrometer (CLAS). Keeping up with this data stream implies design strategies that provide storage guarantees during accelerator operation, minimize the number of times data is buffered allow seamless access to specific data sets for the researcher, synchronize data retrievals with the scheduling of postprocessing calculations on the data reconstruction CPU farms, as well as support the site capability to perform data reconstruction and reduction at the same overall rate at which new data is being collected. The current implementation employs state-of-the-art StorageTek Redwood tape drives and robotics library integrated with the Open Storage Manager (OSM) Hierarchical Storage Management software (Computer Associates, International), the use of Fibre Channel RAID disks dual-ported between Sun Microsystems SMP servers, and a network-based interface to a 10,000 SPECint92 data processing CPU farm. Issues of efficiency, scalability, and manageability will become critical to meet the year 2000 requirements for a Petabyte of near-line storage interfaced to over 30,000 SPECint92 of data processing power.

Chambers, Rita↗
NASA NTRS2007

Flight and Integrated Testing: Blazing the Trail for the Ares Launch Vehicles

It has been 30 years since the United States last designed and built a human-rated launch vehicle. The National Aeronautics and Space Administration (NASA) has marshaled unique resources from the government and private sectors that will carry the next generation of astronauts into space safer and more efficiently than ever and send them to the Moon to develop a permanent outpost. NASA's Flight and Integrated Test Office (FITO) located at Marshall Space Flight Center and the Ares I-X Mission Management Office have primary responsibility for developing and conducting critical ground and flight tests for the Ares I and Ares V launch vehicles. These tests will draw upon Saturn and the Space Shuttle experiences, which taught the value of using sound systems engineering practices, while also applying aerospace best practices such as "test as you fly" and other lessons learned. FITO will use a variety of methods to reduce the technical, schedule, and cost risks of flying humans safely aboard a launch vehicle.

Taylor, James L.↗
NASA NTRS2009

On-Orbit Calibration and Performance of Aqua MODIS Reflective Solar Bands

Aqua MODIS has successfully operated on-orbit for more than 6 years since its launch in May 2002, continuously making global observations and improving studies of changes in the Earth's climate and environment. 20 of the 36 MODIS spectral bands, covering wavelengths from 0.41 to 2.2 microns, are the reflective solar bands (RSB). They are calibrated on-orbit using an on-board solar diffuser (SD) and a solar diffuser stability monitor (SDSM). In addition, regularly scheduled lunar observations are made to track the RSB calibration stability. This paper presents Aqua MODIS RSB on-orbit calibration and characterization activities, methodologies, and performance. Included in this study are characterizations of detector signal-to-noise ratio (SNR), short-term stability, and long-term response change. Spectral wavelength dependent degradation of the SD bidirectional reflectance factor (BRF) and scan mirror reflectance, which also varies with angle of incidence (AOI), are examined. On-orbit results show that Aqua MODIS onboard calibrators have performed well, enabling accurate calibration coefficients to be derived and updated for the Level 1B (L1B) production and assuring high quality science data products to be continuously generated and distributed. Since launch, the short-term response, on a scan-by-scan basis, has remained extremely stable for most RSB detectors. With the exception of band 6, there have been no new RSB noisy or inoperable detectors. Like its predecessor, Terra MODIS, launched in December 1999, the Aqua MODIS visible (VIS) spectral bands have experienced relatively large changes, with an annual response decrease (mirror side 1) of 3.6% for band 8 at 0.412 microns, 2.3% for band 9 at 0.443 microns, 1.6% for band 3 at 0.469 microns, and 1.2% for band 10 at 0.488 microns. For other RSB bands with wavelengths greater than 0.5 microns, the annual response changes are typically less than 0.5%. In general, Aqua MODIS optics degradation is smaller than Terra MODIS and the mirror side differences are much smaller. Overall, Aqua MODIS RSB on-orbit performance is better than Terra MODIS.

Xiong, Xiaoxiong↗
NASA NTRSDate not supplied

NASA’s Space Launch System: Progress Toward Launch

The Space Launch System (SLS), NASA’s cornerstone launch capability for a new generation of deep space exploration, has begun assembly at Kennedy Space Center (KSC) in preparation for launch in 2021. SLS will provide an unparalleled launch capability for human and robotic deep space exploration missions. Its proven propulsion system, upgrade path to more powerful vehicles, and high-volume payload fairings make it the foundation for ambitious and demanding as part of the Artemis program. Artemis is NASA’s 21st-century plan to put boots on the Moon and to perform sustainable, long-term science in deep space, with eyes toward sending explorers to Mars. The initial SLS vehicle to fly, Block 1 in the crew configuration – with the new Orion spacecraft – is scheduled to lift off from revitalized launch facilities at KSC in 2021 for an uncrewed test flight known as Artemis I. Manufacturing is complete on the vehicle and all elements have been delivered to the Exploration Ground Systems (EGS) Program, except the core stage. The program’s all-new development, the core stage is currently in the midst of a “Green Run” test campaign at Stennis Space Center (SSC). Eight progressively more challenging tests in the Green Run series will culminate in a hot-fire of four flight-proven liquid hydrogen/liquid oxygen (LH2/LOX) RS25 engines. Following the Green Run hotfiring, the core stage will ship to KSC. Already at KSC, aft sections of the fivesegment solid rocket boosters are being assembled. Previously delivered elements, including the upper stage, are undergoing final checkouts in preparation for stacking. An exciting 2021 will include such milestones as stacking SLS and Orion in KSC’s Vehicle Assembly Building (VAB), modal testing, roll out to Launch Pad 39B, Wet Dress Rehearsal (WDR), and launch. Teams across the country are preparing for launch by finalizing procedures, defining launch constraints and flight rules, training console operators, performing simulations, and more. With the SLS Block 1 vehicle for Artemis I nearing integration and launch, the second Block 1 vehicle in the crew configuration, which will carry astronauts on an Artemis II hybrid lunar flyby mission, has several elements manufactured. In fact, the solid rocket motor segments and RS-25 engines are complete. Those program elements are processing hardware for the third flight and working toward manufacturing the second SLS variant to fly, Block 1B, which will onramp a powerful new upper stage, the Exploration Upper Stage (EUS).

John Honeycutt↗
NASA NTRSDate not supplied

Some Aeronautical Communications Experiments

Classically there has existed an asymmetry between the computing and communicating sides of aerospace systems. Over the past few decades, this asymmetry has shifted to favoring communication link technologies, meaning that advancements in available central processing units (CPUs), storage devices, and internal data buses have stagnated. Indeed, the increased emphasis placed on refining subsystem performance such as with antenna bandwidth in phased arrays, amplifier power efficiency, software defined radio (SDR) flexibility and encoding for data compression and error correction has given rise to successful debuts of multi-gigabit-per-second data return from long space-link distances. These accomplishments are easily quantifiable through link budgets and illustrate what is possible, but also reveal the deficiencies in overall communications capabilities. In particular, the ever-accelerating presence of aerospace vehicles gives rise to newer and larger classes of challenges to address the needs of 21st century systems. Furthermore remote sensing and imaging capabilities have far outpaced our ability to transmit their products to the ground, so we are increasingly dependent on pre-processing and downselection to contend with the communications bottleneck. No longer may we depend upon the constrained logistics in delivering end-to-end data delivery through manual reconfigurations, static event scheduling and execution on a per-vehicle basis, for these methods do not scale and therefore must give way to dynamic, networked approaches with an overall systems view in mind. Emerging mission requirements exhibit a trend toward multiple smaller-scale vehicles working together to perform dissimilar observations. Such operations necessitate sensor fusion across a constellation, and where data processing may be distributed throughout a fairly disconnected network whose topology changes over time in non-deterministic manners. Individual communications link performance is still very relevant to deploying an effective communications system, but now must be embedded within a greater architecture of capability to optimally utilize the bandwidth available from each link to generate an ultimate end-to-end quality of service. The deleterious effects of timing uncertainty across the arrangement presents a challenge to measurement synchronization and delivery, so a successful deployed system needs to be tolerant to the delays inherent in time-of-light between elements and digital processing latencies existing at each node. In this presentation we share the flight test results from a high performance Gbps laser communications terminal evaluated with a suite of store and forward capabilities called High-rate Delay Tolerant Networking (HDTN). The communications payload is operated over Lake Erie across a range of configurations including several convergence layers, and is evaluated to determine recovery time after link disruptions, information loss, efficiency and speed. The effectiveness of utilizing a flying laboratory to increase the Technology Readiness Level (TRL) of an integrated system in relevant environments is discussed, as well as the value of conducting aeronautics experiments to retire risk for technology infusion into space missions. Upcoming flight campaigns will be presented, including opportunities to demonstrate secure command and control, data intensive hyperspectral imaging, quantum link characterization, 4k High Definition (HD) video streaming and internetworked space-ground-aero relay operations. These experiments will pave the way for future missions which will depend upon interoperability across disparate government and privately owned networks, involve contention with uncertain and dynamic timing, and require agility to autonomously configure optimal parameters across networks of ever-increasing size and complexity to ensure data delivery. https://www1.grc.nasa.gov/space/scan/acs/tech-studies/dtn/

Daniel Raible↗
NASA NTRS1993

California Student Get Away Special Payload GAS-450

The California Student Get Away Special Payload GAS-450, recently went into orbit on the STS-57 Mission, Space Shuttle, Endeavour, 21 June 1993, 6:14 AM and landed on the 29 June 1993 at Kennedy Space Center (KSC). Fifty students from 13 California Central Coast Schools and one in San Francisco designed and built 13 active experiments (6 modules) for this mission. Preliminary analysis of our completely reusable payload bus system indicated that the structure, power system, microprocessor, and sensor systems in each experiment module worked flawlessly. The experiments themselves performed exceptionally well with a 60 percent success ratio. The students are thoroughly documenting their own experiments and results via a standard research paper guideline generated by the GAS-450 technical staff. Lessons learned (program management and technical) are documented at the end of the paper. If any other organization needs payload/experiment development or NASA documentation assistance, then please contact us. We can help make your idea a space tested reality. Three years of intense effort culminated on 3 February 1993, the GSFC field operations team at Kennedy Space Center performed the final pressure decay and electrical tests upon the fully integrated GAS-450 flight canister. Subsequently, the payload was integrated with its parent GAS Bridge Assembly in mid-February and the bridge was transferred to the KSC orbiter team in late February 1993. The STS-57 mission originally scheduled to launch on the 29 April 1993 slipped until 21 June 1993. Our Payload shared the cargo bay with ten other GAS Canisters, the EUREKA experiment, the SHOOT experiment, and the SPACEHAB-1 module. The SIL technical staff retrieved the GAS-450 payload after flight from the NASA Spin Test Facility at KSC and shipped it back to California on the 22 July 1993 for student analysis at Allan Hancock College this summer.

Ray, Glen↗
NASA NTRS2011

Draper Station Analysis Tool

Draper Station Analysis Tool (DSAT) is a computer program, built on commercially available software, for simulating and analyzing complex dynamic systems. Heretofore used in designing and verifying guidance, navigation, and control systems of the International Space Station, DSAT has a modular architecture that lends itself to modification for application to spacecraft or terrestrial systems. DSAT consists of user-interface, data-structures, simulation-generation, analysis, plotting, documentation, and help components. DSAT automates the construction of simulations and the process of analysis. DSAT provides a graphical user interface (GUI), plus a Web-enabled interface, similar to the GUI, that enables a remotely located user to gain access to the full capabilities of DSAT via the Internet and Webbrowser software. Data structures are used to define the GUI, the Web-enabled interface, simulations, and analyses. Three data structures define the type of analysis to be performed: closed-loop simulation, frequency response, and/or stability margins. DSAT can be executed on almost any workstation, desktop, or laptop computer. DSAT provides better than an order of magnitude improvement in cost, schedule, and risk assessment for simulation based design and verification of complex dynamic systems.

Bedrossian, Nazareth↗
NASA NTRS2019

Quantitative Comparison of Proprietary and Open-Source Georeferencing Tools for Use with Astronaut Photography

The Crew Earth Observations (CEO) Facility within the Earth Science and Remote Sensing Unit at NASA’s Johnson Space Center supports the acquisition, analysis, and curation of astronaut photography of Earth’s surface and atmosphere. Astronauts on the International Space Station (ISS) respond to requests from CEO to acquire imagery of scientific and education targets, to include high profile targets in response to activations from the International Charter for Space & Major Disasters (also known as the International Disaster Charter, or IDC) and NASA’s Disasters Program. CEO facilitates the acquisition of astronaut photography in response to IDC events and delivers georeferenced data products to the United States Geological Survey (USGS) for distribution to the disaster community. Using GeoRef, an internal web-based tool developed in collaboration with NASA’s Ames Research Center, CEO generates data packages of georeferenced imagery, uncertainty images for assessing control and tie point accuracy, and metadata documenting raw and processed data. Operational experience with the Georef software identified vulnerabilities to internal code and server errors that can significantly increase time of data production. As such, CEO developed a backup procedure in case the GeoRef software experiences front-end or back-end errors. A system using OSGEO’s open-source QGIS software combined with a semi-automated pipeline using the object-oriented Python language and the Geospatial Abstract Library for generating metadata is quantitatively compared to GeoRef’s data package for quality and productivity. Root Mean Square Error (RMSE) provides a standard measurement of data quality as it relates to ground error. Assessing RMSE measurements generated from georeferenced astronaut photographs acquired with different obliquity and focal length offers a comprehensive accuracy assessment of the software’s transformation algorithms. This assessment will indicate the software's ability to produce data products with the least ground-error or highest data quality regarding ground accuracy. In addition, a comparison of the software’s efficiency in generating a data package that includes georeferenced images, metadata, and uncertainty images for measuring tie/ground point error was performed. Initial results, based on the comparison of three nadir-facing astronaut photographs acquired with a 95mm focal length, reveal the QGIS-based system's average RMSE is 2.36 (pixels) suggesting its georectification system produces data products that meet and perhaps improve upon Georef solution's average RMSE of 32.99 (pixels). However, the QGIS system was unable to reproduce two unique Georef data products, uncertainty images for measuring tie and control point errors and a translated unwrapped image. In addition, the Georef software is designed to accept handheld camera pose information from a hardware component (Geosens) scheduled for deployment on the ISS in late 2018; this information is intended to provide increased accuracy and auto-registration capability for astronaut photographs. Future work is expected to determine the QGIS-based georectification system’s potential as an open-source alternative (and operational backup) to Georef for georeferencing the full range of resolutions and viewing angles unique to handheld digital camera imagery in support of ISS disaster response activities.

Jagge, Amy M.↗
NASA NTRS1993

Superfluid Helium On-Orbit Transfer (SHOOT) flight demonstration

The Superfluid Helium On-Orbit Transfer (SHOOT) Flight Demonstration was an attached Shuttle payload mounted on a Hitchhiker cross-bay carrier which flew on STS-57 in June of 1993. SHOOT successfully demonstrated the handling and transfer of superfluid helium between two containers, called dewars, in low gravity. SHOOT was a class C payload and for the STS-57 mission was termed a complex secondary payload. The primaries were the retrieval of the EURECA carrier and a collection of modular experiments contained in SPACEHAB. Because the liquid helium was continuously boiling off, SHOOT's activities were scheduled for the first three days of the mission, concurrent with some SPACEHAB experiments, but well before the EURECA retrieval. Control of the SHOOT experiment was highly interactive and originated primarily from the Goddard Payload Operations and Control Center (POCC). Transfer and calibration activities required continuous command windows of up to 50 minutes duration and up to 80 minutes out of each orbit. Occasionally the crew controlled the experiment using the Payload General Support Computer (PGSC) when near-real time control and monitoring was required. SHOOT also placed considerable demands on the orbiter, including a pitch rotation of 3 deg./sec for 15 minutes, and translational burns using both the aft and forward RCS jets to generate accelerations up to 7 milli-g. The basis for these and other requirements are discussed. Interacion with the crew and timing of crew activity during the mission will be detailed. The processing flow of SHOOT at KSC is described with emphasis on the tradeoffs for vertical, as opposed to horizontal, installation in the orbiter. Finally, some lessons learned are presented that are relevant to future cryogenic and Hitchhiker payloads.

Shirron, Peter↗
NASA NTRS1995

A rule-based shell to hierarchically organize HST observations

An observing program on the Hubble Space Telescope (HST) is described in terms of exposures that are obtained by one or more of the instruments onboard the HST. These exposures are organized into a hierarchy of structures for purposes of efficient scheduling of observations. The process by which exposures get organized into the higher-level structures is called merging. This process relies on rules to determine which observations can be 'merged' into the same higher level structure, and which cannot. The TRANSformation expert system converts proposals for astronomical observations with HST into detailed observing plans. The conversion process includes the task of merging. Within TRANS, we have implemented a declarative shell to facilitate merging. This shell offers the following features: (1) an easy way of specifying rules on when to merge and when not to merge, (2) a straightforward priority mechanism for resolving conflicts among rules, (3) an explanation facility for recording the merging history, (4) a report generating mechanism to help users understand the reasons for merging, and (5) a self-documenting mechanism that documents all the merging rules that have been defined in the shell, ordered by priority. The merging shell is implemented using an object-oriented paradigm in CLOS. It has been a part of operational TRANS (after extensive testing) since July 1993. It has fulfilled all performance expectations, and has considerably simplified the process of implementing new or changed requirements for merging. The users are pleased with its report-generating and self-documenting features.

Bose, Ashim↗
NASA NTRS2008

James Webb Space Telescope - Applying Lessons Learned to I&T

The James Webb Space Telescope (JWST) is part of a new generation of spacecraft acquiring large data volumes from remote regions in space. To support a mission such as the JWST, it is imperative that lessons learned from the development of previous missions such as the Hubble Space Telescope and the Earth Observing System mission set be applied throughout the development and operational lifecycles. One example of a key lesson that should be applied is that core components, such as the command and telemetry system and the project database, should be developed early, used throughout development and testing, and evolved into the operational system. The purpose of applying lessons learned is to reap benefits in programmatic or technical parameters such as risk reduction, end product quality, cost efficiency, and schedule optimization. In the cited example, the early development and use of the operational command and telemetry system as well as the establishment of the intended operational database will allow these components to be used by the developers of various spacecraft components such that development, testing, and operations will all use the same core components. This will reduce risk through the elimination of transitions between development and operational components and improve end product quality by extending the verification of those components through continual use. This paper will discuss key lessons learned that have been or are being applied to the JWST Ground Segment integration and test program.

Johns, Alan↗
NASA NTRS1980

A solar encounter mission - Starprobe

Accurate measurements of the internal mass distribution and dynamics of the sun as well as in situ observations of its environs are proposed through a JPL-designed satellite, STARPROBE. Scheduled for launch in 1988 under NASA's five-year plan, the probe will conduct radiometric experiments to determine the solar quadrupole moment (J2), fields-and-particles experiments (evaluating such phenomena as heating, acceleration, and peak random velocity of solar wind), and optical experiments potentially superior to those of the Earth-orbiting Solar Optical Telescope (SOT). With flight times ranging from 2.7 to 5.9 years, present delivery options comprise planetary gravity-assist trajectories that will give the spacecraft a perihelion of four solar radii at a 90 deg-inclination. Owing to science- and mission requirements, the thermal shield of the craft should tolerate a solar flux 3000 times greater than that at earth, radioisotope thermoelectric generators supplying 700 watts of power, and a three-axis stabilization system with reaction wheels providing control torque. Implementation concepts now under study may change some of the details of the design.

Randolph, J. E.↗
NASA NTRSDate not supplied

A Notional Artemis Lunar Surface Exploration Package (ArLSEP) based on the Gandalf Staff Platform

Introduction: The Artemis program is planning to deliver crew and cargo to the lunar surface, but there is no current package for supporting lunar in-struments and experiments similar to the Apollo Lunar Surface Exploration Package (ALSEP). This abstract provides a possible concept for such a package using the Gandalf Staff Platform as a common core. Gandalf Staff: The Gandalf Staff is an early prototype system developed over FY’21/FY’22 using NASA Science Technology Mission Directorate (STMD) Center Information Fund (CIF) grants to de-sign, build and test “proof-of-concept” components. These components include a 24v battery powered monopole that powers a suite of subsystems, including a Graphical User Interface (GUI) for crew, surface voice and data communications, Lunar Search and Rescue (LunaSAR) navigation and communications, LiDAR, field site external lighting, 360-degree camera, and a geothermal instrument for measuring sub-surface temperature gradient. The staff can be carried independently by an Extra-Vehicular Activity (EVA) astronaut, or can be mounted into a tripod for “hands free” support at a surface site being investigated. The staff can be attached to an external solar array and power storage system for long-duration operations. [1,2] ALSEP: An ASLEP flew on each mission Apollo 12 to Apollo 17. For Apollo 11, a simplified packaged called the Early Apollo Scientific Experiments Pack-age (EASEP) was flown. Each package included a “Central Station” that provided the power and communications connected to a variety of instruments and sensors. The power was provided by a Radioisotope Thermoelectric Generator (RTG) fueled by Plutoni-um-238 generating 70 watts of power (initially, decayed over time) [3]. The communications system provide for direct to Earth data transfer from the lunar surface. Each pack-age was stowed externally in the Lunar Module (LM) Scientific Equipment (SEQ) bay with a mass up to 163 kg (Apollo 17). The crew unloaded the ALSEP from the LM and deployed the instruments on the lunar surface. Although designed to operate for only 1 year, many sites operated for up to 8 years successfully [4]. The Active Seismic Experiment (ASE) included 3 geophones for detecting seismic waves created by mortars and thumpers deployed by the crew. Other active experiments measured the lunar atmosphere, the heat flow in the subsurface, the lunar gravity and potential gravity waves, the lunar magnetic field, the solar wind and plasma interactions in cislunar space. Passive experiments included collectors for dust and cosmic rays, and retroreflectors for precise measurements of distance using a laser from Earth. The ALSEP program continues to generate insights into lunar formation and evolution. ArLSEP Concepts: The lunar surface science package for the Artemis program will hopefully exceed the capability of the ALSEP. There are multiple issues for discussion leading to the design of a new ArLSEP, needing requirements definition from the science community, NASA mission architecture, and NASA budget planners. 1. Delivery Mechanism Two possible projects currently provide capability to deliver scientific cargo to the lunar surface: 1) the Commercial Lunar Payload Services (CLPS) [5] and the Human Landing System (HLS) [6, 7]. Each project is controlled by a different organization within NASA and budgeted with different criteria although both support lunar exploration. The HLS system delivers crew (and potentially cargo) to human landing sites. If an ArLSEP is “predeployed” to such a site, the design must include power (either from the vehicle or independently) to keep the electronics functioning until deployed by the crew. If an ArLSEP is delivered on a vehicle after the crew is present on the lunar surface, safety protocols require adequate distance from the humans for impact from descent propelled sur-face regolith ejecta. This distance can not exceed the capability of the crew to walk (if no rover) to the vehicle for ArLSEP deployment. 2. Overall Guidelines The general design of ArLSEP will likely follow the ALSEP with a common system for communications and power; however, significant architecture differences between Apollo and Artemis exist. Power: The RTG will not be available for early Artemis missions nor likely follow-on Lunar Exploration Transportation Services (LETS) missions [8]. Thus, ArLSEP power must be supplied by solar arrays with sufficient battery capability to “keep alive” necessary electronics during any lunar surface eclipse period. Communication: The Artemis program is developing a series of communications satellites for lunar orbit to provide surface transmission of data and voice to Earth. Called “LunaNET”, this network is component useful for ArLSEP since south polar locations may not always have direct “line-of-sight” to Earth [9]. 3. Concept of Operations (ConOps) The general ConOps for ArLSEP is to deliver the package to lunar surface before the crew arrives, and then have the crew deploy the package after some period of time. This requires coordinated design (for power systems) and launch window (for schedule) on both the cargo and crew missions. Once the ArLSEP is deployed, it will operate autonomously for a number of years. It should be designed to be EVA compatible for crew maintenance and upgrade. 4. Notional Design (for discussion purpose only) The landing site near the South Pole is expected to have no eclipse cycle exceeding 5 days, so the “keep alive” power is 144 hours (6 days to include margin). A 12v ArLSEP will use rechargeable LiFePO4 cells, which are common in the Electric Vehicle (EV) industry. With a current of 5 amps and a 125 watt system, the mass is about 90kg. The comm. system and structure adds another 10kg, thus the “Central Station” is approximately 100kg. The solar power is collected on four arrays (each 2m above the surface), and the entire ArLSEP is designed to stow in a 2m x 1m x 1m volume. The experiment and instrument design will vary for each installation and add mass to the total (although they are expected to fit within the 2m3 volume). Seismic wave generation will likely not be provided with mortars, thus an electric “thumper” will be required. Active instruments such as imaging systems and sensing instruments will benefit from the additional power and communication capability provided by ArLSEP. Passive systems such as retroreflectors, witness plates, and cosmic dust collectors can be added to either the landing vehicle and/or the ArLSEP. With repeated HLS missions to the same human site, the ArLSEP can be expanded and easily maintained for long duration science collection on the lunar surface.

ALSEP↗