James
❌❌✅❌✅🔲🔲
Kumar Amityush
✅✅❌✅✅🔲🔲
Om Biradar
❌❌✅❌🔲🔲🔲
Om S Habib
❌❌✅✅🔲🔲🔲
Reem Hamraz
❌✅✅✅✅🔲🔲
After the absolute gauntlet of the past few weeks, this week finally offered a little bit of breathing room. I'm not going to lie, I needed it. But "lighter" in the open-source world doesn't mean stopping; it just means you finally have the time to sit back and actually think before you code.
Moving from loading files to using them
Users probably won't notice most of the work from these past two weeks... and that's completely okay.
Times have have been incredibly productive and exciting. If you read my last update, you’ll know we successfully wrapped up the implementation of the Core Spectral Types. With that strong foundation in place, the real fun has begun.
Now that we have the core types for handling our spectral data, we've started diving into the algorithms that make Stingray so powerful for X-ray astronomers.
Implementing the Lomb-Scargle periodogram. For those who might not be familiar, astronomical data is notoriously messy.
I've realized something over these last few weeks. Comfort is a trap.
In Python, everything is comfortable. You have these beautiful, high-level wrappers that hide the ugly reality of how the machine actually works. But if I want to do work that matters—if I want to build things that last—I can't stay in the comfortable layers. I have to go down to where it's dark and unforgiving.
The past two weeks have been quite different from the start of the coding period.
Instead of spending most of my time implementing new functionality, I found myself exploring a part of open source development that I had very little experience with before: testing infrastructure, CI workflows and release tooling.
One thing I've learned so far is that writing code is only part of maintaining a project. Making sure that code continues to work months or years later is an equally important challenge.
The first month of Google Summer of Code has been nothing short of a whirlwind. Here's a quick breakdown of how the first two weeks went down:
Navigating the Codebase: If you've ever stared at a massive codebase and wondered where to begin, you know how my first few days felt. Getting my hands dirty made things click into place rapidly.
"I really want to be something in life. I don't want to be forgotten."
My GSoC project's main goals includes parallelizing the reading of structs in parquet files. This is very beneficial to the community as astronomical data involves data stored in structs and other nested structures.
