Collection of biological information during prolonged flight missions with ''yes and no'' data reduction analysis
Flight mission data recording in binary code on magnetic tape or punched paper tape
DATA RECORDING↗
SEARCH · Search NASA
Results for “Missions Data”
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.
TRMM Version 7 Near-Realtime Data Products
The TRMM data system has been providing near-realtime data products to the community since late 1999. While the TRMM project never had near-realtime production requirements, the science and applications communities had a great interest in receiving TRMM data as quickly as possible. As a result these NRT data are provided under a best-effort scenario but with the objective of having the swath data products available within three hours of data collection 90% of the time. In July of 2011 the Joint Precipitation Measurement Missions Science Team (JPST) authorized the reprocessing of TRMM mission data using the new version 7 algorithms. The reprocessing of the 14+ years of the mission was concluded within 30 days. Version 7 algorithms had substantial changes in the data product file formats both for data and metadata. In addition, the algorithms themselves had major modifications and improvements. The general approach to versioning up the NRT is to wait for the regular production algorithms to have run for a while and shake out any issues that might arise from the new version before updating the NRT products. Because of the substantial changes in data/metadata formats as well as the algorithm improvements themselves, the update of NRT to V7 followed an even more conservative path than usual. This was done to ensure that applications agencies and other users of the TRMM NRT would not be faces with short-timeframes for conversion to the new format. This paper will describe the process by which the TRMM NRT was updated to V7 and the V7 data products themselves.
Tocker, Erich Franz↗
Cooperative Lander-Surface/Aerial Microflyer Missions for Mars Exploration
Concepts are being investigated for exploratory missions to Mars based on Bioinspired Engineering of Exploration Systems (BEES), which is a guiding principle of this effort to develop biomorphic explorers. The novelty lies in the use of a robust telecom architecture for mission data return, utilizing multiple local relays (including the lander itself as a local relay and the explorers in the dual role of a local relay) to enable ranges ~10 to 1,000 km and downlink of color imagery. As illustrated in Figure 1, multiple microflyers that can be both surface or aerially launched are envisioned in shepherding, metamorphic, and imaging roles. These microflyers imbibe key bio-inspired principles in their flight control, navigation, and visual search operations. Honey-bee inspired algorithms utilizing visual cues to perform autonomous navigation operations such as terrain following will be utilized. The instrument suite will consist of a panoramic imager and polarization imager specifically optimized to detect ice and water. For microflyers, particularly at small sizes, bio-inspired solutions appear to offer better alternate solutions than conventional engineered approaches. This investigation addresses a wide range of interrelated issues, including desired scientific data, sizes, rates, and communication ranges that can be accomplished in alternative mission scenarios. The mission illustrated in Figure 1 offers the most robust telecom architecture and the longest range for exploration with two landers being available as main local relays in addition to an ephemeral aerial probe local relay. The shepherding or metamorphic plane are in their dual role as local relays and image data collection/storage nodes. Appropriate placement of the landing site for the scout lander with respect to the main mission lander can allow coverage of extremely large ranges and enable exhaustive survey of the area of interest. In particular, this mission could help with the path planning and risk mitigation in the traverse of the long-distance surface explorer/rover. The basic requirements of design and operation of BEES to implement the scenarios are discussed. Terrestrial applications of such concepts include distributed aerial/surface measurements of meteorological events, i.e., storm watch, seismic monitoring, reconnaissance, biological chemical sensing, search and rescue, surveillance, autonomous security/ protection agents, and/or delivery and lateral distribution of agents (sensors, surface/subsurface crawlers, clean-up agents). Figure 2 illustrates an Earth demonstration that is in development, and its implementation will illustrate the value of these biomorphic mission concepts.
Thakoor, Sarita↗
Autonomous Data Transfer Operations for Missions
Automating the data transfer operation can significantly reduce the cost of moving data from a spacecraft to a location on Earth. Automated data transfer methods have been developed for the terrestrial Internet. However, they often do not apply to the space environment, since in general they are based on assumptions about connectivity that are true on the Internet but not on space links. Automated file transfer protocols have been developed for use over space links that transfer data via store-and-forward of files or segments of files. This paper investigates some of the operational concepts made possible by these protocols.
Repaci, Max↗
An Analysis of Shuttle Crew Scheduling Violations
From the early years of the Space Shuttle program, National Aeronautics and Space Administration (NASA) Shuttle crews have had a timeline of activities to guide them through their time on-orbit. Planners used scheduling constraints to build timelines that ensured the health and safety of the crews. If a constraint could not be met it resulted in a violation. Other agencies of the federal government also have scheduling constraints to ensure the safety of personnel and the public. This project examined the history of Space Shuttle scheduling constraints, constraints from Federal agencies and branches of the military and how these constraints may be used as a guide for future NASA and private spacecraft. This was conducted by reviewing rules and violations with regard to human aerospace scheduling constraints, environmental, political, social and technological factors, operating environment and relevant human factors. This study includes a statistical analysis of Shuttle Extra Vehicular Activity (EVA) related violations to determine if these were a significant producer of constraint violations. It was hypothesized that the number of SCSC violations caused by EVA activities were a significant contributor to the total number of violations for Shuttle/ISS missions. Data was taken from NASA data archives at the Johnson Space Center from Space Shuttle/ISS missions prior to the STS-107 accident. The results of the analysis rejected the null hypothesis and found that EVA violations were a significant contributor to the total number of violations. This analysis could help NASA and commercial space companies understand the main source of constraint violations and allow them to create constraint rules that ensure the safe operation of future human private and exploration missions. Additional studies could be performed to evaluate other variables that could have influenced the scheduling violations that were analyzed.
Bristol, Douglas↗
NASA's Asteroid Redirect Mission: A Robotic Boulder Capture Option for Science, Human Exploration, Resource Utilization, and Planetary Defense
NASA is examining two options for the Asteroid Redirect Mission (ARM), which will return asteroid material to a Lunar Distant Retrograde Orbit (LDRO) using a robotic solar electric propulsion spacecraft, called the Asteroid Redirect Vehicle (ARV). Once the ARV places the asteroid material into the LDRO, a piloted mission will rendezvous and dock with the ARV. After docking, astronauts will conduct two extravehicular activities (EVAs) to inspect and sample the asteroid material before returning to Earth. One option involves capturing an entire small (~4 - 10 m diameter) near-Earth asteroid (NEA) inside a large inflatable bag. However, NASA is also examining another option that entails retrieving a boulder (~1 - 5 m) via robotic manipulators from the surface of a larger (~100+ m) pre-characterized NEA. The Robotic Boulder Capture (RBC) option can leverage robotic mission data to help ensure success by targeting previously (or soon to be) well- characterized NEAs. For example, the data from the Japan Aerospace Exploration Agency's (JAXA) Hayabusa mission has been utilized to develop detailed mission designs that assess options and risks associated with proximity and surface operations. Hayabusa's target NEA, Itokawa, has been identified as a valid target and is known to possess hundreds of appropriately sized boulders on its surface. Further robotic characterization of additional NEAs (e.g., Bennu and 1999 JU3) by NASA's OSIRIS REx and JAXA's Hayabusa 2 missions is planned to begin in 2018. This ARM option reduces mission risk and provides increased benefits for science, human exploration, resource utilization, and planetary defense. Science: The RBC option is an extremely large sample-return mission with the prospect of bringing back many tons of well-characterized asteroid material to the Earth-Moon system. The candidate boulder from the target NEA can be selected based on inputs from the world-wide science community, ensuring that the most scientifically interesting boulder be returned for subsequent sampling. In addition, the material surrounding the boulder can be collected from the surface, thus providing geological contextual information and additional samples of NEA regolith. The robotic manipulators used for capturing the boulder will ensure some of the surface remains undisturbed and that the boulder will retain its structural integrity, which will preserve the context of any samples collected by the astronauts and ensure a high level of science return. Human Exploration: Due to the coherent nature of the boulder that will be collected, entire encapsulation of the asteroid material is not required. This facilitates exploration and sample collection of the boulder by astronauts in a variety of ways. The total time for EVA during the crew portion of the mission is very limited. Current estimates are that each of the two EVAs will only last four hours. The RBC option will allow crew members to have good situational awareness of the work site and quickly identify sample sites of interest. In addition, the samples to be collected can be readily accessed without having to deal with removal of an encapsulation system, which adds extra complexity and risk for the astronauts during EVA. Resource Utilization: One of the most crucial aspects for resource utilization is the identification and collection of appropriate materials (e.g., volatiles, organics, metals, etc.) that contain components of interest. Prior characterization of NEAs is required in order to increase the likelihood that appropriate materials will be returned. Ground-based observations of small (<10 m) NEAs are challenging, but characterization efforts of larger targets have demonstrated that NEAs with volatiles and organics have been identified. Two potential targets for the RBC option (Bennu and 1999 JU3) have been previously identified as potentially rich in resources, and both are already targets of currently planned robotic missions that will characterize their physical properties in great detail. Planetary Defense: The RBC option involves interaction with a well- characterized potentially hazardoussized NEA that would enable NASA to conduct one or more planetary defense demonstrations. The primary method would use the collected boulder to augment the mass of the ARV and perform an Enhanced Gravity Tractor (EGT) demonstration on the NEA. Additionally, other approaches could be demonstrated during the mission, such as Ion Beam Deflection (IBD) and/or observation of a Kinetic Impactor (KI). The relative effectiveness of a slow push-pull method such as the EGT or IBD could be directly compared and contrasted with the results of the more energetic KI method on the target NEA. Conclusions: This boulder option for NASA's ARM can leverage knowledge of previously characterized NEAs from prior robotic missions, which provides more certainty of the target NEA's physical characteristics and reduces mission risk. This increases the return on investment for NASA's future activities with respect to human exploration, resource utilization, and planetary defense.
Abell, P.↗
NASA SNPP SIPS - Following in the Path of EOS
NASA's Earth Science Data Information System (ESDIS) Project has been operating NASA's Suomi National Polar-Orbiting Partnership (SNPP) Science Data Segment (SDS) since the launch in October 2011. At launch, the SDS focused primarily on the evaluation of Sensor Data Records (SDRs) and Environmental Data Records (EDRs) produced by the Joint Polar Satellite System (JPSS), a National Oceanic and Atmosphere Administration (NOAA) Program, as to their suitability for Earth system science. During the summer of 2014, NASA transitioned to the production of standard Earth Observing System (EOS)-like science products for all instruments aboard Suomi NPP. The five Science Investigator-led Processing Systems (SIPS): Land, Ocean, Atmosphere, Ozone, and Sounder were established to produce the NASA SNPP standard Level 1, Level 2, and global Level 3 products developed by the SNPP Science Teams and to provide the products to NASA's Distributed Active Archive Centers (DAACs) for archive and distribution to the user community. The processing, archiving and distribution of data from NASA's Clouds and the Earth's Radiant Energy System (CERES) and Ozone Mapper/Profiler Suite (OMPS) Limb instruments will continue. With the implementation of the JPSS Block 2 architecture and the launch of JPSS-1, the SDS will receive SNPP data in near real-time via the JPSS Stored Mission Data Hub (JSH), as well as JPSS-1 and future JPSS-2 data. The SNPP SIPS will ingest EOS compatible Level 0 data from the EOS Data Operations System (EDOS) element for their data processing, enabling the continuous EOS-SNPP-JPSS Satellite Data Record.
near real time↗
Connecting Projects to Complete the In Situ Resource Utilization Paradigm
Terrain Identify specifics such as slope, rockiness, traction parameters Identify what part of ISRU needs each Physical Geotechnical Hardness, density, cohesion, etc. Identify what part of ISRU needs each (e.g., excavation needs to know hardness, density; soil processing needs to know density, cohesion; etc.)Mineral Identify specifics Identify what part of ISRU needs each Volatile Identify specifics Identify what part of ISRU needs each Atmosphere Identify specifics Identify what part of ISRU needs each Environment Identify specifics Identify what part of ISRU needs each Resource Characterization What: Develop an instrument suite to locate and evaluate the physical, mineral, and volatile resources at the lunar poles Neutron Spectrometer Near Infrared (IR) to locate subsurface hydrogen surface water Near IR for mineral identification Auger drill for sample removal down to 1 m Oven with Gas Chromatograph Mass Spectrometer to quantify volatiles present ISRU relevance: Water volatile resource characterization and subsurface material access removal Site Evaluation Resource Mapping What: Develop and utilize new data products and tools for evaluating potential exploration sites for selection and overlay mission data to map terrain, environment, and resource information e.g., New techniques applied to generate Digital Elevation Map (DEMs) at native scale of images (1mpxl)ISRU relevance: Resource mapping and estimation with terrain and environment information is needed for extraction planning Mission Planning and Operations What: Develop and utilize tools and procedures for planning mission operations and real time changes Planning tools include detailed engineering models (e.g., power and data) of surface segment systems allows evaluation of designs ISRU relevance: Allows for iterative engineering as a function of environment and hardware performance.
Paradigm↗
Telemetry data processing plan for the OGO-A MISSION
Telemetry data processing plan for OGO-A MISSION - pulse code modulation digital and analog data techniques - ground data acquisition system
PULSE CODE MODULATION /PCM/↗
HCMM hydrological analysis in Utah
Data reduction and preliminary comparisons and correlations of Heat Capacity Mapping Mission data to ground truth measurements were made. The data covered Utah Lake and the surrounding area. Output modes include a digital hard copy record of the intensity value for each pixel and color graphics. Analyses of non-diatom net plankton (algae), turbidity, nitrogen, phosphorus, and temperatures were made. In addition, infrared data for the agricultural area around Utah lake were also preliminarily examined and compared to depth to groundwater data.
Source record↗
Configuration and Implementation
The main objectives of a Planetary Data System (PDS) are to curate planetary data - that is to store and maintain complete planetary data sets and the necessary supporting documentation to make them useful - and to facilitate scientific study of these data through improved organization and access. A hardware system, no matter how sophisticated and supportive, cannot replace the live colleague interaction needed for good science.System users with only a general knowledge of a data file or data set will need guidance in determining whether that data is most appropriate to support a theory. The PDS is meant to allow easy access to data, to provide useful presentations of that data, and to facilitate data analysis; however it is not designed to supercede the critical examination and interactions that data analysis requires. The Planetary Data System will be a powerful research tool which allows the entire planetary science community access to a complete data and will facilitate the archiving of pass, current, and future mission data sets.
Source record↗
Advanced propulsion for polar-orbiting and coorbiting free flyers
Advanced propulsion systems for polar-orbiting and coorbiting free flyers were investigated. Resistojet, arcjet, ion, magnetoplasmadynamic and chemical-bipropellant nitrogen tetroxide/monomethyl hydrazine (NTO/MMH) propulsion systems were compared to the baseline free-flyer hydrazine (N2H4)-propulsion-system performance. Advanced resistojet, arcjet, ion, and NTO/MMH propulsion systems enable significant propellant-mass savings over the baseline N2H4-propulsion system. Using free-flyer mission requirements from the Langley Research Center Mission-Data Base, detailed propulsion requirements for over thirty free-flyer missions were analyzed. The Polar-Platform trip-time constraints may preclude using a low-thrust electric-propulsion system. Electric propulsion will, however, allow a significant coorbiter propellant-mass reduction. Frequent servicing and nodal-regression effects on the coorbiting free-flyer's orbit increase the required mission velocity change and propellant mass. For many coorbiter missions high-specific-impulse resistojet-, arcjet- and ion-propulsion systems allow substantial life-cycle propellant-mass savings.
Palaszewski, B. A.↗
Catalogs of Space Shuttle earth observations photography
A review is presented of postflight cataloging and indexing activities of mission data obtained from Space Shuttle earth observations photography. Each Space Shuttle mission acquires 1300-4400 photographs of the earth that are reviewed and interpreted by a team of photointerpreters and cataloging specialists. Every photograph's manual and electronic set of plots is compared for accuracy of its locational coordinates. This cataloging activity is a critical and principal part of postflight activity and ensures that the database is accurate, updated and consequently made meaningful for further utilization in the applications and research communities. A final product in the form of a Catalog of Space Shuttle Earth Observations Handheld Photography is published for users of this database.
Lulla, Kamlesh↗
TMBM: Tethered Micro-Balloons on Mars
The use of balloons/aerobots on Mars has been under consideration for many years. Concepts include deployment during entry into the atmosphere from a carrier spacecraft, deployment from a lander, use of super-pressurized systems for long duration flights, 'hot-air' systems, etc. Principal advantages include the ability to obtain high-resolution data of the surface because balloons provide a low-altitude platform which moves relatively slowly. Work conducted within the last few years has removed many of the technical difficulties encountered in deployment and operation of balloons/aerobots on Mars. The concept proposed here (a tethered balloon released from a lander) uses a relatively simple approach which would enable aspects of Martian balloons to be tested while providing useful and potentially unique science results. Tethered Micro-Balloons on Mars (TMBM) would be carried to Mars on board a future lander as a stand-alone experiment having a total mass of one to two kilograms. It would consist of a helium balloon of up to 50 cubic meters that is inflated after landing and initially tethered to the lander. Its primary instrumentation would be a camera that would be carried to an altitude of up to tens of meters above the surface. Imaging data would be transmitted to the lander for inclusion in the mission data stream. The tether would be released in stages allowing different resolutions and coverage. In addition during this staged release a lander camera system may observe the motion of the balloon at various heights above he lander. Under some scenarios upon completion of the primary phase of TMBM operations, the tether would be cut, allowing TMBM to drift away from the landing site, during which images would be taken along the ground.
Sims, M. H.↗
GSFC Technology Thrusts and Partnership Opportunities
This slide presentation reviews the technology thrusts and the opportunities to partner in developing software in support of the technological advances at the Goddard Space Flight Center (GSFC). There are thrusts in development of end-to-end software systems for mission data systems in areas of flight software, ground data systems, flight dynamic systems and science data systems. The required technical expertise is reviewed, and the supported missions are shown for the various areas given.
Le Moigne, Jacqueline↗
NASA/ESA CV-990 Spacelab simulation. Appendixes: C, data-handling: Planning and implementation; D, communications; E, mission documentation
Data handling, communications, and documentation aspects of the ASSESS mission are described. Most experiments provided their own data handling equipment, although some used the airborne computer for backup, and one experiment required real-time computations. Communications facilities were set up to simulate those to be provided between Spacelab and the ground, including a downlink TV system. Mission documentation was kept to a minimum and proved sufficient. Examples are given of the basic documents of the mission.
Reller, J. O., Jr.↗
Apollo Lunar Sample Integration into Google Moon: A New Approach to Digitization
The Google Moon Apollo Lunar Sample Data Integration project is part of a larger, LASER-funded 4-year lunar rock photo restoration project by NASA s Acquisition and Curation Office [1]. The objective of this project is to enhance the Apollo mission data already available on Google Moon with information about the lunar samples collected during the Apollo missions. To this end, we have combined rock sample data from various sources, including Curation databases, mission documentation and lunar sample catalogs, with newly available digital photography of rock samples to create a user-friendly, interactive tool for learning about the Apollo Moon samples
Dawson, Melissa D.↗
Safe2Ditch Steer-To-Clear Development and Flight Testing
This paper describes a series of small unmanned aerial system (sUAS) flights performed at NASA Langley Research Center in April and May of 2019 to test a newly added Steer-to-Clear feature for the Safe2Ditch (S2D) prototype system. S2D is an autonomous crash management system for sUAS. Its function is to detect the onset of an emergency for an autonomous vehicle, and to enable that vehicle in distress to execute safe landings to avoid injuring people on the ground or damaging property. Flight tests were conducted at the City Environment Range for Testing Autonomous Integrated Navigation (CERTAIN) range at NASA Langley. Prior testing of S2D focused on rerouting to an alternate ditch site when an occupant was detected in the primary ditch site. For Steer-to-Clear testing, S2D was limited to a single ditch site option to force engagement of the Steer-to-Clear mode. The implementation of Steer-to-Clear for the flight prototype used a simple method to divide the target ditch site into four quadrants. An RC car was driven in circles in one quadrant to simulate an occupant in that ditch site. A simple implementation of Steer-to- Clear was programmed to land in the opposite quadrant to maximize distance to the occupant’s quadrant. A successful mission was tallied when this occurred. Out of nineteen flights, thirteen resulted in successful missions. Data logs from the flight vehicle and the RC car indicated that unsuccessful missions were due to geolocation error between the actual location of the RC car and the derived location of it by the Vision Assisted Landing component of S2D on the flight vehicle. Video data indicated that while the Vision Assisted Landing component reliably identified the location of the ditch site occupant in the image frame, the conversion of the occupant’s location to earth coordinates was sometimes adversely impacted by errors in sensor data needed to perform the transformation. Logged sensor data was analyzed to attempt to identify the primary error sources and their impact on the geolocation accuracy. Three trends were observed in the data evaluation phase. In one trend, errors in geolocation were relatively large at the flight vehicle’s cruise altitude, but reduced as the vehicle descended. This was the expected behavior and was attributed to sensor errors of the inertial measurement unit (IMU). The second trend showed distinct sinusoidal error for the entire descent that did not always reduce with altitude. The third trend showed high scatter in the data, which did not correlate well with altitude. Possible sources of observed error and compensation techniques are discussed.
Petty, Bryan J.↗