SEARCH · Search NASA
Search indexed NASA NTRS and DOE OSTI research on propulsion, heat transfer, battery materials and energy systems. Follow report and document links to the original sources.
Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.
The TeraByte Infrared Delivery (TBIRD) mission has successfully demonstrated 200-Gbps laser communication downlinks from a 6U CubeSat in low-Earth orbit (LEO), delivering up to 4.8 terabytes (TB) error-free in a 5-minute pass. In total 65 passes were performed from May 2022 through May 2023. This paper presents an overview of the results of two experimental campaigns during that year of operations.
Frequently it is necessary to distribute spacecraft telemetry to multiple destinations on Internet Protocol (IP) networks. There are various methods of delivering this data, but when the data is high rate and there are many destinations IP multicast provides the best solution from a network perspective. However, IP multicast only supports the User Datagram Protocol (UDP) which is connectionless and unreliable. This nature of UDP and by extension the low priority treatment of UDP packets by some network hardware creates a difficult environment for distribution of high rate telemetry to a number of recipients over IP networks. NACK (Negative ACKnowledgment) Oriented Reliable Multicast (NORM) is defined by IETF (Internet Engineering Task Force) RFC (Request for Comments) 5740 in 2009 by B. Adamson et al. NORM provides a mechanism of retransmission and or forward error correction for UDP packets, potentially overcoming the limits of UDP for the transmission of spacecraft telemetry. Marshall Space Flight Center’s (MSFC) Huntsville Operations Support Center (HOSC) manages the delivery of the International Space Station (ISS) payload science and health data. The ISS IP Ground Routed (IIGoR) network provides the delivery of the data from the ground stations to the control centers. HOSC personnel have been experimenting with the use of NORM on the link between the ground stations and the front end processor equipment in Huntsville, AL.
The TeraByte Infrared Delivery (TBIRD) mission has successfully demonstrated 200-Gbps laser communication downlinks from a 6U CubeSat in low-Earth orbit (LEO) and has delivered up to 4.8 terabytes (TB) error-free in a 5-minute pass. In total 65 passes have been performed since launch in May 2022, with 25 of those passes conducted in April-May 2023. The TBIRD space and ground terminals leverage commercial fiber-coupled coherent transceivers along with a custom Automatic Repeat reQuest (ARQ) protocol to ensure error-free communication through the atmospheric fading channel. This paper presents data throughput results from the on-orbit passes and an analysis of the ARQ system operation that shows that near-optimal performance was achieved. We also present results from Doppler compensation experiments that led to an increase in the data volume transferred per pass.
The TeraByte Infrared Delivery (TBIRD) mission has successfully demonstrated 200-Gbps laser communication downlinks from a 6U CubeSat in low-Earth orbit (LEO) and has delivered up to 4.8 terabytes (TB) error-free in a 5-minute pass. In total, 65 passes have been performed since launch in May 2022, with 22 of those passes conducted in April-May 2023. The TBIRD space and ground terminals leverage commercial fiber-coupled coherent transceivers along with a custom Automatic Repeat reQuest (ARQ) protocol to ensure error-free communication through the atmospheric fading channel. This paper presents data throughput results from the on-orbit passes and an analysis of the ARQ system operation that shows that near-optimal performance was achieved. Results from Doppler compensation experiments that increased the data volume per pass are also presented.
The fortedata R package is an open data notebook from the Forest Resilience Threshold Experiment (FoRTE) – a modeling and manipulative field experiment that tests the effects of disturbance severity and disturbance type on carbon cycling dynamics in a temperate forest. Package data consist of measurements of carbon pools and fluxes and ancillary measurements to help analyze and interpret carbon cycling over time. Currently the package includes data and metadata from the first three FoRTE field seasons, serves as a central, updatable resource for the FoRTE project team, and is intended as a resource for external users over the course of the experiment and in perpetuity. Further, it supports all associated FoRTE publications, analyses, and modeling efforts. This increases efficiency, consistency, compatibility, and productivity while minimizing duplicated effort and error propagation that can arise as a function of a large, distributed and collaborative effort. More broadly, fortedata represents an innovative, collaborative way of approaching science that unites and expedites the delivery of complementary datasets to the broader scientific community, increasing transparency and reproducibility of taxpayer-funded science. The fortedata package is available via GitHub: https://github.com/FoRTExperiment/fortedata (last access: 19 February 2021), and detailed documentation on the access, used, and applications of fortedata are available at https://fortexperiment.github.io/fortedata/ (last access: 19 February 2021). The first public release, version 1.0.1 is also archived at https://doi.org/10.5281/zenodo.4399601 (Atkins et al., 2020b). All data products are also available outside of the package as .csv files: https://doi.org/10.6084/m9.figshare.13499148.v1 (Atkins et al., 2020c).
This report describes work conducted on Delivery Order 181 between October 1996 through June 1997. During this period software was written to: compute axial PSD's from RDOS AXAF-I mirror surface maps; plot axial surface errors and compute PSD's from HDOS "Big 8" axial scans; plot PSD's from FITS format PSD files; plot band-limited RMS vs axial and azimuthal position for multiple PSD files; combine and organize PSD's from multiple mirror surface measurements formatted as input to GRAZTRACE; modify GRAZTRACE to read FITS formatted PSD files; evaluate AXAF-I test results; improve and expand the capabilities of the GT x-ray mirror analysis package. During this period work began on a more user-friendly manual for the GT program, and improvements were made to the on-line help manual.
The Mars Exploration Rover project consisted of two missions (MER-A: spirit rover and MER-B: opportunity rover) that launched spacecraft on June 10, 2003, and July 8, 2003, respectively. The spacecraft arrived at Mars approximately seven months later on January 4, 2004, and January 24, 2004. These spacecraft needed to be precisely navigated to a Mars atmospheric entry flight path angle of -11.5 deg +/-0.12 deg (3(sigma)) for MER-A and +/-0.14 deg (3(sigma)) for MER-B in order to satisfy the landing site delivery requirements. The orbit determination task of the navigation team needed to accurately determine the trajectory of the spacecraft, predict the trajectory to Mars atmospheric entry, and account for all possible errors sources so that the each spacecraft could be correctly targeted using five trajectory corrections along the way. This paper describes the orbit determination analysis which allowed MER-A to be targeted using only four trajectory correction maneuvers to an entry flight path angle of -11.49 deg +/-O.010 deg (3(sigma)) and MER-B to be targeted using only three trajectory correction maneuvers to an entry flight path angle of -11.47 +/-0.021 deg(3(sigma)).
The Mars Science Laboratory (MSL), carrying the Curiosity rover to Mars, was launched on November 26, 2011, from Cape Canaveral, Florida. The target for MSL was selected to be Gale Crater, near the equator of Mars, with an arrival date in early August 2012. The two main interplanetary navigation tasks for the mission were to deliver the spacecraft to an entry interface point that would allow the rover to safely reach the landing area, and to tell the spacecraft where it entered the atmosphere of Mars, so it could guide itself accurately to close proximity of the landing target. MSL used entry guidance as it slowed down from the entry speed to a speed low enough to allow for a successful parachute deployment, and this guidance allowed shrinking the landing ellipse to a 99% conservative estimate of 7 by 20 kilometers. Since there is no global positioning system in Mars, achieving this accuracy was predicated on flying a trajectory that closely matched the reference trajectory used to design the guidance algorithm, and on initializing the guidance system with an accurate Mars-relative entry state that could be used as the starting point to integrate the inertial measurement unit data during entry and descent. The pre-launch entry flight path angle (EFPA) delivery requirement was +/- 0.20 deg, but after launch a smaller threshold of +/- 0.05 deg was used as the criteria for late trajectory correction maneuver (TCM) decisions. The pre-launch requirement for entry state knowledge was 2.8 kilometers in position error and 2 meters per second in velocity error, but also smaller thresholds were defined after launch to evaluate entry state update opportunities. The biggest challenge for the navigation team was to accurately predict the trajectory of the spacecraft, so the estimates of the entry conditions could be stable, and late trajectory correction maneuvers or entry parameter updates could be waved off. As a matter of fact, the prediction accuracy was such that the last TCM performed was a small burn executed eight days before landing, and the entry state that was calculated just 36 hours after that TCM, and that was uploaded to the spacecraft the same day, did not need to be updated. The final EFPA was 0.013 deg shallower than the -15.5 deg target, and the on-board entry state was just 200 meters in position and 0.11 meters per second in velocity from the post-landing reconstructed entry state. Overall the entry delivery and knowledge requirements were fulfilled with a margin of more than 90% with respect to the pre-launch thresholds. This excellent accuracy contributed to a very successful and accurate entry, descent, and landing, and surface mission.
This National Aeronautics and Space Administration (NASA) Orbital Debris Engineering Model (ORDEM) 3.1 Software User Guide accompanies delivery of the latest upgraded version of the model, ORDEM 3.1. The user guide also provides a top-level program description and a list of capabilities. It includes descriptions of runtime error and information codes, input/output file formats, runtimes for different orbit configurations, and how to use uncertainty files. ORDEM 3.1 supersedes the previous NASA Orbital Debris Program Office (ODPO) models – ORDEM 3.0 (Stansbery, et al. 2014) and ORDEM2000 (Liou, et al. 2002). The availability of new sensor and in situ data, re-analysis of older data, and development of new analytical techniques has enabled the construction of this more comprehensive and sophisticated model. An upgraded graphical user interface (GUI) is integrated with the software. This upgraded GUI uses project-oriented organization and provides the user with graphical representations of numerous output data products. For example, these range from the conventional flux vs. average debris size (or altitude bin) for chosen analysis orbits (or views) to the more complex color-contoured, two-dimensional (2-D) directional flux diagrams in local spacecraft elevation and azimuth. The current model, ORDEM 3.1, supports spacecraft as well as telescope/radar project assessments. ORDEM 3.1 contains updated debris populations covering low Earth orbit (LEO, up to 2000 km altitude) to geosynchronous orbit (GEO, up to 40,000 km altitude) and can assess debris calculations up to year 2050, extending coverage past the previous limit of 2035 in ORDEM 3.0. Although populations differ from its predecessor, ORDEM 3.1 is functionally the same as ORDEM 3.0 and can support ORDEM 3.0 projects through backward compatibility.
This National Aeronautics and Space Administration (NASA) Orbital Debris Engineering Model (ORDEM) 3.2 Software User Guide accompanies delivery of the latest upgraded version of the model, ORDEM 3.2. The user guide also provides a top-level program description and a list of capabilities. It includes descriptions of runtime error and information codes, input/output file formats, runtimes for different orbit configurations, and how to use uncertainty files. ORDEM 3.2 supersedes the previous NASA Orbital Debris Program Office (ODPO) models – ORDEM 3.0 (Stansbery, et al. 2014) and ORDEM2000 (Liou, et al. 2002). The availability of new sensor and in situ data, re-analysis of older data, and development of new analytical techniques has enabled the construction of this more comprehensive and sophisticated model. An upgraded graphical user interface (GUI) is integrated with the software. This upgraded GUI uses project-oriented organization and provides the user with graphical representations of numerous output data products. For example, these range from the conventional flux vs. average debris size (or altitude bin) for chosen analysis orbits (or views) to the more complex color-contoured, two-dimensional (2-D) directional flux diagrams in local spacecraft elevation and azimuth. The current model, ORDEM 3.2, supports spacecraft as well as telescope/radar project assessments. ORDEM 3.2 contains updated debris populations covering low Earth orbit (LEO, up to 2000 km altitude) to geosynchronous orbit (GEO, up to 40,000 km altitude) and can assess debris calculations up to year 2050, extending coverage past the previous limit of 2035 in ORDEM 3.0. Although populations differ from its predecessor, ORDEM 3.2 is functionally the same as ORDEM 3.0 and can support ORDEM 3.0 projects through backward compatibility.
The navigation aspects of the Mariner Venus/Mercury 1973 mission are presented. Principal emphasis is on the maneuver strategy employed, propellant costs and the results of the navigation performance relating to the accomplishment of the mission objectives including an extended mission for a second Mercury encounter. Key error sources and mission constraints are discussed. Of particular interest is the impact of in-flight adaptation of the pre-launch maneuver strategy (due to spacecraft anomalies) on propellant cost and the delivery achieved at the first Mercury encounter. The maneuver strategy and propellant cost for the extended mission are shown to be heavily influenced by the delivery achieved at the first Mercury encounter and the science objectives at the second Mercury encounter.
Since the Voyager Mission will encounter Saturn at a time when the planet will be nearly in the earth's equatorial plane, earth-based orbit determination will be more difficult than usual because of the so-called zero-declination singularity associated with conventional radiometric observations. Simulation studies show that in order to meet the required delivery accuracy at Saturn, a relative range measurement between the Goldstone and Canberra Deep Space Stations must be accurate to 4.5 times the square root of two meters. Topics discussed include the nature of error sources, the methodology and technology required for calibration, the verification process concerning the nearly simultaneous range capability, a description of the ranging system, and tracking strategy.
The role played by remote sensors on-board the Landsat and NOAA-7 satellites in monitoring and management of three catastrophic events that took place in 1982 and 1983 in Indonesia (two major volcanic eruptions and a large-scale forest fire) is assessed. The modes of operation of the satellite platforms, the types of data derived, and data availability to the users are described, and the sources of failures and delays (such as the presence of clouds, technical and computer errors, red-tape, etc.) are examined. The major drawbacks of the Landsat-supplied information for monitoring short-lived and fast-changing events were the insufficient frequency of data acquisition, delayed delivery of data, and extended times needed for data distribution and processing. Indonesia's NOAA-7 and GMS sensors, although of low spatial resolution, offered higher frequency of data collection, and profited from the existence of a local receiving station. The present value of the space-based imagery is seen mainly in the baseline assessment of the disaster-prone areas, which can assist in preparing these areas for the impending catastrophic events.
Our first activity is based on delivery of code to Bob Evans (University of Miami) for integration and eventual delivery to the MODIS Science Data Support Team. As we noted in our previous semi-annual report, coding required the development and analysis of an end-to-end model of fluorescence line height (FLH) errors and sensitivity. This model is described in a paper in press in Remote Sensing of the Environment. Once the code was delivered to Miami, we continue to use this error analysis to evaluate proposed changes in MODIS sensor specifications and performance. Simply evaluating such changes on a band by band basis may obscure the true impacts of changes in sensor performance that are manifested in the complete algorithm. This is especially true with FLH that is sensitive to band placement and width. The error model will be used by Howard Gordon (Miami) to evaluate the effects of absorbing aerosols on the FLH algorithm performance. Presently, FLH relies only on simple corrections for atmospheric effects (viewing geometry, Rayleigh scattering) without correcting for aerosols. Our analysis suggests that aerosols should have a small impact relative to changes in the quantum yield of fluorescence in phytoplankton. However, the effect of absorbing aerosol is a new process and will be evaluated by Gordon.
The study was conducted on six watersheds ranging in size from 277 km to 3460 km in the Rio Grande and Arkansas River basins of southwestern Colorado. Six years of satellite data in the period 1973-78 were analyzed and snowcover maps prepared for all available image dates. Seven snowmapping techniques were explored; the photointerpretative method was selected as the most accurate. Three schemes to forecast snowmelt runoff employing satellite snowcover observations were investigated. They included a conceptual hydrologic model, a statistical model, and a graphical method. A reduction of 10% in the current average forecast error is estimated when snowcover data in snowmelt runoff forecasting is shown to be extremely promising. Inability to obtain repetitive coverage due to the 18 day cycle of LANDSAT, the occurrence of cloud cover and slow image delivery are obstacles to the immediate implementation of satellite derived snowcover in operational streamflow forecasting programs.
The motivation behind Integrated Demand Management (IDM) research is to explore possible improvements to United States National Airspace System (NAS) performance that could be realized through procedural integration of strategic traffic flow management capabilities, such as the Collaborative Trajectory Options Program (CTOP), and tactical capabilities, such as Time Based Flow Management (TBFM). An initial IDM concept for clear weather operations was developed and evaluated for potential benefits, including efficiency, delay reduction, predictability and throughput, and to identify any major issues that might represent a showstopper for a fielded application. Newark Liberty International Airport (EWR) arrival operations provided a use case for concept development. EWR uses miles-in-trail (MIT) metering to regulate demand into TBFM during high volume operations, and short-haul flights are often penalized with excessive, last-minute ground delays when the overhead stream is saturated. IDM addresses this problem by replacing MIT conditioning with CTOP to better manage the demand delivery to the TBFM entry points. A quasi-real time high-fidelity simulation that would normally involve participants was conducted using heuristic-based procedures that mimicked operators behaviors instead. Five total conditions were compared: two baseline conditions with MIT delivery to TBFM entry points using two different TBFM settings; and three IDM conditions: one with airborne speed control using an Required Time of Arrival (RTA) capability, a second without RTA, and a third with no wind forecast errors. Results suggest that the IDM concept can deliver traffic more efficiently by shifting the delays from airborne to ground for both RTA and non-RTA conditions, while maintaining a target throughput rate. The results also suggest that with good predictability of airport capacity, excessive TBFM ground delay can be minimized by applying more strategic CTOP delay, increasing predictability for the airline operators. Overall, the results indicate that the implementation of an IDM concept under clear weather conditions can improve NAS system performance. Future IDM research aims to expand the concept to address demandcapacity imbalance d severe weather.
Link analysis is a system engineering process in the design, development, and operation of communication systems and networks. Link models that are mathematical abstractions representing the useful signal power and the undesirable noise and attenuation effects (including weather effects if the signal path transverses through the atmosphere) that are integrated into the link budget calculation that provides the estimates of signal power and noise power at the receiver. Then the link margin is applied which attempts to counteract the fluctuations of the signal and noise power to ensure reliable data delivery from transmitter to receiver. (Link margin is dictated by the link margin policy or requirements.) A simple link budgeting approach assumes link parameters to be deterministic values typically adopted a rule-of-thumb policy of 3 dB link margin. This policy works for most S- and X-band links due to their insensitivity to weather effects. But for higher frequency links like Ka-band, Ku-band, and optical communication links, it is unclear if a 3 dB link margin would guarantee link closure. Statistical link analysis that adopted the 2-sigma or 3-sigma link margin incorporates link uncertainties in the sigma calculation. (The Deep Space Network (DSN) link margin policies are 2-sigma for downlink and 3-sigma for uplink.) The link reliability can therefore be quantified statistically even for higher frequency links. However in the current statistical link analysis approach, link reliability is only expressed as the likelihood of exceeding the signal-to-noise ratio (SNR) threshold that corresponds to a given bit-error-rate (BER) or frame-error-rate (FER) requirement. The method does not provide the true BER or FER estimate of the link with margin, or the required signalto-noise ratio (SNR) that would meet the BER or FER requirement in the statistical sense. In this paper, we perform in-depth analysis on the relationship between BER/FER requirement, operating SNR, and coding performance curve, in the case when the channel coherence time of link fluctuation is comparable or larger than the time duration of a codeword. We compute the "true" SNR design point that would meet the BER/FER requirement by taking into account the fluctuation of signal power and noise power at the receiver, and the shape of the coding performance curve. This analysis yields a number of valuable insights on the design choices of coding scheme and link margin for the reliable data delivery of a communication system - space and ground. We illustrate the aforementioned analysis using a number of standard NASA error-correcting codes.
Human-scale missions to Mars will likely require multiple landers delivered precisely to designated locations. The current NASA human Mars reference architecture assumes delivery of three 25 t payloads from a 1- or 5-Sol orbit to the surface with a landing precision of 50 m to ensure logistics are located near the habitat. While initial navigation estimates improve with on-orbit ground tracking, errors increase during post-deorbit coast. Likewise, Mars atmospheric variability and forecasting uncertainty means that the entry vehicle guidance, navigation, and control systems must be robust to accommodate landing during any time of day or Mars year, including during dust storms. Precision landing technologies are currently being assessed to determine if onboard navigation sensors are sufficient to enable the landing accuracy required or if additional navigation aids such as surface or orbiting beacons will be needed. This study evaluates the system performance requirements to meet the desired landing accuracy for the reference vehicle design and entry, descent, and landing concept of operations. A detailed six degree-of-freedom integrated performance simulation framework is used to perform the assessment and demonstrate that under current assumptions, onboard navigation sensors are sufficient to support precision landing.