Upgrading to Pytheia 2.1

From 2.1.0 to 2.1.1

Version 2.1.1 restores evaluation of existing coefficients in the protected Windows package. The scientific equations, term definitions and control-system modules retain the 2.1.0 conventions. No refit is required solely for this update. Preserve your data and settings, extract the new package into a separate folder, and follow the evaluation instructions.

From 2.0.0: scientific changes introduced in 2.1.0

FO, NRX, NRY and TX in HA/Dec mode have corrected definitions. Refit models containing these terms. These corrections can change the fitted model and its residuals.

The coefficients of ECEC, ECES, HACA1, HZSA2, AUX1E, AUX2E and every HA/Dec term change sign under the unified convention. For changes that are solely sign conventions, reversing the affected coefficient signs preserves the model. Do not assume sign conversion alone addresses a corrected physical definition.

Keep coefficient files, term definitions and the control-system module on the same version. Refit with 2.1.0 where practical and validate the applied model before operational use. Preserve your original data, settings, coefficients and reports.

The coefficient file now records site latitude. New Python and C modules, usable from C++, apply a fitted model; they do not perform fitting. Custom terms require matching implementation in the control system.

The Orionis bundled example is a deterministic synthetic dataset of 120 observations. Its accepted rigorous RMS remains 2.5608 arcseconds (exact reference: 2.560784140697542); this is not measured on-sky performance or a telescope accuracy guarantee.

The Windows package retains early recipient/expiry feedback and installation-verification progress, the bundled runtime, signed integrity and both supported license formats. Full verification on a cold mechanical hard drive can still take several minutes.

See the term catalogue, TCS guidance and Windows setup guide.