How pridelab/pride-pppar works
Project type and purpose
• PRIDE-PPPAR is an open-source scientific computation package (CLI + light GUI) for Precise Point Positioning with Ambiguity Resolution (PPP-AR) in multi-GNSS.
• It is not a web or mobile app—rather it’s a high-performance Fortran/C core wrapped by shell/Python scripts and an optional GUI for early-career users.
Top-level architectural components
A. Input & configuration layer
• RINEX observation/navigation files (via “example/data” or user-provided).
• GNSS products: orbit/clock/bias (downloaded by scripts).
• Configuration files and atmospheric grids (under “table/”).
B. Pre-processing & data preparation
• tedit module: RINEX quality checks & editing.
• redig module: cycle-slip detection and flagging of residuals.
• scripts/pdp3.sh: master orchestration script for data download & parameter dispatch.
C. Core computation engines
• spp (single point positioning)
• arsig (phase-bias alignment & ambiguity candidate search)
• lsq (least-squares estimator for parameter adjustment)
• mhm (multipath hemispherical map compensation)
• orbit (kinematic orbit determination for LEO)
• otl (ocean tide loading correction)
• utils (common utilities)
– Each subfolder in src implements one module with its own Makefile.
D. Post-processing & results
• scripts/plot*.sh & plot*.py for visualization.
• CLI outputs: .kin, .res, .amb, .ztd, .htg, etc.
• example/results_ref for regression tests and reference outputs.
E. User interface
• GUI executables in gui/: thin wrapper invoking pdp3.sh under the hood.
• install.sh for environment setup.
Relationships & data flows
1. User invokes GUI or pdp3.sh (entry point) →
2. pdp3.sh downloads GNSS products and invokes tedit/redig for raw data cleaning →
3. Pre-processed RINEX + bias products are fed into spp to compute initial position and residuals →
4. arsig reads residuals & bias streams to search/fix ambiguities →
5. lsq performs parameter estimation (epoch by epoch or multi-day) using utilities & lib routines →
6. mhm, orbit, otl modules are called as optional sub-steps (controlled by flags) →
7. Final result files are written; plot scripts can be run.
Architectural patterns & design principles
• Modular design: each GNSS correction or estimation step is isolated in its own submodule with a clear interface.
• Pipeline/orchestration: pdp3.sh glues modules in a linear data‐flow pipeline.
• Layered: data‐preparation → core computation → result visualization.
• Reusability: “lib” contains shared numerical routines; “utils” has common helpers; all core modules call them.
• Configurable: behavior is controlled by command-line flags and a “config_template” under table/.