Please check the build logs for more information.
See Builds for ideas on how to fix a failed build, or Metadata for how to configure docs.rs builds.
If you believe this is docs.rs' fault, open an issue.
KepLemon
Citra Space Corporation's Rust-accelerated astrodynamics package built on the shared libraries provided by space-track. Please visit the documentation page for additional details.
Installation
From PyPI (Preferred)
KepLemon can be installed directly for any operating system from a command line using pip install keplemon.
From a Local Build
For python users, the preferred installation method is through PyPI; however, the package can be installed locally by following the steps below.
git clone https://github.com/citra-space/keplemon.gitcargo install cargo-makecargo make build-<os>-<architecture>(e.g. for Linux x86cargo make build-linux-x86)pip install target/wheels/*.whl
To avoid potential conflicts with system libraries, you can alternatively build the wheel using Docker.
Then install the wheel the same way with:
pip install target/wheels/*.whl
Environment Settings
Although not required, it is recommended to explicitly apply the settings in this section before using KepLemon to avoid unexpected behaviors and inaccurate calculations.
CPU Limits
By default, KepLemon will have access to all available cores when performing parallel functions. Limit this by calling
set_thread_count before using other KepLemon functions.
# Update this to the desired core count
Time Constants and Earth-Orientation Parameters (EOP)
All astrodynamics packages have a strict dependence on measured changes to time and Earth's orientation. Since KepLemon uses the public Standardized Astrodynamics Algorithms Library (SAAL) at the core, the time and (EOP) data must conform to a specific format required by the underlying binaries. Rather than referencing data directly provided by the USNO, utility scripts are provided in KepLemon to request and export the relevant data.
Global Update
Use the command below from a terminal to update time constants and EOP data package-wide.
Local Override
EOP data can also be written to explicit paths for inspection or package overrides using the commands below.
!!! note
If you intend to use the data written to a local override, you must use the load_time_constants method at the
beginning of your scripts. This is not needed if you maintain constants using the global method.
# Update this to reflect the desired override path
Contributing
Anyone is welcome to contribute to KepLemon. Users are encouraged to start by opening issues or forking the repository. Changes directly to the baseline may be approved by contacting the owner at brandon@citra.space.