Traitement massif en double différence de données GNSS dans le cadre de l'infrastructure EPOS

Présentation de Gaël Janex (ISTerre) | Rencontres scientifiques et techniques Résif | 15-18 novembre 2021, Obernai

1. EPOS-GNSS - Processing GNSS data with gamit/globk Rencontres RESIF November 18th 2021 Gaël Janex, Anne Socquet, Andrea Walpersdorf ...and previously Aline Déprez, Alizia Tarayoun, Nathalie Cotte, Mary Grace Bato
2. EPOS Goal : answering some of the most pressing societal questions concerning geo-hazards and those geodynamic phenomena relevant to the environment and human welfare. The European Plate Observing System is a multidisciplinary, distributed research infrastructure that facilitates the integrated use of data, data products, and facilities from the solid Earth science community in Europe. EPOS ensures the long-term access to solid Earth science data and services.
3. EPOS-GNSS EPOS-GNSS is one of the 9 EPOS Thematic Core Service (TCS) The mission of the GNSS TCS is to provide access to GNSS data, metadata, products, and software in support of the Solid Earth Sciences. To achieve this goal, EPOS-GNSS: • coordinates the archiving and distribution of relevant GNSS data, metadata and data products • promotes best practice for GNSS station operation, data quality control and data management • maintains and distributes open source software for GNSS data, metadata and product discoverability 14 services (Data, Data Products, Software and Services) 3 community portals : Metadata : Data : Products : gnss-metadata.eu gnssdata-epos.oca.eu gnssproducts.epos.ubi.pt
4. GNSS processing within EPOS-GNSS UGA / CNRS deliverables : • Double-difference processing (GAMIT/GLOBK, Herring et al., 2015) • Time series for EPOS stations • Automatic d+2 and d+25 processing • Velocities derived from time series INGV deliverables : • PPP (Precise Point Positioning) processing (GIPSY) • Time series for EPOS stations • Velocities derived from time series
5. Why double-difference ? • Takes out satellite and receiver clock errors from calculations • Reduces the effect of orbit errors • Reduces the effect of wave propagation unknowns in the atmosphere • Since we calculate baselines (distance between each receiver pair), computation costs rise geometrically with number of processed stations => The dataset is split into subnetworks => Need to combine subnetwork results together, and reference using IGS stations • Need to reprocess whole data when new stations (with old data) are added baseline
6. gamit/globk processing flow
7. gamit subnetwork processing
8. netsel (subnetwork creation) For each day independently, the station network is split into subnetworks (up to 40 stations) Overlapping stations between local networks 1 large tying network Example for day 2020 223 572 stations 16 networks
9. gamit subnetwork processing
10. Large number of small compute jobs : Use of the UGA mutualized high-performance computing platform (ciment) • Cigri compute grid job submission (best effort mode) • Input data and results go through iRODS distributed data storage • Technical IT support provided by the Gricad team. Period gamit subnetwork processing (~ 30 min runtime) globk daily combinations (~ 1 min runtime) 1 day 1 per subnet : 16-18 currently 1 1 year ~ 6000 365 2000-2021 ~ 80000 ~ 8000
11. Example time series : ENTZ, gamit processing compared to NGL PPP processing Example time series in ITRF14, eurasia fixed (Altamimi 2017)
12. Example time series with post-seismic (2014-2015, western Greece) Example time series in ITRF14, eurasia fixed (Altamimi 2017)
13. Example time series with post-seismic (L’Aquila, 2016, Italy) Example time series in ITRF14, eurasia fixed (Altamimi 2017)
14. Horizontal velocities produced from time series using MIDAS Reference : Eurasia fixed (Altamimi 2017) - MIDAS : Blewitt et al., 2016 - Input data : time series - Velocity is the most frequent 1-year position shift (sliding window) - Robust : low sensitivity to outliers, steps, seasonal component. - Fast (a few minutes for this data set) 615 velocities calculated : - 576 showed here - 39 not showed (high errors)
15. Horizontal velocities produced from time series using MIDAS Reference : Eurasia fixed (Altamimi 2017) Focus on central Europe
16. Horizontal velocities produced from time series using MIDAS Reference : Eurasia fixed (Altamimi 2017) Focus on « stable » western Europe Velocity and errors scaled up for plot
17. Vertical velocities produced from time series using MIDAS
18. Vertical velocities Alps and Italy
19. Comparison of velocities : our DD solution vs INGV PPP solution INGV produces a PPP solution (Gipsy) Velocities are also estimated with Midas Very good match for most of the 427 stations compared : • 2 stations with horizontal diff > 1mm/yr • 2 stations with vertical diff > 2mm/yr Std Dev 0.16 mm/yr 0.17 mm/yr 0.47 mm/yr
20. Ongoing / future work • Valorization through RESIF-RENAG web site, and integration in RENAG combined solution
21. Ongoing / future work • Valorization through RESIF-RENAG web site, and integration in RENAG combined solution • Automate the times series analysis for offset calculations, using trajectory models tools developped at ISTerre in recent years.