Francesco Gianotto
I am an Orbital Dynamicist at the European Space Agency's Near-Earth Object Coordination Centre (NEOCC). My work focuses on asteroid orbit determination, impact monitoring, and planetary defence operations. I am responsible for the operational use and validation of the Aegis software system and contribute to its evolution within NEOCC activities. I am also a developer and user of Meerkat Asteroid Guard, a software platform for imminent impactor detection, impact-risk assessment, and alert management.
Sessions
Astrometric residuals, the difference between the measured position of an object and the position predicted by orbital calculations at the time of observation, constitute a fundamental diagnostic as they can reveal limitations in the dynamical model or errors in the measurements. This can be particularly relevant for newly discovered asteroid imminent impactors which usually have only a few observation and astrometric errors could bias the orbital solution and the resulting impact prediction. Providing observatories with timely and transparent feedback on the quality of their astrometry is therefore essential for improving individual measurements and the overall reliability of the orbit solutions.
The ESA Near-Earth Object Coordination Centre (NEOCC) has recently released a new suite of free and publicly available tools for astrometric residual analysis, integrated into its NEO Portal. These include the “Observations Analysis” and “Observatories” pages[1, 2], together with a dedicated “Residuals” tab on individual object pages (e.g., (99942) Apophis) [3], offering interactive visualizations, advanced filtering, per-observatory statistics, and downloadable datasets[1]. Based on the output of the NEOCC orbit determination software Aegis[4], the tool shows astrometric residuals on demand for any object, at any epoch, and for every contributing observatory, transforming what was previously an internal diagnostic capability into a public resource.
We will demonstrate the tool live, showing how both professional and amateur observers can use it to assess the quality of their measurements, identify possible timing biases (e.g. Figure 1, left), and other systematic deviations in their astrometric submissions. It can be used to validate the overall performance of an observing system and to improve its hardware, software or configuration.
In addition to the live demonstration, we will present results from mining and analysing more than half a billion processed observations using these tools. We will present two still unrecognized systematic patterns in the mean astrometric residuals: one affecting the largest asteroid surveys (e.g. Figure 1, top right), and another one correlated with position on the celestial sphere (e.g. Figure 1 bottom right). The origin of these systematic effects remains under investigation, and a detailed analysis will be presented in a paper currently being prepared.
[1] https://neo.ssa.esa.int/observatories
[2] https://neo.ssa.esa.int/observations-analysis?tab=res_ra_vs_dec&obs_code=F51
[3] https://neo.ssa.esa.int/search-for-asteroids?sum=1&des=99942%20Apophis
[4] https://ui.adsabs.harvard.edu/abs/2024CeMDA.136...58F
The ESA Near-Earth Object Coordination Centre (NEOCC) is responsible for the monitoring of Near-Earth Objects and the assessment of potential impact hazards. These activities rely on Aegis [1], a software system for asteroid orbit determination, ephemerides generation, uncertainty propagation, close-approach analysis, and impact monitoring. The results and computational capabilities of Aegis are made available to the community through the NEOCC web portal [2] and dedicated APIs [3]. As operational demands evolved, Aegis transitioned from a standalone scientific application to a service deployed within ESA's cloud infrastructure.
This contribution presents the architectural evolution of Aegis and the engineering decisions that enabled its migration to a distributed operational environment while preserving a mature and validated scientific code base. The original system was conceived as a largely monolithic application running on a single machine. Rather than pursuing a complete redesign, the development strategy focused on incremental modernisation, gradually introducing containerisation, automated testing and deployment workflows, service-oriented interfaces, and distributed execution capabilities.
Today, Aegis operates as a collection of Docker-based services deployed on ESA Cloud using Docker Swarm orchestration. Scientific processing remains largely performed by established Fortran components, while Python services coordinate workflows, expose REST interfaces, and exchange information through Redis-based messaging queues. Although parts of the system still rely on shared file-system access, reflecting historical design choices, this approach has proven adequate for current operational requirements and data volumes while allowing progressive migration towards more centralised data management solutions. The software has also been deployed on ESA High-Performance Computing (HPC) infrastructures, requiring targeted adaptations but without fundamental changes to its scientific components.
Modern software engineering often favours highly scalable cloud-native solutions. However, scientific operational systems frequently evolve under different constraints, including long-lived code bases, limited development resources, strict reliability requirements, and moderate data volumes. The Aegis experience shows that significant gains in maintainability, deployment flexibility, and operational robustness can be achieved through incremental modernisation, without the need for unnecessarily complex architectures.
[1] https://doi.org/10.1007/s10569-024-10225-z
[2] https://neo.ssa.esa.int/
[3] https://neo.ssa.esa.int/computer-access
The increasing discovery rate of near-Earth objects requires software systems capable not only of orbit analysis, but also of continuous data ingestion, automated decision-making, and rapid dissemination of actionable information. We present Meerkat Asteroid Guard [1], the European Space Agency's operational imminent impactor monitoring system, developed and maintained at the Near-Earth Object Coordination Centre (NEOCC). Since becoming operational in 2021, Meerkat has contributed to the identification and follow-up of all known pre-impact asteroid discoveries detected during its operational lifetime.
Meerkat continuously monitors newly reported objects on the Minor Planet Center's Near-Earth Object Confirmation Page, automatically detecting updates, retrieving observations, and executing orbit determination and impact assessment workflows. The system produces a range of data products, including impact probabilities, uncertainty visualizations, follow-up pointing recommendations, impact corridors, and object classification summaries, which are distributed to analysts and observers in near real time.
This contribution focuses on the software architecture and operational design of the system rather than on the underlying orbital algorithms. Meerkat employs a deliberately simple and maintainable architecture based on containerized services, automated pipelines, multiprocessing, and CI/CD practices. The software is designed for robustness, transparency, and ease of maintenance, allowing reliable 24/7 operation while remaining adaptable to evolving planetary-defence requirements.
Particular attention is given to the alerting framework. Through email notifications, messaging systems, and automated phone calls, Meerkat acts as a catalyst for rapid international follow-up campaigns. Through dedicated mailing lists, alerts are distributed to professional and amateur astronomers across multiple continents, enabling rapid follow-up observations to refine orbit solutions and confirm or rule out potential impact scenarios. Meerkat therefore provides a practical example of how astronomy software can bridge automated data processing and global scientific collaboration in a time-critical operational environment.
[1] https://doi.org/10.1007/s40295-025-00560-0