From download to your first report.

1. Download and verify

   Download the ZIP and checksum. Compare the ZIP’s SHA-256 with the value shown on the download page.

2. Extract the entire package

   Use Windows “Extract All”. Open the extracted Pytheia200_Evaluation folder. It contains Pytheia200.exe, settings.ini, app, runtime, integrity, license, and other files. Keep them together. Do not run from inside the ZIP.

3. Install your separate activation

   Request a licence from Orionis. Copy the supplied license.json and license.sig into the package’s license folder. Keep the public key already in that folder.

   Copy the personalized LICENSE.txt into the package root, replacing the generic agreement. Read it: the name and period come from your signed licence. Your 30 UTC calendar days begin on issuance.

4. Run the bundled example

   Open PowerShell in the folder containing Pytheia200.exe and run:

   .\Pytheia200.exe

   The default settings.ini selects example/example.dat. The reference fit converges to total RMS 2.5608 arcseconds.

5. Open the outputs

   Open example/output/results_example.html in a browser. The fitted coefficients are in example/output/coefficients_example.txt. Check the report’s licensed-recipient attribution.

6. Use your own observations

   Edit settings.ini or keep another settings file for your telescope. Relative data and output paths are resolved from that settings file’s folder.

   .\Pytheia200.exe "C:\My Telescope\mytelescope.ini"

   Select azel or hadec, your terms, and the input data. HA/Dec requires site latitude. Consult the bundled documentation before creating additional terms or using results operationally.

If the program stops

Some calculations emit the documented pandas chained-assignment warning. The release’s scientific tests and reference fit pass with it present.

For help, email support@orionisgroup.com with the exact console output and your settings, omitting confidential observation data where appropriate.