Learning

Classify asteroid orbits using machine learning

Check near-Earth asteroid orbit-group labels from orbital elements

This reproducible catalogue benchmark maps eleven orbital and photometric fields to the Amor, Apollo or Aten group. The fixed 11–3 softmax model classifies 317 of 344 held-out records correctly. Its 92.2% accuracy must be read alongside 67.9% balanced accuracy and 22.2% Aten recall.

92.2%held-out accuracy
0.715macro-F1
22.2%Aten recall
344held-out test records

1. Scientific objective

The objective is to reproduce an existing near-Earth-object orbit-group label from catalogue fields. The learned classifier is useful as a data-pipeline consistency check and as a compact multiclass benchmark. Because Amor, Apollo and Aten classes are defined by explicit orbital-element boundaries, the network does not replace the authoritative rule-based classification.

Catalogue consistency

Flag records whose learned class disagrees with the stored label or with the deterministic orbital-element rule.

Pipeline verification

Exercise schema validation, feature ordering, multiclass inference and class-level monitoring in a reproducible workflow.

Boundary review

Identify low-margin cases near group boundaries for inspection instead of treating every softmax score as equally certain.

Planetary defenceNEO catalogue teamsAstronomical data scienceScientific software validation
Scope. This example classifies catalogue orbit groups. It does not propagate an orbit, estimate impact probability, determine potentially hazardous asteroid status or replace review of orbital uncertainty and observation quality.

2. Data and provenance

The downloadable orbit_class.csv contains 1,722 complete, non-duplicated records. The target is strongly imbalanced: 1,477 Apollo records (85.8%), 149 Aten records (8.7%) and 96 Amor records (5.6%).

The field names below are the exact names used by the updated CSV and Python export.

CSV fieldMeaningUnit or scale
semi_major_axisSemimajor axis, aAU
eccentricityOrbital eccentricity, edimensionless
inclinationInclination to the reference plane, idegrees
argument_of_perihelionArgument of perihelion, ωdegrees
longitude_of_ascending_nodeLongitude of the ascending node, Ωdegrees
mean_anomalyMean anomaly at the catalogue epoch, Mdegrees
perihelion_distancePerihelion distance, qAU
aphelion_distanceAphelion distance, QAU
orbital_periodOrbital periodJulian years
absolute_magnitudeAbsolute magnitude, Hmagnitude
earth_moidMinimum orbit-intersection distance with EarthAU
orbit_classTarget group: AMO, APO or ATEcategorical

Authoritative class boundaries

CodeGroupJPL orbital-element definition
AMOAmora > 1.0 AU and 1.017 < q < 1.3 AU
APOApolloa > 1.0 AU and q < 1.017 AU
ATEAtena < 1.0 AU and Q > 0.983 AU
SubsetRowsPurpose
Training1,034Estimate the 36 model parameters
Selection344Monitor generalization during fixed-architecture training
Testing344Report final performance once
Orbit-class distribution dominated by Apollo records
The Apollo class represents 85.8% of the records. Class-level recall and macro metrics are therefore more informative than accuracy alone.
Pearson associations between orbital inputs and an encoded orbit-class target
The chart uses a numerical encoding of a nominal three-class target. Its coefficients depend on that coding and should not be interpreted as physical importance or causality.
Provenance. The working table is based on the Orbit Classification For Prediction data set. The article uses NASA/JPL definitions for the scientific meaning of the three orbit groups. The downloaded table does not provide object identifiers, orbit epochs, covariance information or observation provenance, which limits independent catalogue verification.

3. Model

All eleven numeric inputs use mean-and-standard-deviation scaling. The fixed model connects them directly to three softmax outputs ordered as AMO, APO and ATE. It has no hidden layer and contains 36 trainable parameters, so it is a multiclass logistic model expressed in Neural Designer’s neural-network framework.

This is both the base and final architecture. No neuron-selection task is used in this example.

Output contract. The largest softmax score determines the predicted group. These scores have not been independently calibrated as probabilities; low-margin or rule-disagreeing records should be reviewed.
Fixed asteroid orbit classifier with eleven scaled inputs and three softmax class outputs
Fixed 11–3 softmax architecture used as both the base and final model; there is no hidden layer or neuron-selection stage.

4. Training strategy

The model minimizes multiclass cross-entropy with the quasi-Newton method and no explicit regularization. Training stopped at the configured loss goal after 87 completed epochs (88 stored iterations): cross-entropy decreased from 1.1373 to 0.0008 on training data, while selection cross-entropy changed from 0.6998 to 0.1920.

The selection error reached its lowest stored value, 0.0792, at epoch 59 and then increased while training error continued to fall. This divergence is evidence of overfitting after that point; production work should restore the best-selection checkpoint or apply early stopping.

Training and selection cross-entropy histories over 87 epochs
The fixed architecture fits the training subset almost perfectly, but its selection error rises after epoch 59.

5. Model selection and baseline

