Search NASASearch

SEARCH · Search NASA

Results for “Science Definition Team”

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 127 records · Page 7

Robotic Lunar Landers for Science and Exploration

NASA Marshall Space Flight Center and The Johns Hopkins University Applied Physics Laboratory has been conducting mission studies and performing risk reduction activities for NASA s robotic lunar lander flight projects. In 2005, the Robotic Lunar Exploration Program Mission #2 (RLEP-2) was selected as a Exploration Systems Mission Directorate precursor robotic lunar lander mission to demonstrate precision landing and definitively determine if there was water ice at the lunar poles; however, this project was canceled. Since 2008, the team has been supporting NASA s Science Mission Directorate designing small lunar robotic landers for diverse science missions. The primary emphasis has been to establish anchor nodes of the International Lunar Network (ILN), a network of lunar science stations envisioned to be emplaced by multiple nations. This network would consist of multiple landers carrying instruments to address the geophysical characteristics and evolution of the moon. Additional mission studies have been conducted to support other objectives of the lunar science community and extensive risk reduction design and testing has been performed to advance the design of the lander system and reduce development risk for flight projects. This paper describes the current status of the robotic lunar mission studies that have been conducted by the MSFC/APL Robotic Lunar Lander Development team, including the ILN Anchor Nodes mission. In addition, the results to date of the lunar lander development risk reduction efforts including high pressure propulsion system testing, structure and mechanism development and testing, long cycle time battery testing and combined GN&C and avionics testing will be addressed. The most visible elements of the risk reduction program are two autonomous lander test articles: a compressed air system with limited flight durations and a second version using hydrogen peroxide propellant to achieve significantly longer flight times and the ability to more fully exercise flight sensors and algorithms. Robotic Lunar Lander design and development will have significant feed-forward to other missions to the Moon and, indeed, to other airless bodies such as Mercury, asteroids, and Europa, to which similar science and exploration objectives are applicable.

Cohen, B. A.

Operations Concept for Responding to Urgent Requests for NASA-ISRO Synthetic Aperture Radar (NISAR)

The NASA-ISRO Synthetic Aperture Radar, or NISAR, mission is an Earth-mapping radar observatory to be launched from Sriharikota (India) in 2022. This mission is a collaboration between the National Aeronautics and Space Administration (NASA) and the Indian Space Research Organization (ISRO). This spacecraft will carry two instruments that will operate at radar wavelengths (L and Sband) and will provide data for understanding changes in the Earth’s land surface. The scientific data from this mission will revolutionize our understanding of the causes and consequences of land surface changes on Earth, ranging from Solid Earth Deformation in the form of natural hazards like earthquakes, volcanic eruptions and landslides, to ecosystem disturbances, to changes in the cryosphere (measurements of polar ice caps, ice sheets and sea ice). A nominal Reference Observation Plan, that repeats roughly every 12-24 days, developed prior to launch by the NISAR Mission Planning team, in consultation with the Science Team, will form the basis of science data collection by the payload instruments onboard the NISAR observatory after launch. Scheduling of science observations for the mission requires accounting for limited spacecraft resources like onboard data storage, downlink capacity, energy/power, thermal limits and instrument duty cycles. In addition to nominal science data collection, the project has a Level 1 requirement to respond to requests for urgent data acquisition over disaster sites (natural or anthropogenic) by scheduling new acquisitions within 24 hrs of notification and delivering science data within 5 hours of data acquisition. This capability is to be exercised on a ‘best-efforts basis’. While the definition of what constitutes an ‘urgent request’, and how such requests would be submitted to the project, is within the domain of the Science Team, the Mission System team is responsible for developing the baseline operations concept and implementation approach for responding to such requests. Given the ‘best-efforts’ nature of this requirement, a few highlevel guidelines have been developed to help guide the formulation of the operations concept, and are presented in this paper. Requests for urgent response data will be accommodated following the guiding principle of minimal to no impact on nominal science and planned engineering activities. No change in satellite orbit or attitude will be made for urgent response. Restricting response approaches to only changing the downlink and/or ground processing priority for existing observations, and adding new observations only in areas where NISAR will not be nominally imaging, allows for minimal impact on the Reference science Observation Plan. No instrument mode changes will be allowed for urgent response (except for high-priority requests), and no new observations that impact either planned science or engineering activities will be scheduled. Additionally, data requests must fit within the available project resource margins (both spacecraft and ground resources are to be evaluated). Both JPL and ISRO will be involved at various steps of the implementation, irrespective of whether the urgent request is for L-SAR (NASA instrument) or S-SAR (ISRO instrument) or a joint dataset.

