Skip to main content

astropy@GSoC Blog Post #2, Week 1&2

Hi,

How are you?

So, it's been two weeks of astropy@GSoC work already. Of course I have been damn busy! With the last commit made to the draft PR https://github.com/astropy/astropy/pull/11835, a few hours back, I have successfully written a basic CDS writer. And voilà it works, albeit without the ReadMe at present! 😁

Note that I am quite unlikely to go into technical details here in these posts. There are two reasons for this. Hhm..., Na I guess there's just one single reason. It would be too repetitive a task to write them. I already write aplenty about those in the GitHub comments and other communications. And of course, the whole codes I am writing during the project are available publicly on GitHub, for the overly curious kind. Moreover, the final report is gonna have more than ample discussion too, because I like to explain myself a lot. 😐 What then is the need to write all that here again? So consider these posts my plain uncouth thoughts, which in any case, I suppose, aligns more with the spirit OpenAstronomy asks these for.

On a second important point, honestly, these Astropy people are really intelligent. It would appear, even more as the project progresses, that they knowingly marked a normal project as Easy to lure some innocent students! 😂

Anyway, Bye.

See ya the next time! 🙋‍♂️



Comments

  1. The best kind of projects get difficult with time! :)

    ReplyDelete

Post a Comment

Popular posts from this blog

An Algorithm to find who to invite to your Event!

The criterion for including people for an all-paid Dinner Party, for instance, should at the very minimum be the people whom I can call and I am sure who will pick up the phone. This then by definition includes almost all, nah, all of my male friends and excludes most of the, if not all, ex-girls I have dated before. Then there is the proximity of location constraint. Plus, inclusion of anyone who invited me to their past celebrations and I know who maybe able to join for this one. Or somebody with whom I was close either in proximity of location or friendship or both or with whom I spent a lot of time together. Now, on top of these, in order to reduce the list to the most closest of the close current friends, I can impose the following additional requirements: 1) Should have met them atleast once this year or in the past 6 months, whichever is longest. 2) We should have had atleast one 1-1 meeting, preferably outing for >1 hour, either for lunch, coffee or dinner or something else....

Three demises and room for no more

In the past few months, three personalities I had grown looking up to over the year, have started their journey towards the heavenly abode, the latest departure happening just the last week. All the three occasions of the news had felt out of the blue. It is not that I had been exceedingly close to any of them, nonetheless, brief touches of their presence in my life had made in such sublime manner that it would hardly be possible otherwise now. It is especially the distant figures such as these that we are prone to assume a constant in our lives. We meet and come across a plethora of people in our life times, yet it is often the transient moments that leave a lasting impression, amplified more so when the impermanence of it all suddenly decides to make itself known. I am grateful that, in varying degree of acquaintance, I had the opportunity to know Mr. Emmanuel Robin, Dr. N Rathnasree and Prof. T Padmanabhan. These succinct lines here are an amateur effort to pay some tribute to them....

astropy@GSoC Blog Post #3, Week 3

So, it's the start of the 3rd week now. I will be virtually meeting Aarya and Moritz again Tom. For the past few weeks now, I have been pushing commits to a Draft PR  https://github.com/astropy/astropy/pull/11835  on GitHub. I wanted to have something working quite early in the project, in order to be able to pinpoint accurately when something doesn't work. This is why I started with directly adding the cdspyreadme code within Astropy. Afterwards, I am also writing the code from scratch. As more of the required features from cdspyreadme get integrated into cds.py , those files and codes added earlier will be removed. About the reading/writing to Machine Readable Table format, in fact I wrote about it briefly in my GSoC Proposal that I could attempt it as an extension. I don't have an opinion on whether or not it should have it's own format classes etc. However, since the title of my GSoC project is to Add a CDS format writer to Astropy , I would prefer to work on the ...