## Adding the Altitude, Latitude, and Eclipse event detectors

It was an engaging first half of GSoC, and it was during this duration, I understood some critical details of executing the event detectors. We started to look into the eclipse detector since we thought it might be challenging to get it right.

In the weekly community calls, we brainstormed over an appropriate method that would fit in poliastro. Thanks to SciPy’s events support through solve_ivp, we just had to come up with a time-varying and continuous “shadow” function without having to solve analytical equations manually. However, the critical challenge for us was to come up with such an equation! After a few trials of geometric manipulations and Jorge and Juanlu’s assistance, we came across an equation involving classical orbital elements that could serve our purpose. We were still questioning the performance and complexity of the method since …

This month the poliastro repository has crossed ⭐️ 500 GitHub stars ⭐️, thanks everyone for believing in the project!

Juan Luis released version 0.15.2 with a fix for newer astroquery versions, as well as compatibility with Plotly 5.0, which allows users to install all the required JupyterLab extensions without Node.js. This will make the installation process much easier!

Yash and Jorge had a very productive month: after a lot of discussion in our weekly community calls and several rounds of code reviews, we finally have eclipse event detection merged! Yash has passed the first Google Summer of Code evaluation with flying colors and will publish an entry in our blog soon. The work Jorge did on our validation infrastructure as part of the NumFOCUS Small Development Grant has proven to be extremely useful. In addition, Yash has also …

# The initial days…

Hi there! I am Yash, and I will be spending this summer with poliastro as part of GSoC 2021 to add some event detection capabilities. It was around December when I first learned about poliastro, and it gradually got me fascinated by orbital mechanics.

While preparing to make my first pull request, poliastro's comprehensive documentation and tutorials came to the rescue! It was much needed for a beginner like me who had just stepped into the field of Astrodynamics. This was a period when I thoroughly enjoyed interacting with the community and learning orbital mechanics while simultaneously learning the best practices in software development.

# Building up ideas and our aspirations for this summer!

After deciding to submit a proposal for the event detection project, I started brainstorming and looking for several references keeping in mind their relevance …

The first (and hopefully) only beta of poliastro 0.15 is out! 🎉 It took us a bit longer to get this release out, but we are happy that poliastro 0.15 is now around the corner. We will soon write detailed release notes and a proper announcement for it, and in the meanwhile you can read the preliminary poliastro 0.15 changelog.

Juan Luis revamped our website a bit, by adjusting our domain names and improving the navigation bar (twice). Besides, he has finished the reorganization of our docs following the Diátaxis Framework by Daniele Procida, prepared for the upcoming Sphinx 4.0 release, and updated our installation and contribution instructions.

Jorge has finished validating our planetary transformations against GMAT and Orekit, which required reaching out to the Orekit developers and adjusting one outdated constant in poliastro. This wraps up …

poliastro finally landed support for Python 3.9, thanks to the fine folks of numba! Their release candidate already works with the newest Python release, and we've been told that the stable release is around the corner. This means that the next stable release of poliastro will also support it 🚀

On the validation side, Jorge has been working on more enhancements, and we have finally confirmed that our 3D impulsive maneuvers give the same result as GMAT and Orekit! You can read the full details in this blog post.

And finally, we have made some small improvements on the development side, by fixing some continuous integration small failures, reducing the number of warnings in our tests, and other small fixes. Thanks Yash, Dhruv, zkl2, and Souhit!

## Impulsive 3D maneuvers have been validated!

As part of the NumFOCUS small development grants, the poliastro/validation repository has increased its activity in order to reach its main goal: validate poliastro's most complex features against similar software.

One of those features are impulsive maneuvers (Hohmann and Bi-elliptic) when applied to non-equatorial orbits. The absence of numerical results in literature and similar sources, made impossible to test associated pieces of code to impulsive maneuvers for orbits with inclination and spacecraft not placed in periapsis. However, this situation has changed, as they are now validated against Orekit and GMAT.

You can see corresponding pull-request for Hohmann validation and Bi-elliptic validation. Not only that, a continuous integration tool has been setup. This ensures that if any bug is introduced within main poliastro source code, we can detect it and fix it without any problem.

One interesting thing is that …

We got awarded a Small Development Grant by NumFOCUS to validate poliastro against commercial and non-commercial similar applications! 🎉 Jorge started by setting GitHub Actions to trigger the validations automatically, validating our conversion between cartesian and Keplerian elements against Orekit, and is now fighting some discrepancies with Hohmann transfers.

On the development front, while we wait for Numba to release Python 3.9-compatible wheels for our next release, we refactored our Cowell propagator to make the code simpler and more numba-friendly, we tried to merge Eleftheria's implementation of the Escobal method for satellite visibility (and sadly got blocked in the process), and kept working on our analysis of Walker constellations for the OpenSatCom activity. We also engaged with the authors of the awesome numbakit-ode to rewrite our Cowell method using numba, but found some issues along the way and we decided …

## This is an end of an era

Contributing to Poliastro has been an incredible experience for me. Since it was the first time, I've participated in GSOC. And the first time I've ever approached to package dedicated to problems arising in Astrodynamics and Orbital Mechanics. Being part of Poliastro was an exciting challenge that I had to surmount and also an unbelievable opportunity to learn about Space, Math and Physics.

With the thorough knowledge learned, and the feedback from JuanLu and Jorge, I was able to overcome every challenge in my Poliastro's journey. As I had said when I had the opportunity, I am grateful to both of my mentors who accepted me to be part of this exceptional community. :)

# Git-log

What we have achieved in the past three months:

Hey, folks! The last weeks were really exciting getting done an algorithm for ground-track orbit. After long days trying to find the perfect approach for Poliastro, we decided to give it a go bringing to life this paper

# But everything it's not what it seems

Well, we thought it will be quite straightforward but much too learn still I have , right Master Yoda?

So I am not gonna lie to you folks, it wasn't that easy, but as Rocky says, "Every champion was once a contender who refused to give up". So now you are gonna know how we solve it. Game on! First things first, we needed to apply numerical analysis in order to obtain the roots of the equation, because given the complexity of the function, there was no other way around.

So we had to come up …

## On the move!

Hey, folks! Here's Meuge, your usual host from the last few months.

In the last few weeks, we got a little bit of everything, analyzing, coding, and searching for feasible solutions to reach the best result. Therefore, we came up with a new feature in Poliastro's Earth module. The API may change in the future, so be aware by the time you read this. Hence, I bet you might be wondering, what's all the fuzz?

Well, now you can experiment with the new API to compute the visibility of sensors that are on board of the satellites. The FOV, field of view, the question is about meeting mission goals within the limit of a satellite sensor. Given some parameters about the viewing satellite, the fundamental problem related to calculating the field of view is estimating how much of Earth we …