Sharma, Priyanka

The MSFC Collaborative Engineering Process for Preliminary Design and Concept Definition Studies

This paper describes a collaborative engineering process developed by the Marshall Space Flight Center's Advanced Concepts Office for performing rapid preliminary design and mission concept definition studies for potential future NASA missions. The process has been developed and demonstrated for a broad range of mission studies including human space exploration missions, space transportation system studies and in-space science missions. The paper will describe the design team structure and specialized analytical tools that have been developed to enable a unique rapid design process. The collaborative engineering process consists of integrated analysis approach for mission definition, vehicle definition and system engineering. The relevance of the collaborative process elements to the standard NASA NPR 7120.1 system engineering process will be demonstrated. The study definition process flow for each study discipline will be will be outlined beginning with the study planning process, followed by definition of ground rules and assumptions, definition of study trades, mission analysis and subsystem analyses leading to a standardized set of mission concept study products. The flexibility of the collaborative engineering design process to accommodate a wide range of study objectives from technology definition and requirements definition to preliminary design studies will be addressed. The paper will also describe the applicability of the collaborative engineering process to include an integrated systems analysis approach for evaluating the functional requirements of evolving system technologies and capabilities needed to meet the needs of future NASA programs.

Mulqueen, Jack

Conceptual design for the Space Station Freedom fluid physics/dynamics facility

A study team at NASA's Lewis Research Center has been working on a definition study and conceptual design for a fluid physics and dynamics science facility that will be located in the Space Station Freedom's baseline U.S. Laboratory module. This modular, user-friendly facility, called the Fluid Physics/Dynamics Facility, will be available for use by industry, academic, and government research communities in the late 1990's. The Facility will support research experiments dealing with the study of fluid physics and dynamics phenomena. Because of the lack of gravity-induced convection, research into the mechanisms of fluids in the absence of gravity will help to provide a better understanding of the fundamentals of fluid processes. This document has been prepared as a final version of the handout for reviewers at the Fluid Physics/Dynamics Facility Assessment Workshop held at Lewis on January 24 and 25, 1990. It covers the background, current status, and future activities of the Lewis Project Study Team effort. It is a revised and updated version of a document entitled 'Status Report on the Conceptual Design for the Space Station Fluid Physics/Dynamics Facility', dated January 1990.

Thompson, Robert L.

A PI’s Guide to Analog Research

Congratulation on being awarded a grant to conduct research in a spaceflight analog! NASA funded research in a Human Research Program (HRP) managed analog environment is very different from research in a traditional laboratory. This presentation will provide a guide to help investigators successfully plan studies for integration and implementation in an HRP analog platform. There are many things to consider when planning a study for implementation in an analog facility and campaign or mission. How do you get from grant approval to data analysis? This is where HRP’s Research Operations and Integration (ROI) team comes in. The ROI team works with sponsoring HRP elements and PI teams to capture requirements and help the PI teams through the phases of research complement development, integration and implementation. A complement is comprised of a group of studies requiring a common platform and/or scenario that are able to be integrated on a noninterference basis for implementation. Properly defining and documenting requirements and study needs is crucial in successful integration and implementation. This presentation will outline and provide the information needed for PI teams to understand the integration process and the role of the ROI team in the successful integration and implementation of their study. Topics to be discussed will include but not be limited to science requirement definition and documentation, NASA IRB submissions, subject recruitment, screening and selection, study integration process, efficiency in data collection and data sharing, daily crew schedules, hardware and software shipping, receipt and checkout, biological sample collection, mission support, data management and receipt of data.

B. Caldwell

Standardization of the Definitions of Vertical Resolution and Uncertainty in the NDACC-archived Ozone and Temperature Lidar Measurements

