Exoplanet Period From Transit Spacing

Transit timing linear fit with independently identified missing-cycle ordinals, not average adjacent gaps or automatic integer-cycle resolution. Model only, not an ephemeris, measured stellar identity or observational guarantee.

Description

Transit timing needs cycle identifiers to distinguish neighboring events from missed cycles.

Transit timing needs cycle identifiers to distinguish neighboring events from missed cycles.1

A linear fit estimates a period while residuals preserve deviations from that timing model. Use Exoplanet Period From Transit Spacing to evaluate the supplied inputs under the model explained below.

When to use Exoplanet Period From Transit Spacing

Use Exoplanet Period From Transit Spacing to evaluate the supplied inputs under the model explained below. Establish the units, measurement scope and model assumptions before entering values.

How to use Exoplanet Period From Transit Spacing and understand its results

  1. Establish the units, measurement scope and model assumptions before entering values.
  2. Enter Observed transit times days, Caller integer cycle ordinals using the field table and validation rules below, then run the tool.
  3. Read Least squares orbital period days, Transit timing residuals days; interpret the units, signs, ordering and unknown-value placeholders described below.
  4. Correct reported input errors and rerun. Apply successful results according to their specific meanings and check the assumptions before using them in a decision.
Input fieldMeaningValue typeRequirement
observedTransitTimesDaysObserved transit times daysarray of numberRequired; constraints below
callerIntegerCycleOrdinalsCaller integer cycle ordinalsarray of numberRequired; constraints below

Enter 2–10000 nonempty aligned transit times in days and strictly increasing safe-integer cycle ordinals, which may skip cycles or use signed labels. Fit ordinary least squares with ordinal as x and time as y, requiring positive fitted slope. Return period in days and residuals in original order. The times need not individually increase if the slope remains positive. No cycle discovery, timing uncertainties or transit search occurs.

periodDays=OLSslope(cycleOrdinals,times); residual=time−intercept−period×cycle

Use the field order, units and branch conditions described above.

Output fieldMeaningValue type
leastSquaresOrbitalPeriodDaysLeast squares orbital period daysnumber
transitTimingResidualsDaysTransit timing residuals daysarray of number
json
{
  "input": {
    "observedTransitTimesDays": [
      0,
      10,
      30
    ],
    "callerIntegerCycleOrdinals": [
      0,
      1,
      3
    ]
  },
  "output": {
    "leastSquaresOrbitalPeriodDays": 9.999999999999998,
    "transitTimingResidualsDays": [
      -3.552713678800501e-15,
      -1.7763568394002505e-15,
      3.552713678800501e-15
    ]
  }
}

Limitations and assumptions

A linear fit estimates a period while residuals preserve deviations from that timing model. Apply the exact scope and assumptions explained above.

All listed fields require explicit values. Unexpected fields, incorrect types, nonfinite numbers and sparse arrays fail validation. Domain-specific bounds, alignments and supported tokens are explained above; extremely large inputs or outputs can also be rejected. Input errors differ from successful false results, empty match lists and unknown-evidence placeholders.

Alternative or Complementary methods

Use Exoplanet Transit Depth Percent for a related task: An ideal opaque transit blocks a fraction of a uniformly bright stellar disk.

Use Exoplanet Equilibrium Temperature for a related task: Equilibrium temperature balances absorbed and reradiated energy in an ideal model.

References

  1. Exoplanet Period From Transit Spacing — tool.io

Similar or alternative tools

Don't forget to set a bookmark for tool.io!
Privacy | Imprint | Cookies