CLI parameters
The get-cp service is controlled with python get_cp_app.py COMMAND. Without a command it starts the five-minute monitor.
| Command | Purpose | Options and defaults |
|---|---|---|
daemon | Checks the MPC observation page continuously and rebuilds after a change. | --interval, default 300 seconds; --force-first forces the first build. |
once | Performs one MPC check and exits. | --force rebuilds even when the marker is unchanged. |
mirror | Creates a manual online comparison copy. The monitor never uses this command. | --output, --base-url, and optional --modern-output. |
build | Builds from a stable snapshot of the locally calculated fragments. | --source, --output, --date, --settle-seconds, --timeout. |
modernize | Creates the repaired local presentation without changing the exact mirror. | --source and --output. |
check | Checks raw page equality and local links. | --site, --base-url. |
shadow-check | Compares current reference ephemerides with the independent local calculator without changing the website. | --objects, --kernel, --report-directory. |
pilot-check | Runs the gated local ephemeris pilot against an isolated reference calculation. | --objects, --object-limit (default 5), --kernel, --report-directory, --preflight. |
orbit-engine-check | Compares the locally built orbit engine with a retained reference executable. | --objects, --object-limit (default 0, meaning all), executable paths, and --report-directory. |
Global options
-h and --help display the complete help. --config selects a JSON configuration file. Commands do not change Windows Task Scheduler. When public output is enabled in the selected configuration, successful daemon and once builds are staged for publication through the configured Fling folder.
Calculation and publication
After an MPC change, the monitor fits the orbit and calculates the daily ephemeris with the locally built source core. Hourly and minute ephemerides use the optimized local calculation path. A one-arcsecond acceptance gate protects the result; rejected candidates remain on the complete local source-core path.
The MPC page is checked every five minutes. The site is rebuilt after relevant changes and by the configured scheduled refresh. Successful builds are generated locally and copied atomically to the controlled publication folder.