The international Network for the Detection of Atmospheric Composition Change (NDACC) is a global network of high-quality, remote-sensing research stations for observing and understanding the physical and chemical state of the Earth atmosphere. As part of NDACC, over 20 ground-based lidar instruments are dedicated to the long-term monitoring of atmospheric composition and to the validation of space-borne measurements of the atmosphere from environmental satellites such as Aura and ENVISAT. One caveat of large networks such as NDACC is the difficulty to archive measurement and analysis information consistently from one research group (or instrument) to another [1][2][3]. Yet the need for consistent definitions has strengthened as datasets of various origin (e.g., satellite and ground-based) are increasingly used for intercomparisons, validation, and ingested together in global assimilation systems.In the framework of the 2010 Call for Proposals by the International Space Science Institute (ISSI) located in Bern, Switzerland, a Team of lidar experts was created to address existing issues in three critical aspects of the NDACC lidar ozone and temperature data retrievals: signal filtering and the vertical filtering of the retrieved profiles, the quantification and propagation of the uncertainties, and the consistent definition and reporting of filtering and uncertainties in the NDACC- archived products. Additional experts from the satellite and global data standards communities complement the team to help address issues specific to the latter aspect.

Detection of Atmospheric Composition Change (NDACC

Hardware Development Process for Human Research Facility Applications

The simple goal of the Human Research Facility (HRF) is to conduct human research experiments on the International Space Station (ISS) astronauts during long-duration missions. This is accomplished by providing integration and operation of the necessary hardware and software capabilities. A typical hardware development flow consists of five stages: functional inputs and requirements definition, market research, design life cycle through hardware delivery, crew training, and mission support. The purpose of this presentation is to guide the audience through the early hardware development process: requirement definition through selecting a development path. Specific HRF equipment is used to illustrate the hardware development paths. The source of hardware requirements is the science community and HRF program. The HRF Science Working Group, consisting of SCientists from various medical disciplines, defined a basic set of equipment with functional requirements. This established the performance requirements of the hardware. HRF program requirements focus on making the hardware safe and operational in a space environment. This includes structural, thermal, human factors, and material requirements. Science and HRF program requirements are defined in a hardware requirements document which includes verification methods. Once the hardware is fabricated, requirements are verified by inspection, test, analysis, or demonstration. All data is compiled and reviewed to certify the hardware for flight. Obviously, the basis for all hardware development activities is requirement definition. Full and complete requirement definition is ideal prior to initiating the hardware development. However, this is generally not the case, but the hardware team typically has functional inputs as a guide. The first step is for engineers to conduct market research based on the functional inputs provided by scientists. CommerCially available products are evaluated against the science requirements as well as modifications needed to meet program requirements. Options are consolidated and the hardware development team reaches a hardware development decision point. Within budget and schedule constraints, the team must decide whether or not to complete the hardware as an in-house, subcontract with vendor, or commercial-off-the-shelf (COTS) development. An in-house development indicates NASA personnel or a contractor builds the hardware at a NASA site. A subcontract development is completed off-site by a commercial company. A COTS item is a vendor product available by ordering a specific part number. The team evaluates the pros and cons of each development path. For example, in-bouse developments utilize existing corporate knowledge regarding bow to build equipment for use in space. However, technical expertise would be required to fully understand the medical equipment capabilities, such as for an ultrasound system. It may require additional time and funding to gain the expertise that commercially exists. The major benefit of subcontracting a hardware development is the product is delivered as an end-item and commercial expertise is utilized. On the other hand, NASA has limited control over schedule delays. The final option of COTS or modified COTS equipment is a compromise between in-house and subcontracts. A vendor product may exist that meets all functional requirements but req uires in-house modifications for successful operation in a space environment. The HRF utilizes equipment developed using all of the paths described: inhouse, subcontract, and modified COTS.

Bauer, Liz

South Atlantic Anomaly Entry and Exit as Measured by the X-Ray Timing Explorer

The Rossi X-ray Timing Explorer (RXTE) carries instruments that must switch off high voltages (HV) when passing through the South Atlantic Anomaly (SAA). The High Energy X-ray Timing Experiment (HEXTE) contains a particle monitor that detects the increased particle flux associated with the SAA and autonomously reduces its voltage. The Proportional Counter Array (PCA) relies on uplinked predictions of SAA entry/exit times based on ephemeris data provided by the Flight Dynamics Facility. A third instrument, the All-Sky Monitor (ASM) also uses a predicted SAA model to reduce voltage when passing through the SAA. Data collected from the HEXTE particle monitor, as well as other instrument readings near the times of SAA entry/exit offer the potential for refining models of the boundaries of the SAA. The SAA has an increased particle flux which causes high rates of detection in the RXTE instruments designed to observe x-rays. The high counting rates could degrade the PCA if HV is not reduced during SAA passages. On the other hand, PCA downtime can be minimized and the science return can be optimized by having the best possible model of the SAA boundary. Thus, the PCA team planned an extensive effort during in-orbit checkout to utilize both the HEXTE particle monitor data and instrument counting rates to refine the model of the SAA boundary. The times of SAA entry and exit are compared with the definitive epemeris to determine the precise location (latitude and longitude) of the SAA boundary. Over time, the SAA and its perimeter were mapped. The RXTE Science Operations Center is continuously working to feed back the results of this effort into the science scheduling process, improving the SAA model as it affects the RXTE instruments, thus obtaining more accurate estimates of the SAA entry/exit times.

Smith, Evan

Integration and use of Microgravity Research Facility: Lessons learned by the crystals by vapor transport experiment and Space Experiments Facility programs

The Crystals by Vapor Transport Experiment (CVTE) and Space Experiments Facility (SEF) are materials processing facilities designed and built for use on the Space Shuttle mid deck. The CVTE was built as a commercial facility owned by the Boeing Company. The SEF was built under contract to the UAH Center for Commercial Development of Space (CCDS). Both facilities include up to three furnaces capable of reaching 850 C minimum, stand-alone electronics and software, and independent cooling control. In addition, the CVTE includes a dedicated stowage locker for cameras, a laptop computer, and other ancillary equipment. Both systems are designed to fly in a Middeck Accommodations Rack (MAR), though the SEF is currently being integrated into a Spacehab rack. The CVTE hardware includes two transparent furnaces capable of achieving temperatures in the 850 to 870 C range. The transparent feature allows scientists/astronauts to directly observe and affect crystal growth both on the ground and in space. Cameras mounted to the rack provide photodocumentation of the crystal growth. The basic design of the furnace allows for modification to accommodate techniques other than vapor crystal growth. Early in the CVTE program, the decision was made to assign a principal scientist to develop the experiment plan, affect the hardware/software design, run the ground and flight research effort, and interface with the scientific community. The principal scientist is responsible to the program manager and is a critical member of the engineering development team. As a result of this decision, the hardware/experiment requirements were established in such a way as to balance the engineering and science demands on the equipment. Program schedules for hardware development, experiment definition and material selection, flight operations development and crew training, both ground support and astronauts, were all planned and carried out with the understanding that the success of the program science was as important as the hardware functionality. How the CVTE payload was designed and what it is capable of, the philosophy of including the scientists in design and operations decisions, and the lessons learned during the integration process are descussed.

Heizer, Barbara L.

Research Issues in Image Registration for Remote Sensing

Image registration is an important element in data processing for remote sensing with many applications and a wide range of solutions. Despite considerable investigation the field has not settled on a definitive solution for most applications and a number of questions remain open. This article looks at selected research issues by surveying the experience of operational satellite teams, application-specific requirements for Earth science, and our experiments in the evaluation of image registration algorithms with emphasis on the comparison of algorithms for subpixel accuracy. We conclude that remote sensing applications put particular demands on image registration algorithms to take into account domain-specific knowledge of geometric transformations and image content.

Eastman, Roger D.

Life sciences payload definition and integration study, task C and D. Volume 2: Payload definition, integration, and planning studies

The Life Sciences Payload Definition and Integration Study was composed of four major tasks. Tasks A and B, the laboratory definition phase, were the subject of prior NASA study. The laboratory definition phase included the establishment of research functions, equipment definitions, and conceptual baseline laboratory designs. These baseline laboratories were designated as Maxi-Nom, Mini-30, and Mini-7. The outputs of Tasks A and B were used by the NASA Life Sciences Payload Integration Team to establish guidelines for Tasks C and D, the laboratory integration phase of the study. A brief review of Tasks A and B is presented provide background continuity. The tasks C and D effort is the subject of this report. The Task C effort stressed the integration of the NASA selected laboratory designs with the shuttle sortie module. The Task D effort updated and developed costs that could be used by NASA for preliminary program planning.

Source record

Space Mission Concept Development Using Concept Maturity Levels

Over the past five years, pre-project formulation experts at the Jet Propulsion Laboratory (JPL) has developed and implemented a method for measuring and communicating the maturity of space mission concepts. Mission concept development teams use this method, and associated tools, prior to concepts entering their Formulation Phases (Phase A/B). The organizing structure is Concept Maturity Level (CML), which is a classification system for characterizing the various levels of a concept's maturity. The key strength of CMLs is the ability to evolve mission concepts guided by an incremental set of assessment needs. The CML definitions have been expanded into a matrix form to identify the breadth and depth of analysis needed for a concept to reach a specific level of maturity. This matrix enables improved assessment and communication by addressing the fundamental dimensions (e.g., science objectives, mission design, technical risk, project organization, cost, export compliance, etc.) associated with mission concept evolution. JPL's collaborative engineering, dedicated concept development, and proposal teams all use these and other CML-appropriate design tools to advance their mission concept designs. This paper focuses on mission concept's early Pre-Phase A represented by CMLs 1- 4. The scope was limited due to the fact that CMLs 5 and 6 are already well defined based on the requirements documented in specific Announcement of Opportunities (AO) and Concept Study Report (CSR) guidelines, respectively, for competitive missions; and by NASA's Procedural Requirements NPR 7120.5E document for Projects in their Formulation Phase.

Concept Maturity Levels (CMLs)

Polar Gateways Arctic Circle Sunrise Conference 2008, Barrow, Alaska: IHY-IPY Outreach on Exploration of Polar and Icy Worlds in the Solar System

Polar, heliophysical, and planetary science topics related to the International Heliophysical and Polar Years 2007-2009 were addressed during this circumpolar video conference hosted January 23-29, 2808 at the new Barrow Arctic Research Center of the Barrow Arctic Science Consortium in Barrow, Alaska. This conference was planned as an IHY-IPY event science outreach event bringing together scientists and educational specialists for the first week of sunrise at subzero Arctic temperatures in Barrow. Science presentations spanned the solar system from the polar Sun to Earth, Moon, Mars, Jupiter, Saturn, and the Kuiper Belt. On-site participants experienced look and feel of icy worlds like Europa and Titan by being in the Barrow tundra and sea ice environment and by going "on the ice" during snowmobile expeditions to the near-shore sea ice environment and to Point Barrow, closest geographic point in the U.S. to the North Pole. Many science presentations were made remotely via video conference or teleconference from Sweden, Norway, Russia, Canada, Antarctica, and the United States, spanning up to thirteen time zones (Alaska to Russia) at various times. Extensive educational outreach activities were conducted with the local Barrow and Alaska North Slope communities and through the NASA Digital Learning Network live from the "top of the world" at Barrow. The Sun- Earth Day team from Goddard, and a videographer from the Passport to Knowledge project, carried out extensive educational interviews with many participants and native Inupiaq Eskimo residents of Barrow. Video and podcast recordings of selected interviews are available at http://sunearthday.nasa.gov/2008/multimedidpodcasts.php. Excerpts from these and other interviews will be included in a new high definition video documentary called "From the Sun to the Stars: The New Science of Heliophysics" from Passport to Knowledge that will later broadcast on NASA TV and other educational networks. Full conference proceedings are accessible at http://polargateways2008.org/.

Cooper, John F.

Artificial Intelligence (AI) Methods for Automating the Impact Tool Evidence Library

INTRODUCTION: The development of the Evidence Library for use with the IMPACT (Informing Mission Planning via Analysis of Complex Tradespaces) probability risk assessment tool involved a multilayered, time intensive process of data collection and analysis by subject matter experts from the Exploration Medical Capability (ExMC) Element Clinical and Science Team to produce clinical findings forms (CliFFs) for 120 medical conditions. Artificial Intelligence Large Language Models (LLMs) can be leveraged to facilitate this process, thus reducing labor and time. TOPIC: CliFFs contain information about medical conditions as they pertain to spaceflight. This includes condition definitions, incidence data, crew task impairment estimates caused by conditions, treatment protocols and references to literature used for gathering condition evidence. Guided by the Evidence Library Methods document and the CliFF development instructions, a team has leveraged Microsoft Azure AI services and open-source documentation to construct an AI-assisted automated pipeline for CliFF development. This process is designed to search, retrieve, and evaluate the applicable data, and ultimately generate a completed CliFF. The LLM evaluates the relevance of each of the source materials to spaceflight, either as direct evidence or as an analog. The model extracts keywords and generates brief summaries to enhance search and retrieval in later stages of CliFF development. For instance, it can calculate epidemiological statistical data, such as incidence rates and the likelihood of best or worst-case scenarios. APPLICATION: Large Language Models (LLMs) can efficiently summarize large amounts of text. Leveraging this technology will automate data retrieval and evidence gathering for medical databases, like the IMPACT tool, by aiding in the labor-intensive process of analyzing large bodies of literature and organizing it into a formatted document like a CliFF. This added efficiency will enable expeditious expansion of the Evidence Library with additional medical conditions and update previous CLiFFs as new technology becomes available.

Ali Al

The Goddard High Resolution Spectrograph Scientific Support Contract

In 1988, Computer Sciences Corporation (CSC) was selected as the Goddard High Resolution Spectrograph (GHRS) Scientific Support Contractor (SSC). This was to have been a few months before the launch of NASA's first Great Observatory, the Hubble Space Telescope (HST). As one of five scientific instruments on HST, the GHRS was designed to obtain spectra in the 1050-3300 A ultraviolet wavelength region with a resolving power, lambda/Delta(lambda) , of up to 100,000 and relative photometric accuracy to 1%. It was built by Ball AeroSpace Systems Group under the guidance of the GHRS Investigation Definition Team (IDT), comprised of 16 scientists from the US and Canada. After launch, the IDT was to perform the initial instrument calibration and execute a broad scientific program during a five-year Guaranteed Time Observation (GTO) period. After a year's delay, the launch of HST occurred in April 1990, and CSC participated in the in-orbit calibration and first four years of GTO observations with the IDT. The HST primary mirror suffered from spherical aberration, which reduced the spatial and spectral resolution of Large Science Aperture (LSA) observations and decreased the throughput of the Small Science Aperture (SSA) by a factor of two. Periodic problems with the Side 1 carrousel electronics and anomalies with the low-voltage power supply finally resulted in a suspension of the use of Side 1 less than two years after launch. At the outset, the GHRS SSC task involved work in four areas: 1) to manage and operate the GHRS Data Analysis Facility (DAF); 2) to support the second Servicing Mission Observatory Verification (SMOV) program, as well as perform system engineering analysis of the GHRS as nesessary; 3) to assist the GHRS IDT with their scientific research programs, particularly the GSFC members of the team, and 4) to provide administrative and logistic support for GHRS public information and educational activities.

