ANNOUNCEMENT

Hi @room,

I have prepared a FORK of poliastro, codename hapsira, currently located here on Github.

It's mildly re-branded & cleaned, keeping full attribution as per poliastro's MIT license. The basics, i.e. online docs, CI, etc., are working. The logo has yet to receive an update. hapsira's first release will be version 0.18.0, likely before the end of the year, both on PyPI and Conda Forge, allowing for a clean update from poliastro version 0.17.0. It is based on poliastro main as of the date of its archival, October 14 2023, commit 1b01768c. No further critical or functional changes will be made in this release. I updated the changelog to reflect all merges made after 0.17.0, but there could be mistakes and missing pieces - please check if you had something merged during this time frame. In a similar manner, feel free to check for incomplete re-branding or insufficient attribution and report issues.

If you have unresolved technical issues in poliastro that you want to see fixed in the near future, please re-file them against hapsira and link to the original poliastro issue and its discussion. The same goes for unresolved PRs. Please rebase to hapsira main and re-submit them against hapsira, possibly also linking to the original PR and its discussion in poliastro's repository.

I am happy about any kind of PR, though I'd prefer to coordinate via a Github issue before you begin to invest time into a significant change. My personal objectives are:

• array-oriented, parallelized core package running both on CPUs and GPUs optimized for speed & scalability
• isolation of unit handling so the physical unit layer, currently based on astropy, can be swapped entirely eventually (if desired)
• unit-less middle layer for fast operations, running on implicit default units, symmetrical to the current high-level API

For context, see poliastro #1008, poliastro #1018 and "array types for scaling for poliastro" (2021).

I intend to keep the fork as compatible and close to the original as possible, though compatibility breakages are very likely to occur in future releases. I'll use semantic versioning to indicate breaking changes, i.e. a jump from 0.18.x to 0.19.0 marks a break in compatibility.

I'll continue to monitor this chat room and poliastro's mailing list, but further discussions and announcements will occur in hapsira's chat at #hapsira:matrix.org and on hapsira's mailing list at groups.io.

Thanks,
Sebastian

In reply to @jan-peter:matrix.org
I am sorry but I am unfarmiliar with these things.
Can some explain to me like i'm 5 what this is for?

Let me try.

https://naif.jpl.nasa.gov/naif/index.html

It is support concurrent engineers in designing space missions.
And helps scientists plan their observations as they can simulate where bodies (Earth, satellites, ...) are going to be in space.