This post regards the coding the I have done during the third and fourth weeks of my awesome GSoC project.
First things first. My mentor Erik Tollerud (aka @eteq) gave me a really nice opportunity to listen and also contribute with some of the super devs from Space Telescope Science Institute (STScI). More precisely, I participated in a code sprint organized by the JWST Data Analysis Development Forum.
Basically, the intention of this sprint was to build a framework for PSF fitting photometry, which is precisely the subject of my GSoC project. So, thanks Erik =D.
Also, during those meetings, I could see a future development for my GSoC project, which is to consider psf photometry in crowded fields from a set of dithered images instead of just one image of a given field. If time allows, this would be, maybe, my first "extra" task.
Now, talking about coding, I've submitted quite a few PRs to `photutils`. Some of them were just minor organizational things like creating a PSF subpackage or changing the interface of the findstars module.
Yes, we decided to "change" the interface from a functional programming paradigm to nicier, more maintanable object-oriented paradigm.
As a first step into that, I changed the GROUP functionality, which is now much faster and cleaner thanks to Moritz's reviews xD
I also submitted a PR to my own branch as a proposal to an interface of class which will encapsulate the whole PSF photometry process and it will still provide to users the flexibility to either change or include their own functionalities into it. For instance, suppose that an user has a better algorithm to detect stars, then one would just write it as a StarFinder subclass and then pass it to the PSFPhotometry object. Simple, but not simpler :)
Also, thanks to Brigitta, I managed to rebase a branch which adds uncertainty computation to the current sequential psf photometry in photutils.
For now, I'm concentrating my efforts in the GROUP PR and also making NSTAR compatible with our new interface.
Now, to work! :)