Source record

Stellar Interferometer Technology Experiment (SITE)

The MIT Space Engineering Research Center and the Jet Propulsion Laboratory stand ready to advance science sensor technology for discrete-aperture astronomical instruments such as space-based optical interferometers. The objective of the Stellar Interferometer Technology Experiment (SITE) is to demonstrate system-level functionality of a space-based stellar interferometer through the use of enabling and enhancing Controlled-Structures Technologies (CST). SITE mounts to the Mission Peculiar Experiment Support System inside the Shuttle payload bay. Starlight, entering through two apertures, is steered to a combining plate where it is interferred. Interference requires 27 nanometer pathlength (phasing) and 0.29 archsecond wavefront-tilt (pointing) control. The resulting 15 milli-archsecond angular resolution exceeds that of current earth-orbiting telescopes while maintaining low cost by exploiting active optics and structural control technologies. With these technologies, unforeseen and time-varying disturbances can be rejected while relaxing reliance on ground alignment and calibration. SITE will reduce the risk and cost of advanced optical space systems by validating critical technologies in their operational environment. Moreover, these technologies are directly applicable to commercially driven applications such as precision matching, optical scanning, and vibration and noise control systems for the aerospace, medical, and automotive sectors. The SITE team consists of experienced university, government, and industry researchers, scientists, and engineers with extensive expertise in optical interferometry, nano-precision opto-mechanical control and spaceflight experimentation. The experience exists and the technology is mature. SITE will validate these technologies on a functioning interferometer science sensor in order to confirm definitely their readiness to be baselined for future science missions.