No neuron selection was performed, and no architecture selection was performed. The direct 11–3 softmax architecture was fixed before training and retained as the final model. The selection subset was used only to monitor generalization.

Baselines that matter for this scientific task

MethodTesting accuracyBalanced accuracyInterpretation
Always predict Apollo87.2%33.3%High apparent accuracy caused by class imbalance
Fixed neural model92.2%67.9%Improves aggregate classification but misses most Aten records
NASA/JPL boundary rules100.0%100.0%Expected benchmark because the target is defined from orbital elements
Why the rule baseline is essential. Applying the published Amor, Apollo and Aten boundaries reproduces all 344 testing labels. Across the full CSV it reproduces 1,721 of 1,722 labels; the sole exception has q exactly 1.017 AU, a boundary value excluded by the strict inequalities above.

6. Scientific validation

The held-out subset contains 17 Amor, 300 Apollo and 27 Aten records. The model correctly classifies 317 of 344 records, but the confusion matrix shows that 21 of the 27 Aten records are assigned to Apollo.

MetricValueInterpretation
Accuracy92.15%317 correct classifications from 344 testing records
Macro precision91.63%Unweighted mean precision across the three groups
Balanced accuracy / macro recall67.86%Unweighted mean recall; exposes weak Aten sensitivity
Macro-F171.46%Unweighted harmonic-mean performance across groups
Weighted-F190.34%F1 weighted by the imbalanced testing prevalence

Confusion matrix

Actual / predictedAmorApolloAtenTotal
Amor143017
Apollo32970300
Aten021627
Total173216344

Per-class performance

GroupTesting rowsPrecisionRecallF1
Amor1782.35%82.35%82.35%
Apollo30092.52%99.00%95.65%
Aten27100.00%22.22%36.36%
Scientific interpretation. The high overall accuracy is driven by the dominant Apollo class. For catalogue quality control, the 22.2% Aten recall is the limiting result. The deterministic boundary classifier is both simpler and more accurate for assigning these defined orbit groups.

7. Inference and reproducibility

A professional workflow should validate the schema and units, calculate the deterministic NASA/JPL group, optionally run the learned classifier as an independent consistency check, and route disagreements or low-score-margin cases to review. Hazard assessment is a separate workflow that requires more than an orbit-group label.

Orbit solution
Schema and unit checks
JPL boundary rule
Model consistency score
Disagreement review
Catalogue record

Representative catalogue-consistency case

This operating point is inside the training ranges and is stored in the Neural Designer project. Its a and q values satisfy the Apollo definition.

InputValueInputValue
Semimajor axis1.52 AUEccentricity0.34
Inclination14.6°Argument of perihelion197°
Ascending-node longitude200°Mean anomaly118°
Perihelion distance1.00 AUAphelion distance2.05 AU
Orbital period1.88 yearsAbsolute magnitude21.4
Earth MOID0.016 AURule-based groupApollo
Model resultAPO

Softmax scores: AMO 4.27%, APO 95.73%, Aten <0.01%. The model and boundary rule agree.

Do not infer hazard from this result. A small Earth MOID or an Apollo label alone is not an impact probability. Potentially hazardous asteroid screening additionally uses an absolute-magnitude threshold, and operational risk assessment requires an orbit solution with uncertainty and dedicated impact monitoring.

Try the exported orbit classifier

Enter an operating point using the same units and field order as the published CSV. Decimal commas and decimal points are accepted.

Research demonstration. The calculation runs locally with the exact exported weights and preprocessing. Values outside the validated domain are rejected. Scores are not calibrated probabilities, and this component does not assess impact risk.

Reproduce the calculation

The Python package contains the exact exported model, ordered input schema, representative case and expected softmax scores. The Neural Designer package preserves the 1,034/344/344 split, trained parameters and regenerated analyses.

from model import NeuralNetwork

inputs = [1.52, 0.34, 14.6, 197, 200, 118, 1.00, 2.05, 1.88, 21.4, 0.016]
amo, apo, ate = NeuralNetwork().calculate_outputs(inputs)

8. Validity, uncertainty and limitations

  • The label is rule-derived. Amor, Apollo and Aten groups are defined from orbital elements. A deterministic implementation is the appropriate production classifier; the learned model is a benchmark or consistency check.
  • Class imbalance is substantial. Apollo records are 85.8% of the data. Accuracy therefore overstates performance on the minority Aten class.
  • Training continued beyond the best selection epoch. Selection cross-entropy was lowest at epoch 59 and rose to 0.192 by epoch 87. The published export does not restore that earlier checkpoint.
  • Random row validation is limited. It measures interpolation within this curated table, not transfer to later catalogue epochs, newly discovered objects or lower-quality orbit solutions.
  • Uncertainty is absent. The CSV contains point estimates but no covariance matrices, observational arcs, condition codes or measurement uncertainties.
  • The source table lacks object identity. Without catalogue identifiers and epochs, records cannot be independently reconciled with the current JPL Small-Body Database.
  • Softmax scores are not calibrated probabilities. They should not be interpreted as scientific confidence or impact risk.

References