Intelligent User-Preferred Reroutes Using Digital Data Communication
Explore the source record for details and available documents.
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.
Explore the source record for details and available documents.
The National Aeronautics and Space Administration (NASA) is supporting research to transition from a legacy, air traffic management (ATM) system to Trajectory-Based Operations (TBO) environment targeting the 2035-2045 timeframe by creating simulation scenarios for current and future studies. TBO in the National Airspace System (NAS) focuses on modernizing the current operating paradigm to increase efficiency, predictability, resilience, and flexibility while migrating toward greater operational autonomy across the airspace. These simulation scenarios offer a wide dissemination and use of system-level constraints and aircraft state/intent data, routine use of data communications to request complex trajectory modifications and to receive clearances, and aircraft that are flying on 4-D trajectories with flexibility when desired, but structure where required. This report describes the end-to-end development of scenarios for the NASA Langley Research Center simulation environment to represent a 2040 Trajectory-Based Operations airspace for air transport operations research.
This project will develop foundations for energy-efficient, high-data-rate, and reliable communication links for next-generation advanced wireless technologies. The Internet of Everything is emerging as a major technology that can establish a massively connected network among both human-type users and machine-type devices. Particularly, massive machine-type communication is becoming the dominant communication paradigm for numerous emerging areas, including data center networking and wireless backhaul, healthcare (e-health), manufacturing (industry 4.0), utilities, transportation (connected cars and public safety), and virtual or augmented reality for human-machine interaction applications. The rising demand for high data rates, especially in indoor scenarios and densely populated outdoor environments, will eventually overload conventional RF-based technologies. This project aims to conduct fundamental research to design, optimize, and validate a communication-aware, energy-efficient, and reliable network (CommAwareNet) architecture for future smart facilities and environments that require unprecedented high throughput needs for massive numbers of the machine- and human-type users. The scientific and technical merit of this work lies in the research required to bring the proposed transformative CommAwareNet solution into fully functional and practical architecture.
The Naval Postgraduate School's (NPS) Space Systems Academic Group (SSAG) is designing and developing a small communications satellite for launch aboard the shuttle as a complex autonomous payload (CAP). The objectives of PANSAT are three-fold. First, PANSAT will provide an ideal educational tool for the officer students at NPS supporting Space Systems Engineering and Space Systems Operations with hands-on hardware development. Second, the satellite will provide digital store-and-forward communications, or packet radio, for the amateur radio community. The third objective is to provide a low-cost, space-based platform for small experiments. PANSAT will be launched from the shuttle at a nominal altitude of 200 n.m. and an inclination of at least 37 degrees. The satellite weight is 150 lbs. Since there is no attitude control, eight dipole whip antennas will be used to provide isotropic ground coverage for communications. FM digital communications will be used with up-link and down-link on a single frequency in the amateur band of 437.25 MHz. A maximum 50 kHz of bandwidth is envisioned for the satellite. The expected lifetime of the satellite is 1 1/2 to 2 years before atmospheric reentry. The PANSAT design consists of the following: communications subsystem (COMM); computer, or data processor and sequencer (DP&S); power subsystem; structure subsystem; and experiment payload.
This is the AmeriFlux version of the carbon flux data for the site US-INg INFLUX - Wayne Twp Comm (Site-7). Site Description - Urban site, tower is a lattice communications tower
Micrometre and smaller scale dust within cometary comae can be observed by telescopic remote sensing spectroscopy [1] and the particle size and abundance can be measured by in situ spacecraft impact detectors [2]. Initial interpretation of the samples returned from comet 81P/Wild 2 by the Stardust spacecraft [3] appears to show that very fine dust contributes not only a small fraction of the solid mass, but is also relatively sparse [4], with a low negative power function describing grain size distribution, contrasting with an apparent abundance indicated by the on-board Dust Flux Monitor Instrument (DFMI) [5] operational during the encounter. For particles above 10 m diameter there is good correspondence between results from the DFMI and the particle size inferred from experimental calibration [6] of measured aerogel track and aluminium foil crater dimensions (as seen in Figure 4 of [4]). However, divergence between data-sets becomes apparent at smaller sizes, especially submicrometre, where the returned sample data are based upon location and measurement of tiny craters found by electron microscopy of Al foils. Here effects of detection efficiency tail-off at each search magnification can be seen in the down-scale flattening of each scale component, but are reliably compensated by sensible extrapolation between segments. There is also no evidence of malfunction in the operation of DFMI during passage through the coma (S. Green, personal comm.), so can the two data sets be reconciled?
OBJECTIVES: NASA Extreme Environment Mission Operations (NEEMO) is an underwater spaceflight analog that allows a true mission‐like operational environment and uses buoyancy effects and added weight to simulate different gravity levels. Three missions were undertaken from 2014‐2015, NEEMO's 18‐20. All missions were performed at the Aquarius undersea research habitat. During each mission, the effects of varying operations concepts and tasks type and complexity on representative communication latencies associated with Mars missions were studied. METHODS: 12 subjects (4 per mission) were weighed out to simulate near‐zero or partial gravity extravehicular activity (EVA) and evaluated different operations concepts for integration and management of a simulated Earth‐based science backroom team (SBT) to provide input and direction during exploration activities. Exploration traverses were planned in advance based on precursor data collected. Subjects completed science‐related tasks including presampling surveys, geologic‐based sampling, and marine‐based sampling as a portion of their tasks on saturation dives up to 4 hours in duration that were to simulate extravehicular activity (EVA) on Mars or the moons of Mars. One‐way communication latencies, 5 and 10 minutes between space and mission control, were simulated throughout the missions. Objective data included task completion times, total EVA times, crew idle time, translation time, SBT assimilation time (defined as time available for SBT to discuss data/imagery after it has been collected, in addition to the time taken to watch imagery streaming over latency). Subjective data included acceptability, simulation quality, capability assessment ratings, and comments. RESULTS: Precursor data can be used effectively to plan and execute exploration traverse EVAs (plans included detailed location of science sites, high‐fidelity imagery of the sites, and directions to landmarks of interest within a site). Operations concepts that allow for presampling surveys enable efficient traverse execution and meaningful Mission Control Center (MCC) interaction across long communication latencies and can be done with minimal crew idle time. Imagery and information from the EVA crew that is transmitted real‐time to the intravehicular (IV) crewmember(s) can be used to verify that exploration traverse plans are being executed correctly. That same data can be effectively used by MCC (across comm latency) to provide further instructions to the crew from a SBT on sampling priorities, additional tasks, and changes to the plan. Text / data capabilities are preferred over voice capabilities between MCC and IV when executing exploration traverse plans over communication latency. Autonomous crew planning tools can be effective at modifying existing plans if the objectives and constraints are clearly defined.
NASA Extreme Environment Mission Operations (NEEMO) is an underwater spaceflight analog that allows a true mission-like operational environment and uses buoyancy effects and added weight to simulate different gravity levels. Three missions were undertaken from 2014-2015, NEEMO's 18-20. All missions were performed at the Aquarius undersea research habitat. During each mission, the effects of communication latencies on operations concepts, timelines, and tasks were studied. METHODS: Twelve subjects (4 per mission) were weighed out to simulate near-zero or partial gravity extravehicular activity (EVA) and evaluated different operations concepts for integration and management of a simulated Earth-based science team (ST) to provide input and direction during exploration activities. Exploration traverses were preplanned based on precursor data. Subjects completed science-related tasks including pre-sampling surveys, geologic-based sampling, and marine-based sampling as a portion of their tasks on saturation dives up to 4 hours in duration that were designed to simulate extravehicular activity (EVA) on Mars or the moons of Mars. One-way communication latencies, 5 and 10 minutes between space and mission control, were simulated throughout the missions. Objective data included task completion times, total EVA times, crew idle time, translation time, ST assimilation time (defined as time available for ST to discuss data/imagery after data acquisition). Subjective data included acceptability, simulation quality, capability assessment ratings, and comments. RESULTS: Precursor data can be used effectively to plan and execute exploration traverse EVAs (plans included detailed location of science sites, high-fidelity imagery of the sites, and directions to landmarks of interest within a site). Operations concepts that allow for pre-sampling surveys enable efficient traverse execution and meaningful Mission Control Center (MCC) interaction across communication latencies and can be done with minimal crew idle time. Imagery and contextual information from the EVA crew that is transmitted real-time to the intravehicular (IV) crewmember(s) can be used to verify that exploration traverse plans are being executed correctly. That same data can be effectively used by MCC (across comm latency) to provide meaningful feedback and instruction to the crew regarding sampling priorities, additional tasks, and changes to the EVA timeline. Text / data capabilities are preferred over voice capabilities between MCC and IV when executing exploration traverse plans over communication latency.
The ISS provides an excellent opportunity for pioneering artificial intelligence software to meet the challenges of real-time communications (comm) link management. This opportunity empowers the ISS Program to forge a testbed for developing cognitive communications systems for the benefit of the ISS mission, manned Low Earth Orbit (LEO) science programs and future planetary exploration programs. In November, 1998, the Flight Operations Directorate (FOD) started the ISS Antenna Manager (IAM) project to develop a single processor supporting multiple comm satellite tracking for two different antenna systems. Further, the processor was developed to be highly adaptable as it supported the ISS mission through all assembly stages. The ISS mission mandated communications specialists with complete knowledge of when the ISS was about to lose or gain comm link service. The current specialty mandated cognizance of large sun-tracking solar arrays and thermal management panels in addition to the highly-dynamic satellite service schedules and rise/set tables. This mission requirement makes the ISS the ideal communications management analogue for future LEO space station and long-duration planetary exploration missions. Future missions, with their precision-pointed, dynamic, laser-based comm links, require complete autonomy for managing high-data rate communications systems. Development of cognitive communications management systems that permit any crew member or payload science specialist, regardless of experience level, to control communications is one of the greater benefits the ISS can offer new space exploration programs. The IAM project met a new mission requirement never previously levied against US space-born communications systems management: process and display the orientation of large solar arrays and thermal control panels based on real-time joint angle telemetry. However, IAM leaves the actual communications availability assessment to human judgement, which introduces unwanted variability because each specialist has a different core of experience with comm link performance. Because the ISS utilizes two different frequency bands, dynamic structure can be occasionally translucent at one frequency while it can completely interdict service at the other frequency. The impact of articulating structure on the comm link can depend on its orientation at the time it impinges on the link. It can become easy for a human specialist to cross-associate experience at one frequency with experience at the other frequency. Additionally, the specialist's experience is incremental, occurring one nine-hour shift at a time. Only the IAM processor experiences the complete 24x7x365 communications link performance for both communications links but, it has no "learning capability." If the IAM processor could be endowed with a cognitive ability to remember past structure-induced comm link outages, based on its knowledge of the ISS position, attitude, communications gear, array joint angles and tracking accuracy, it could convey such experience to the human operator. It could also use its learned communications link behaviors to accurately convey the availability of future communications sessions. Further, the tool could remember how accurately or inaccurately it predicted availability and correct future predictions based on past performance. The IAM tool could learn frequency-specific impacts due to spacecraft structures and pass that information along as "experience." Such development would provide a single artificial intelligence processor that could provide two different experience bases. If it also "knew" the satellite service schedule, it could distinguish structure blockage from schedule or planet blockage and then quickly switch to another satellite. Alternatively, just as a human operator could judge, a cognizant comm system based on the IAM model could "know" that the blockage is not going to last very long and continue tracking a comm satellite, waiting for it to track away from structure. Ultimately, once this capability was fully developed and tested in the Mission Control Center, it could be transferred on-orbit to support development of operations concepts that include more advanced cognitive communications systems. Future applications of this capability are easily foreseen because even more dynamic satellite constellations with more nodes and greater capability are coming. Currently, the ISS fully employs its high-data-rate return link for harvesting payload science. In the coming months, it will double that data rate and is forecast to fully utilize that capability. Already there is talk of an upgrade that quadruples the current data rate allocated to ISS payload science before the end of its mission and laser comm links have already been tested from the ISS. Every data rate upgrade mandates more complicated and sensitive communications equipment which implies greater expertise invested in the human operator. Future on-orbit cognizant comm systems will be needed to meet greater performance demands aboard larger, far more complicated spacecraft. In the LEO environment, the old-style one-satellite-per-spacecraft operations concept will give way to a new concept of a single customer spacecraft simultaneously using multiple comm satellites. Much more highly-dynamic manned LEO missions with decades of crew members potentially increase the demand for communications link performance. A cognizant on-board communications system will meet advanced communications demands from future LEO missions and future planetary missions. The ISS has fledgling components of future exploration programs, both LEO and planetary. Further, the Flight Operations Directorate, through the IAM project, has already begun to develop a communications management system that attempts to solve advanced problems ideally represented by dynamic structure impacting scheduled satellite service. With an earnest project to integrate artificial intelligence into the IAM processor, the ISS Program could develop a cognizant communications system that could be adapted and transferred to future on-orbit avionics designs.
The ISS provides an excellent opportunity for pioneering artificial intelligence software to meet the challenges of real-time communications (comm) link management. This opportunity empowers the ISS Program to forge a testbed for developing cognitive communications systems for the benefit of the ISS mission, manned Low Earth Orbit (LEO) science programs and future planetary exploration programs. In November, 1998, the Flight Operations Directorate (FOD) started the ISS Antenna Manager (IAM) project to develop a single processor supporting multiple comm satellite tracking for two different antenna systems. Further, the processor was developed to be highly adaptable as it supported the ISS mission through all assembly stages. The ISS mission mandated communications specialists with complete knowledge of when the ISS was about to lose or gain comm link service. The current specialty mandated cognizance of large sun-tracking solar arrays and thermal management panels in addition to the highly-dynamic satellite service schedules and rise/set tables. This mission requirement makes the ISS the ideal communications management analogue for future LEO space station and long-duration planetary exploration missions. Future missions, with their precision-pointed, dynamic, laser-based comm links, require complete autonomy for managing high-data rate communications systems. Development of cognitive communications management systems that permit any crew member or payload science specialist, regardless of experience level, to control communications is one of the greater benefits the ISS can offer new space exploration programs. The IAM project met a new mission requirement never previously levied against US space-born communications systems management: process and display the orientation of large solar arrays and thermal control panels based on real-time joint angle telemetry. However, IAM leaves the actual communications availability assessment to human judgment, which introduces unwanted variability because each specialist has a different core of experience with comm link performance. Because the ISS utilizes two different frequency bands, dynamic structure can be occasionally translucent at one frequency while it can completely interdict service at the other frequency. The impact of articulating structure on the comm link can depend on its orientation at the time it impinges on the link. It can become easy for a human specialist to cross-associate experience at one frequency with experience at the other frequency. Additionally, the specialist's experience is incremental, occurring one nine-hour shift at a time. Only the IAM processor experiences the complete 24x7x365 communications link performance for both communications links but, it has no "learning capability." If the IAM processor could be endowed with a cognitive ability to remember past structure-induced comm link outages, based on its knowledge of the ISS position, attitude, communications gear, array joint angles and tracking accuracy, it could convey such experience to the human operator. It could also use its learned communications link behaviors to accurately convey the availability of future communications sessions. Further, the tool could remember how accurately or inaccurately it predicted availability and correct future predictions based on past performance. The IAM tool could learn frequency-specific impacts due to spacecraft structures and pass that information along as "experience." Such development would provide a single artificial intelligence processor that could provide two different experience bases. If it also "knew" the satellite service schedule, it could distinguish structure blockage from schedule or planet blockage and then quickly switch to another satellite. Alternatively, just as a human operator could judge, a cognizant comm system based on the IAM model could "know" that the blockage is not going to last very long and continue tracking a comm satellite, waiting for it to track away from structure. Ultimately, once this capability was fully developed and tested in the Mission Control Center, it could be transferred on-orbit to support development of operations concepts that include more advanced cognitive communications systems. Future applications of this capability are easily foreseen because even more dynamic satellite constellations with more nodes and greater capability are coming. Currently, the ISS fully employs a 300 million bit-per-second (Mbps) return link for harvesting payload science. In the coming eighteen months, it will step up to 600 Mbps. Already there is talk of a 1.2 billion bit-per-second (Gbps) upgrade for the ISS and laser comm links have already been tested from the ISS. Every data rate upgrade mandates more complicated and sensitive communications equipment which implies greater expertise invested in the human operator. Future on-orbit cognizant comm systems will be needed to meet greater performance demands aboard larger, far more complicated spacecraft. In the LEO environment, the old-style one-satellite-per-spacecraft operations concept will give way to a new concept of a single customer spacecraft simultaneously using multiple comm satellites. Much more highly-dynamic manned LEO missions with decades of crew members potentially increase the demand for communications link performance. A cognizant on-board communications system will meet advanced communications demands from future LEO missions and future planetary missions. The ISS has fledgling components of future exploration programs, both LEO and planetary. Further, the Flight Operations Directorate, through the IAM project, has already begun to develop a communications management system that attempts to solve advanced problems ideally represented by dynamic structure impacting scheduled satellite service. With an earnest project to integrate artificial intelligence into the IAM processor, the ISS Program could develop a cognizant communications system that could be adapted and transferred to future on-orbit avionics designs.
ERS2 radar data acquired before and after the Mw7.6, Manyi (Tibet) earthquake of November 8, 1997, provide geodetic information about the surface displacement produced by the earthquake in two ways. (1) The sub-pixel geometric adjustment of the before and after images provides a two dimensional offset field with a resolution of approx, 1m in both the range (radar line of sight) and azimuth (satellite track) directions. Comparison of offsets in azimuth and range indicates that the displacement along the fault is essentially strike-slip and in a left-lateral sense. The offset map reveals a relatively smooth and straight, N78E surface rupture that exceeds 150 km in length, consistent with the EW plane of the Harvard CMT solution. The rupture follows the trace of a quaternary fault visible on satellite imagery (Tapponnier and Molnar, 1978; Wan Der Woerd, pers. comm.). (2) Interferometric processing of the SAR data provides a range displacement map with a precision of a few millimeters. The slip distribution along the rupture reconstructed from the range change map is a bell-shaped curve in the 100-km long central section of the fault with smaller, local maxima near both ends. The curve shows that the fault slip exceeds 2.2 m in range, or 6.2 in strike-slip, along a 30-km long section of the fault and remains above 1 m in range, approx. 3 m strike-slip, along most of its length. Preliminary forward modeling of the central section of the rupture, assuming a uniform slip distribution with depth, indicates that the slip occur-red essentially between 0 and the depth of 10 km, consistent with a relatively shallow event (Velasco et al., 1998).
As space mission design trends towards shared, multi-mission platforms and high-performance onboard computing architectures, the number of spacecraft launched into operation is also steadily rising. Through ridesharing, spacecraft miniaturization, and other cost-reduction measures, the barriers to space are lowering, resulting in compounded growth in the amount of flight software being deployed. To meet the needs of both the growing quantity and evolving nature of spacecraft, flight software design must accordingly adapt to support more efficient development, solutions to computational resource-sharing, and software reusability. This paper focuses on a software payload demonstrating several core technologies that improve the state-of-the-art in these identified areas. Launched into low-earth orbit in January 2022, our software payload was conceived, designed, and delivered in a span of merely two months. It was developed on top of the NASA core Flight System (cFS) framework and the Distributed Spacecraft Autonomy (DSA) Comm cFS application, which translates cFS software bus messages across a Data Distribution Service (DDS) network. The flight software, packaged in Linux container images, was deployed as one of 18 flight applications managed through the Unibap SpaceCloud Framework. The applications were run on a Unibap iX5-102 radiation-tolerant payload computer, hosted on the D-Orbit SCV-004 spacecraft as part of an ESA-sponsored in-orbit technology test. Our payload, referred to as the DSA D-Orbit software, demonstrates the reusability of the DSA Comm app in a substantially different context and purpose as its original mission. Comm’s original design goal was to reliably distribute messages between spacecraft swarms of arbitrary size and dynamic network topology. However, we leverage this same functionality to introduce redundancy and opportunistic parallel data processing in the context of a representative onboard image processing workload. This adaptive mission architecture was enabled in part by the SpaceCloud Framework’s use of container virtualization as the payload integration interface. By using a base container image with common high-level language runtimes and libraries, we were able to rapidly design, develop, and validate our image processing application without many of the technological barriers common to flight software development. We present details the goals, approach, results, and lessons learned through this technology demonstration experiment and contextualize those observations against present and future challenges in spacecraft software development.
The database of photographic meteor orbits of the IAU Meteor Data Center at the Astronomical Institute SAS has gradually been updated. To the 2003 version of 4581 photographic orbits compiled from 17 different stations and obtained in the period 1936-1996, additional new 211 orbits compiled from 7 sources have been added. Thus, the updated version of the catalogue contains 4792 photographic orbits (equinox J2000.0) available either in two separate orbital and geophysical data files or a file with the merged data. All the updated files with relevant documentation are available at the web of the IAU Meteor Data Center. Keywords astronomical databases photographic meteor orbits 1 Introduction Meteoroid orbits are a basic tool for investigation of distribution and spatial structure of the meteoroid population in the close surroundings of the Earth s orbit. However, information about them is usually widely scattered in literature and often in publications with limited circulation. Therefore, the IAU Comm. 22 during the 1976 IAU General Assembly proposed to establish a meteor data center for collection of meteor orbits recorded by photographic and radio techniques. The decision was confirmed by the next IAU GA in 1982 and the data center was established (Lindblad, 1987). The purpose of the data center was to acquire, format, check and disseminate information on precise meteoroid orbits obtained by multi-station techniques and the database gradually extended as documented in previous reports on the activity of the Meteor Data Center by Lindblad (1987, 1995, 1999 and 2001) or Lindblad and Steel (1993). Up to present, the database consists of 4581 photographic meteor orbits (Lindblad et al., 2005), 63.330 radar determined orbit: Harvard Meteor Project (1961-1965, 1968-1969), Adelaide (1960-1961, 1968-1969), Kharkov (1975), Obninsk (1967-1968), Mogadish (1969-1970) and 1425 video-recordings (Lindblad, 1999) to which additional 817 video meteors orbits published by Koten el al. (2003) were
A Venus orbit insertion sequence to meet various science objectives and end with a stable science orbit. An Earth data downlink opportunities to polar ground stations. Neither are mission specific.
A selective repeat automatic repeat request (ARQ) system was implemented under software control in the Ground Communications Facility error detection and correction (EDC) assembly at JPL and the comm monitor and formatter (CMF) assembly at the DSSs. The CMF and EDC significantly improved real time data quality and significantly reduced the post-pass time required for replay of blocks originally received in error. Since the remote mission operation centers (RMOCs) do not provide compatible error correction equipment, error correction will not be used on the RMOC-JPL high speed data (HSD) circuits. The real time error correction capability will correct error burst or outage of two loop-times or less for each DSS-JPL HSD circuit.
Mars Relay Network is prepared to support MSL: a) ODY/MRO/MEX will all provide critical event comm support during EDL. b) New Electra/Electra-Lite capabilities on the MSL-MRO link will support >250 Mb/sol MSL data return. 2013 MAVEN orbiter will replenish on-orbit relay infrastructure as prior orbiters approach end-of-life. While NASA has withdrawn from the 2016 EMTGO and 2018 Joint Rover missions, analysis of the potential link shows a path to Gbit/sol relay capability 2012.
dbComm is a module for integrating a Python codebase with MongoDB using the PyMongo library. The methods contained are used to connect to a Mongo database and push/pull data.
While the use of workflows for HPC is growing, MPI interoperability remains a challenge for workflow management systems. The MPI standard and/or its implementations provide a number of ways to build multiple-programs-multiple-data (MPMD) applications. These methods present limitations related to fault tolerance, and are not easy to use. In this paper, we advocate for a novel MPI_Comm_launch function acting as the parallel counterpart of a system(3) call. MPI_Comm_launch allows a child MPI application to be launched inside the resources originally held by processes of a parent MPI application. Two important aspects of MPI_Comm_launch is that it pauses the calling process, and runs the child processes on the parent’s CPU cores, but in an isolated manner with respect to memory. This function makes it easier to build MPMD applications with well-decoupled subtasks. We show how this feature can provide better flexibility and better fault tolerance in ensemble simulations and HPC workflows. Here, we report results showing 2x throughput improvement for application workflows with faults, and scaling results for challenging workloads up to 256 nodes.