Hello, World!

~ No Day But Today ~

Week 9-10 at JuliaAstro
List of Milestones achieved Interpolator tweak #6 Multi File Support #21 ccd2rbg function #15 data matrix and WCSTransform tuple type parser #7 Support for RGB #22 Basic UI panel for AstroImages #3 Interpolator tweak #6 This patch to Reproject.jl was due to some realizations I had upon Mosè Giordano stressing over the fact that I should use isapprox rather than check_diff (my custom test method) in ccd2rgb PR. I realized that there was something at fault and after investigation, I found that there was a custom method of map_coordinate in original reproject of python version which I didn’t understand at that time and left it (as on large scale both gave same results). It created some differences on the edges of images reprojected. So after many hours of figuring out the trick they used, the check_diff was replaced by isapprox along with a tweak to the interpolator. Multi File Support #21 This PR was completed a long time ago but it’s build was failing on appvyeor viz. Windows build. I too along with my mentor was confused at first because Travis (Linux and Mac) build were all green and the logs in appvyeor were also non-sensical.......
Second Evaluation: 2 months into GSoC
I thought the first month will be the toughest as there lies the trickiest part of the project. But guess what, the second month proved otherwise. But that’s the reality of GSoC, right? Until you have faced the challenges at least once, you won’t grow better to face it the next time. I am glad of the learning experience GSoC has given me. I used to think coming into OSS has improved my skill a lot but now I can see how much still I have to perfect myself. The following is the experience of the 2nd month of my GSoC project. What things I achieved before my second evaluation? 1. Plotting Interface for AstroImage This involved writing a custom recipe for plotting AstroImages. Now using plot(img, header), users can display the world coordinates of AstroImages in the plot itself. 2. Image Interface for AstroImage Adding image interface required AstroImage package to fortify with many small features. But the toughest part was to maintain the performance and write code in a type stable manner. I got to know about mutiple dispatch from my mentor and how Julia is utilizing it to make everything faster and efficient. Additions for Image interface: * Multi Image support #19 * Multi WCS support #20 * Multi File support #21......
Week 5-6 at JuliaAstro
List of Milestones achieved Integrated WCS info. with AstroImages Plots #16 Registered the very first version of Reproject.jl #1643 Added Multi Image support to AstroImages #19 Added Multi WCS support to AstroImages #20 Plots and WCS info. Integration This involved writing a custom recipe for plotting AstroImages. Now using plot(img, header), users can display the world coordinates of AstroImages in the plot itself. 1st version of Reproject With all the required functionalities introduced in Reproject.jl which are going to be used in AstroImages.jl, we released the very first version of Reproject.jl. We discovered that there is still some scope of optimization in Reproject.jl as its performance is not at par with the python version. It involves solving some type of instabilities in the dependencies it is using. MultiImage and MultiWCS support in AstroImage Previously AstroImage can store just a single 2D matrix of Image data. I introduced a functionality which allows AstroImage to carry more than one matrix of Image data. Also, as most of the applications will be based on WCSTransform, we thought keeping it there too is also a great idea. Week 7-8 tasks Enable support for RGB images. Setup GUI for AstroImage interaction. Also, this week I joined JuliaAstro organization on Github.......
First Evaluation: 1 months into GSoC
This month went by faster than I expected. Why? It’s because I had too much to do and I was excited enough to write the code and see how things will turn out. Will my ideas to create things in a certain way reflect in my code or not? What would I do if I spent too much time working on the wrong approach? Will I miss the deadline and how would I cope if I did? How my mentors evaluate me until now? Do I reach the full potential of a GSoC student? These things did trouble me a bit but luck was on my side and my mentors were super helpful to guide me through this. What things I achieved before my first evaluation? 1. Reproject.jl This was the trickiest part of my whole project, an important one too. This is a Julia package with 400+ lines of code which I wrote from scratch with my mentor reviewing my work from time to time. List of PRs: #1, #2, #3 Why this package? On a high level, we are trying to achieve a way to represent Astronomical Images in Julia at AstroImages.jl (another new repository I’m working). Astronomical Images are a bit different from our everyday images in JPEG or PNG format, it can be very big in size, carries useful information about the image and comes in its own format i.......
2 weeks into GSoC
I had a feeling in the community bonding period that something will mess up at the start of the coding period as I had the toughest part lined at the start. The same did happen… At the start, I had two weeks for porting reproject from Astropy. In short what it does is, it align two different astronomical images into a single frame of reference. While capturing an astronomical image, different conditions(like the position of the sky) affects the image captured. Thus, two images of the same region of interest will not be exactly similar when taken under different conditions. It may require to rotate, translate or interpolate them to get the result. So where the difficulty arises for me? Astropy is a very mature library but support for Astronomy in Julia is still growing. This means that I can’t port line by line, I need to be creative. Plus the utility functions which the python version of reproject calls was not present in Julia. So at a basic level, it meant I had to port every other function in Julia or get a workaround using the existing things. So a project part which seemed within bounds at the beginning started growing exponentially and I haven’t planned this.......