Geodetic problems and satellite orbits
Geodetic error effects on time dependence of satellite tracking data as received by surface tracking station
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.
Geodetic error effects on time dependence of satellite tracking data as received by surface tracking station
Optical navigation is the use of onboard imaging to aid in the determination of the spacecraft trajectory and of the targets' ephemerides. Opnav techniques provide a direct measurement of the direction from a spacecraft to target bodies. Opnav data thus complement both radiometric tracking data (for instance, Doppler and range) and the groundbased astrometry which is used to determine the a priori ephemeris of the targets. We present the geometry and camera models which form the mathematical basis for optical navigation and some of the image processing techniques by which one can extract the optical observables--that is, the sample and line coordinates of images--from pictures.
The Mars 2020 Mission’s primary objective is to collect 20 geographically unique samples during its prime mission of one and a quarter Martian years, or just over 2 Earth years. Mission planners determined the project needed to develop a system that would enable the operations team to analyze engineering and science data, make science decisions, select viable rover targets at a millimeter resolution and validate an uplink bundle for a car sized rover with more complex science instruments than any previous Mars surface mission. All this had to be done within a five hour time frame. Doing this with a small team would be a challenge, but this had to be accomplished by a large team of engineers and scientists located across North America and Europe. Achieving this level of operational efficiency was unheard of in the prime mission. In addition, the mission had another set of requirements that had nothing to do with surface operations; the Mars 2020 Ground Data System (GDS) was also expected to comply with a new set of security requirements to keep up with the ever changing cybersecurity landscape. The Mars 2020 Ground Data System (GDS) is a re-architected version of the Mars Science Laboratory GDS. The primary goal was to integrate the lessons learned from previous Mars surface missions, accommodate a set of new requirements and capabilities required to ensure mission success, and comply with a new set of cybersecurity controls. The new architecture includes several unique qualities including a data lake, language-agnostic system-wide event-based operations, containerization, automated deployment, network segmentation, infrastructure-as-code, API-driven interfaces, and the first Mars surface GDS to operate primarily in the cloud. The new architecture enabled greater access to the system’s data, tighter integration with the operations team, and a higher level of traceability. The availability of the data also enabled a new set of capabilities previously not possible on surface missions. These new capabilities include an autonomous data to information, pipeline for downlink analysis, horizontal scaling of science data processing capabilities, autonomous round trip data tracking of science and engineering data, integration of flight system state into the tactical planning cycle, high fidelity targeting utilizing kinematic data, and hierarchical image and 3d meshes data representations. This paper will introduce the requirements for the Mars 2020 Mission, the heritage architecture, and the rationale for the changes to achieve the new architecture. The paper will continue to describe the fundamental changes made to the GDS architecture, how these changes enabled a more tightly integrated GDS, and the new capabilities that were enabled by the new architecture. The paper will conclude with the lessons learned from the process of rearchitecting a heritage GDS system and from the first 200 days of operations supporting over 800 users from around the world.
Matlab software was written to provide smoothing of radar tracking data to simulate ADS-B (Automatic Dependent Surveillance-Broadcast) data in order to test a tactical conflict probe. The probe, called TSAFE (Tactical Separation-Assured Flight Environment), is designed to handle air-traffic conflicts left undetected or unresolved when loss-of-separation is predicted to occur within approximately two minutes. The data stream that is down-linked from an aircraft equipped with an ADS-B system would include accurate GPS-derived position and velocity information at sample rates of 1 Hz. Nation-wide ADS-B equipage (mandated by 2020) should improve surveillance accuracy and TSAFE performance. Currently, position data are provided by Center radar (nominal 12-sec samples) and Terminal radar (nominal 4.8-sec samples). Aircraft ground speed and ground track are estimated using real-time filtering, causing lags up to 60 sec, compromising performance of a tactical resolution tool. Offline smoothing of radar data reduces wild-point errors, provides a sample rate as high as 1 Hz, and yields more accurate and lag-free estimates of ground speed, ground track, and climb rate. Until full ADS-B implementation is available, smoothed radar data should provide reasonable track estimates for testing TSAFE in an ADS-B-like environment. An example illustrates the smoothing of radar data and shows a comparison of smoothed-radar and ADS-B tracking. This document is intended to serve as a guide for using the smoothing software.
This submission contains processed datasets from a long-term deployment of 3 moorings and a transect survey of the proposed tidal energy site off the East Forelands in Cook Inlet, AK. The long-term mooring datasets were created from 8 instruments mounted on a Terrasond High Energy Oceanographic Mooring (THEOM) bottom lander and two Mid-Water Mooring (MWM) Stablemoor buoys from 1 July 2021 to 31 August 2021 (60 days). The west-most mooring (MWM1) was deployed at 60.720225 N, 151.436196 W in ~50 m of water. The middle mooring (THEOM) was deployed at 60.720703 N, 151.429500 W in ~52 m of water. The east-most buoy (MWM2) was deployed at 60.720081 N, 151.420896 W in ~50 m of water. Each Stablemoor carried three instruments: 1. A Nortek Vector acoustic Doppler velocimeter (ADV) mounted at the Stablemoor's nose. Data were recorded at 8 Hz on a 5 minute duty cycle every 20 minutes. Data was motion-corrected using the internal IMU and external ADCP bottom-track data and then bin-averaged into 4 minute bins and converted to the Principal (streamwise, cross-stream, vertical) coordinate system. (Note: 30 seconds were trimmed from the beginning and end of each 5 minute duty cycle to account for the filter end-effects from turning on and turning off the IMU.) 2. A down-looking Nortek Signature 1000 kHz acoustic Doppler current profiler (ADCP) mounted in the first Stablemoor instrument well. Data were recorded in 2 Hz with 5-beam burst and bottom-track enabled. Processed data has been averaged into 10 minute bins and converted into the Principal coordinate system. 3. An up-looking Nortek Signature 1000 kHz acoustic Doppler current profiler (ADCP) mounted in the second Stablemoor instrument well. Data were recorded at 4 Hz with 5 beam burst enabled. Processed data has been averaged into 10 minute bins and converted into the Principal coordinate system. Note: the down-facing ADCP on MWM1 failed on July 10th, 2021, only recording 9 days of data. Because ADV motion-correction required bottom track, the ADV from MWM1 also only has 9 days processed. Additionally, only 25 days of data were processed from the MWM2 ADV because it appeared to have been impacted by debris on 7/25. Two instruments were mounted on the THEOM (see MHKDR link further below for THEOM raw data): 4. A Nortek Vector acoustic Doppler velocimeter (ADV). Data were recorded at 8 Hz on a 5 minute duty cycle every 20 minutes. Data was bin-averaged into 5 minute bins, and converted to the Principal coordinate system. 5. A Nortek Signature 500 kHz acoustic Doppler current profiler (ADCP). Data were recorded in 4 Hz in the beam coordinate system from all 5 beams. Processed data has been averaged into 10 minutes bins and converted to the Principal coordinate system.
Reference data for advanced microwave and laser communication and tracking systems - Vol. 3
Short arc reduction of satellite Mars tracking data shows that: (1) There is one large gravity high covering the region of Nix Olympica and the three peaks to the east (about 110 deg longitude). It has an amplitude of 50 milligals at 2200-km altitude and implies a surface mass anomaly times greater than any on earth; (2) there are no large negative gravity anomalies comparable to the positive; and (3) the large 3000-km canyon seems to originate in a gravity high and end in a gravity low.
Manual control systems technology - human performance in tracking data acquisition
Guidance, Navigation, and Control (GN&C) is the measurement and control of spacecraft position, velocity, and attitude in support of mission objectives. This paper provides an overview of a preliminary design of the GN&C system of the Lunar Lander Altair. Key functions performed by the GN&C system in various mission phases will first be described. A set of placeholder GN&C sensors that is needed to support these functions is next described. To meet Crew safety requirements, there must be high degrees of redundancy in the selected sensor configuration. Two sets of thrusters, one on the Ascent Module (AM) and the other on the Descent Module (DM), will be used by the GN&C system. The DM thrusters will be used, among other purposes, to perform course correction burns during the Trans-lunar Coast. The AM thrusters will be used, among other purposes, to perform precise angular and translational controls of the ascent module in order to dock the ascent module with Orion. Navigation is the process of measurement and control of the spacecraft's "state" (both the position and velocity vectors of the spacecraft). Tracking data from the Earth-Based Ground System (tracking antennas) as well as data from onboard optical sensors will be used to estimate the vehicle state. A driving navigation requirement is to land Altair on the Moon with a landing accuracy that is better than 1 km (radial 95%). Preliminary performance of the Altair GN&C design, relative to this and other navigation requirements, will be given. Guidance is the onboard process that uses the estimated state vector, crew inputs, and pre-computed reference trajectories to guide both the rotational and the translational motions of the spacecraft during powered flight phases. Design objectives of reference trajectories for various mission phases vary. For example, the reference trajectory for the descent "approach" phase (the last 3-4 minutes before touchdown) will sacrifice fuel utilization efficiency in order to provide landing site visibility for both the crew and the terrain hazard detection sensor system. One output of Guidance is the steering angle commands sent to the 2 degree-of-freedom (dof) gimbal actuation system of the descent engine. The engine gimbal actuation system is controlled by a Thrust Vector Control algorithm that is designed taking into account the large quantities of sloshing liquids in tanks mounted on Altair. In this early design phase of Altair, the GN&C system is described only briefly in this paper and the emphasis is on the GN&C architecture (that is still evolving). Multiple companion papers will provide details that are related to navigation, optical navigation, guidance, fuel sloshing, rendezvous and docking, machine-pilot interactions, and others. The similarities and differences of GN&C designs for Lunar and Mars landers are briefly compared.
Unmanned aircraft will equip with a detect-and-avoid (DAA) system that enables them to comply with the requirement to "see and avoid" other aircraft, an important layer in the overall set of procedural, strategic and tactical separation methods designed to prevent mid-air collisions. This paper describes a capability called Java Architecture for Detect and Avoid Extensibility and Modeling (JADEM), developed to prototype and help evaluate various DAA technological requirements by providing a flexible and extensible software platform that models all major detect-and-avoid functions. Figure 1 illustrates JADEM's architecture. The surveillance module can be actual equipment on the unmanned aircraft or simulators that model the process by which sensors on-board detect other aircraft and provide track data to the traffic display. The track evaluation function evaluates each detected aircraft and decides whether to provide an alert to the pilot and its severity. Guidance is a combination of intruder track information, alerting, and avoidance/advisory algorithms behind the tools shown on the traffic display to aid the pilot in determining a maneuver to avoid a loss of well clear. All these functions are designed with a common interface and configurable implementation, which is critical in exploring DAA requirements. To date, JADEM has been utilized in three computer simulations of the National Airspace System, three pilot-in-the-loop experiments using a total of 37 professional UAS pilots, and two flight tests using NASA's Predator-B unmanned aircraft, named Ikhana. The data collected has directly informed the quantitative separation standard for "well clear", safety case, requirements development, and the operational environment for the DAA minimum operational performance standards. This work was performed by the Separation Assurance/Sense and Avoid Interoperability team under NASA's UAS Integration in the NAS project.
This milestone evaluates techniques to measure and, if possible, reduce data movement across all levels of the memory hierarchy, focusing on CPU/GPU page level data movement and on intra-GPU memory hierarchy. We quantitatively evaluate the efficacy of the techniques in reducing data movement and measure how performance tracks data movement reduction. We study a small collection of benchmarks and proxy mini-apps that run on advanced pre-exascale GPUs and on the Accelsim GPU simulator. Our approach has two thrusts: to measure advanced data movement reduction directives and techniques on the newest available GPUs, and to evaluate our benchmark set on simulated GPUs configured with architectural refinements to reduce data movement. We primarily evaluated NVidia-based architectures due to the unavailability of AMD GPU hardware and tools until very recently.
Orbit parameters identification method based on given tracking data span applied to lunar orbiter tracking using Fourier analysis
The first report in a series is presented which is intended to be written by the author with the purpose of treating a class of approximation methods of functions in one and several variables and ways of applying them to geophysics and geodesy. The first report is divided in three parts and is devoted to the presentation of the mathematical theory and formulas. Various optimal ways of representing functions in one and several variables and the associated error when information is had about the function such as satellite data of different kinds are discussed. The framework chosen is Hilbert spaces. Experiments were performed on satellite altimeter data and on satellite to satellite tracking data.
The FGGE/SBUV Level 2C data set consists of 12 9-track data tapes, each of which contains total ozone and ozone profile data for one calendar month grouped in files containing the data in a 6 hour synoptic time block. The data flow and quality checks in the production of this data set are described as well as the format of the data tapes and the accompanying shipping documents.
Fission tracking techniques were used to measure the uranium distribution in meteoritic troilite and graphite. The obtained fission tracking data showed a heterogeneous distribution of tracks with a significant portion of track density present in the form of uranium clusters at least 10 microns in size. The matrix containing the clusters was also heterogeneous in composition with U concentrations of about 0.2-4.7 ppb. U/He ages could not be estimated on the basis of the heterogeneous U distributions, so previously reported estimates of U/He ages in the presolar range are probably invalid.
Four test pilots were instrumented for in-flight EEG recordings using a custom portable recording system. Each flew six, two minute tracking tasks in the Calspan NT-33 experimental trainer at Edwards AFB. With the canopy blacked out, pilots used a HUD display to chase a simulated aircraft through a random flight course. Three configurations of flight controls altered the flight characteristics to achieve low, moderate, and high workload, as determined by normative Cooper-Harper ratings. The test protocol was administered by a command pilot in the back seat. Corresponding EEG and tracking data were compared off-line. Tracking performance was measured as deviation from the target aircraft and combined with control difficulty to achieve an estimate of 'cognitive workload'. Trended patterns of parietal EEG activity at 8-12 Hz were sorted according to this classification. In all cases, high workload produced a significantly greater suppression of 8-12 Hz activity than low workload. Further, a clear differentiation of EEG trend patterns was obtained in 80 percent of the cases. High workload produced a sustained suppression of 8-12 Hz activity, while moderate workload resulted in an initial suppression followed by a gradual increment. Low workload was associated with a modulated pattern lacking any periods of marked or sustained suppression. These findings suggest that quantitative analysis of appropriate EEG measures may provide an objective and reliable in-flight index of cognitive effort that could facilitate workload assessment.
The NASA JAO/ES-MCAT (Eugene Stansbery Meter Class Autonomous Telescope) Facility is nearing Full Operational Capability, or FOC. ES-MCAT is now fully capable of autonomously running all observations, including: (a) monitoring weather and closing when conditions are not safe, as well as halting observations when conditions are not suitable (e.g. too cloudy) for operations, (b) start-up/shut-down nightly tasking, (c) collecting calibration data and survey or TLE-tracked data, and (d) processing all collected data, including on-chip photometry and astrometry calibrations using the GAIA star catalogue. The processed data are then further analyzed at NASA Johnson Space Center to correlate detections with known objects in the Space Surveillance Network (SSN) catalogue. MCAT can collect data of specific objects with known orbits or can search for objects with orbits similar to those of spacecraft or rocket bodies that have recently broken up. However, the primary goal for ES-MCAT is to survey the geosynchronous (GEO) belt to provide a statistical sample of the GEO debris environment for both engineering models for spacecraft designers and long-term environment evolutionary purposes. The approach for sweeping the sky to statistically survey GEO has been investigated and updated from past surveys taken by NASA and will be reported, herein referred to as the Candy Cane method. ES-MCAT’s optical performance and the limiting magnitude for the full optical system will be discussed. An analysis used to determine which filter to use for GEO surveys (SDSS r′) includes combining the reflectivity of the primary and secondary mirrors, transmission of the field corrector and CCD window, and the quantum efficiency of the CCD detector, resulting in throughput of the full optical path. This throughput is then combined with the expected typical transparency of the atmosphere at ES-MCAT’s altitude/location for the Sloan Digital Sky Survey (SDSS) g′r′i′z′ and Johnson/Kron-Cousins BVRI filters to yield expected relative throughput.
Key interfaces are described for all LST mission phases: ground test and integration, prelaunch and launch operations, ascent, deployment, operations, on-orbit maintenance, retrieval, deorbit and landing, and refurbishment. These interfaces can be categorized as test and integration, launch operations, Shuttle, data, and mission operations. The interface with the Shuttle and the Shuttle crew is emphasized here because the Shuttle allows a new capability: on-orbit maintenance and ground return. The LST will communicate with the ground elements of the LST system through a space link by means of the Tracking Data Relay Satellite System or directly to the stations of the Space Tracking and Data Network.