Rendezvous Phasing Period
Choose a phasing-loop period for point rendezvous after supplied target revolutions; no safe pericenter or burn budget is inferred.
Description
Rendezvous phasing changes the time taken to complete a loop so two objects return to the same point together.
Rendezvous phasing changes the time taken to complete a loop so two objects return to the same point together. Target phase and integer loop counts specify the desired meeting time.1
Choose a phasing-loop period for point rendezvous after supplied target revolutions; no safe pericenter or burn budget is inferred.
When to use Rendezvous Phasing Period
Use this tool to choose a phasing-loop period for point rendezvous after supplied target revolutions; no safe pericenter or burn budget is inferred.
Prepare the orbital state or model parameters in one reference frame. Confirm compatible distance/time units and the stated angular and gravitational-parameter conventions.
How to use Rendezvous Phasing Period and understand its results
- Prepare the orbital state or model parameters in one reference frame. Confirm compatible distance/time units and the stated angular and gravitational-parameter conventions.
- Enter targetOrbitPeriod, targetAheadDegrees, targetRevolutions, phasingLoops using the field table and calculation rules, then run the tool.
- Read requiredPhasingPeriod, rendezvousElapsedTime. The explanation below defines the units, signs, ordering and any flags or placeholder values.
- If the tool reports an input issue, correct the values and run it again. Apply the stated assumptions when interpreting a successfully returned result.
| Input field | Meaning | Value type; see rules below | Requirement |
|---|---|---|---|
| targetOrbitPeriod | Target orbit period | number | Required |
| targetAheadDegrees | Target ahead degrees | number | Required |
| targetRevolutions | Target revolutions | integer | Required |
| phasingLoops | Phasing loops | integer | Required |
Enter a positive target period, positive integer target revolutions and phasing loops, and a target-ahead angle in [0,360). The tool subtracts the fractional lead from the target revolutions and divides the resulting elapsed time by the phasing loop count. Both returned times retain the period's unit.
elapsed = (targetRevolutions − aheadDegrees/360) × targetPeriod; phasingPeriod = elapsed/phasingLoops Units, indexing, boundary conditions and exceptional cases are defined in the calculation rules above.
| Output field | Meaning | Value type |
|---|---|---|
| requiredPhasingPeriod | Required phasing period | number |
| rendezvousElapsedTime | Rendezvous elapsed time | number |
{
"input": {
"targetOrbitPeriod": 100,
"targetAheadDegrees": 90,
"targetRevolutions": 1,
"phasingLoops": 1
},
"output": {
"requiredPhasingPeriod": 75,
"rendezvousElapsedTime": 75
}
}Limitations and assumptions
This is timing for a point rendezvous, without a burn budget, safe periapsis, plane alignment or full encounter trajectory. Integer counts must be chosen independently.
Numeric inputs must be finite. Follow the calculation-specific rules for overflow, underflow and exceptional cases. Missing required fields, extra fields, wrong value types and violations of the calculation rules are input errors.
Alternative or Complementary methods
Use Phasing Loop Catchup Count: Estimate loops to pass a target phase under constant per-loop advance; overshoot is reported rather than claiming exact rendezvous. For a complementary task, use Keplerian Orbital Period: Compute a two-body elliptic orbital period from semimajor axis and total gravitational parameter, not a fixed planetary lookup.
References
-
Rendezvous Phasing Period — tool.io
Similar or alternative tools
- Phasing Loop Catchup Count
Estimate loops to pass a target phase under constant per-loop advance; overshoot is reported rather than claiming exact rendezvous.
- Keplerian Orbital Period
Compute a two-body elliptic orbital period from semimajor axis and total gravitational parameter, not a fixed planetary lookup.