Crawley, Edward F.

Genesis Solar Wind – Capture, Return, Curate and Analyze: Looking Backward and Creating a Timeline

Introduction: In 1997 NASA’S Discovery Program selected the Genesis mission proposal to return solar wind samples to Earth for laboratory analyses. Principal Investigator Donald S. Burnett and the science team defined the purity of collector materials and ability to analyze solar wind composition to the precision required for planetary science. As a small mission, focused on a well-defined science goal, yet needing careful attention to engineering details, the communication among scientists and engineers, nurtured by Don Burnett, was exceptional. Genesis Mission and Curation Legacy: Genesis, as the first U. S. spacecraft to return astromaterial samples since Apollo, not only integrated the mission planning and flight teams, but also the science and sample curation teams during the mission development period. Since Genesis is a sample return mission, the Science Team was essential in certifying the collectors (sample containers for solar atoms). From inception, Genesis established mission funding for returned sample curation. JSC was lead in contamination control during mission preparation, including establishment of an ISO 4 cleanroom facility and use of ultrapure water (UPW) for cleaning flight hardware (and, as it turned out, for cleaning collectors after the mishap). Reliable, fast communication among scientists, engineers and curators at the hands-on level established deep respect among team members and efficient decision-making. JSC’s 50-years of astromaterial sample curation provided experienced sample processors onsite during recovery in Utah (a deep bench for emergency response). Post-recovery curation included iterative collaboration with science sample users to clean or verify cleanliness of samples. The science legacy from Genesis is addressed by Burnett and Jurewicz, this volume. In The Beginning: After Apollo sample return, Burnett and Marcia Neugebauer at JPL began discussing a solar wind sample return, with Neugebauer arguing that separate collection of solar wind regimes was essential science. By 1992 a solar wind sample return mission was presented at a workshop, and by 1994 a mission was proposed named Suess-Urey. The mission was re-proposed under a new name GENESIS and selected in 1997. Susan Niebur captured the Genesis mission history and stories, from high level management documents and from many interviews with participants [2]. Her account lets readers glimpse personality of participants in quotations from interviews. Need and Scope for Detailed Technical Timeline: A timeline constructed from lower level task documents has been initiated to document the resources and skills actually used, as well as task sequence or concurrency. Timelines for high level mission events are captured in two documents [1] [2] and for detailed re-entry events in [3]. A detailed technical timeline for Genesis mission and curation activities will provide data points for lower level tasks, such as ISO 4 curation facility construction time, preparation for nominal sample field recovery, mishap recovery, and UPW expansion. Changes in technology context 1990-2024: Semiconductor technologies were easily accessible in the U.S.A. (1990-1999), and the Genesis team used those resources for cleanroom design and UPW system expansion. Image documentation was changing from film to digital during cleanroom construction and payload cleaning (1997-2001). Engineering design was done using computer aided design proprietary software, making more difficult the archiving of payload configuration and materials. Email of documents, tracked delivery service and virtual meeting capability greatly improved communication efficiency. Information sources – Pre-launch mission preparation: Examples of mission science, engineering and contamination control are collector purity testing, payload design/fabrication and ISO 4 cleanroom construction. Information on timing of these activities comes from facility readiness reviews, management reviews, shipping documents, procurement documents, test reports, travel documents, laboratory logs, Quality Assurance documents, dates on images, participant notebooks and emails. Information sources – Sample return re-entry and field recovery activities: Information comes from event timelines produced by Mid-Air Recovery team, Lockheed team lead notes and from chase video, JPL Quality Assurance. Information also comes from images and logbooks from UTTR cleanroom operations and from curatorial documents. Information sources – Resulting science and sample cleaning processes: Agendas from the annual gatherings of the science team initially trace testing for collector purity/cleanliness, and after sample recovery, include collector cleaning and cleanliness assessment. Post-recovery documents include curatorial orders and procedures, sample allocation documents and LPSC abstracts. Timeline Objectives: A simple spreadsheet timeline with headers DATE, EVENT, PEOPLE, COMMENT, INFORMATION SOURCE has been initiated and currently has over 90 entries. While this is not definitive historical research, it is a quick look at the evolution of Genesis curation with pointers to documents or people with information. Engineers for future missions may find useful points of comparison for development of facilities. References:[1] Genesis Mission Reference Document, (2011) JPL D-62382.[2] Niebur S. M., edited by Brown D. W. (2023) NASA’s Discovery Program: The First 20 Years of Competitive Planetary Exploration, NASA-SP-2023-4238.[3] Genesis Mishap Investigation Board Report, Vol. 1 (July 2005).

solar wind

Gateway Payload Users Guide

This Gateway Payload Users Guide is provided as an introduction to science operations on the Gateway for potential Payload Developer (PD) teams. It is not intended to be a comprehensive guide that answers detailed questions that may arise. More detailed information and resources will be provided as PD teams work toward launch and flight operations. This document does not contain payload or system requirements. Payload requirements are contained in GP-10037: Gateway Payload Interface Definition Document. Applicable requirements from GP-10037 will be derived into payload-specific requirements documents.

utilization