REVIEW 1 cited by
General relativistic observables of the GRAIL mission
Not yet reviewed by Pith; the record is open.
This paper has not been read by Pith yet. Machine review is queued; the pith claim, tier, and objections will appear here once it completes.
SPECIMEN: schema-true, not a live event
T0 review · schema-true
One-sentence machine reading of the paper's core claim.
pith:XXXXXXXX · record.json · timestamp
abstract
We present a realization of astronomical relativistic reference frames in the solar system and its application to the GRAIL mission. We model the necessary spacetime coordinate transformations for light-trip time computations and address some practical aspects of the implementation of the resulting model. We develop all the relevant relativistic coordinate transformations that are needed to describe the motion of the GRAIL spacecraft and to compute all observable quantities. We take into account major relativistic effects contributing to the dual one-way range observable, which is derived from one-way signal travel times between the two GRAIL spacecraft. We develop a general relativistic model for this fundamental observable of GRAIL, accurate to 1 $\mu$m. We develop and present a relativistic model for another key observable of this experiment, the dual one-way range-rate, accurate to 1 $\mu$m/s. The presented formulation justifies the basic assumptions behind the design of the GRAIL mission. It may also be used to further improve the already impressive results of this lunar gravity recovery experiment after the mission is complete. Finally, we present transformation rules for frequencies and gravitational potentials and their application to GRAIL.
Forward citations
Cited by 1 Pith paper
-
Relativistic framework for high-precision GNSS processing in GCRS/BCRS with extension to cislunar space
A JPL team derives error-budgeted GCRS↔BCRS state transformations, demonstrates few-mm 24-hour frame closure in GipsyX, and defines lunar reference/time scales (LCRS/TCL/TL) for cislunar use.
Discussion (0). Continue with ORCID to comment.