GSoC winning Proposal
Feb 24, 2020
2 minutes read
After forming many strategies and improvising them along the way, I decided that I will submit 2 proposals for GSoC 2019. Originally there is a limit of 3 proposals per student but as I started preparing from Nov 2018, I had enough time to curate 2 strong proposals. The proposal which got me GSoC’19 is: Visualization of astronomical images in Julia (Proposal) And my other proposal got me JSoC’19 (which I couldn’t pursue due to GSoC rules). I will add that too when I’m sure that it is of no use to me anymore and I can’t resubmit it XD; Some Tips for writing a good proposal Keep it short and under 10-12 pages long. No one has enough time to read 20 pages. Use hyperlinks if you want to explain something more but don’t have space. Try to follow the format which I have used. I have seen, compared and analyzed many proposals and this format covers most of the necessary things while keeping length into account. Make sure to include some of your previous work which can help the mentors analyze your quality of work. Approach your mentors early to get feedback on your proposal and make final changes 3-4 days before the deadline.......
(Prequel)Second PR to JuliaAstro
Sep 24, 2019
3 minutes read
PR info. 9th PR on AstroImages.jl(I only submitted 2 PR before getting selected for JuliaAstro although I had other PRs in other Julia related repos). Task: A FITS file can contain both images and/or tables related to an Astronomical image. So my task was to write something to handle cases when there is no image component present in the file. It’s like adding corner cases. Things used: Nothing specific. But many iterations done due to not knowing standard things. (I was still new to Julia) Back-story My first PR was in and I discovered this one accidentally. I got an error while using a FITS file without an image component. Although we can specify our own index but by default AstroImages treated the first index of FITS as image component. But according to me, the system should be intelligent to handle such know situations (also was finding things to make PRs for). It later turned out to be an important observation. PR evaluation and learnings This PR started with pointing mistakes I did in the PR. I wasn’t familiar with the concept of Multiple Dispatch then and I mixed development practices of Python too. I was opening the same file several times (in Astronomy it can go to GBs too).......
(Prequel)First PR to JuliaAstro: Making Impression
Sep 22, 2019
2 minutes read
PR info. 7th PR on AstroImages.jl. My first PR to JuliaAstro org. Task: Add a feature to change brightness/contrast of AstroImages in real-time in Jupyter notebook itself. Things used: Interact.jl for interactive Jupyter visualization. Back-story There was a criterion of OpenAstronomy that a student should have at least one PR to the project to be eligible for getting selected into the org. Our mentor Mose told us about this and as AstroImages.jl was a new package, there weren’t enough issues to solve. So he came up with this idea that can be implemented to the package. Lucky me, I have done the same thing before while extending docs of Images.jl. I think this gave me an edge over others. Those days I was also contributing to JuliaText, so managing time for both org. was tuff. But as I knew how to do this, it was a quick PR. PR evaluation and learnings Mose was expecting the same thing which I had made. I also proposed some ideas like we can store this operation and change the data of FITS if the user wants according to this feature. But Mose highlighted that the data is holy, we shouldn’t just modify it just carelessly.......