Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Multi-Aperture Photometry #3

Open
kjkoeller opened this issue Jul 8, 2023 · 4 comments
Open

Multi-Aperture Photometry #3

kjkoeller opened this issue Jul 8, 2023 · 4 comments

Comments

@kjkoeller
Copy link

Hello,

I recently graduated with a masters degree and my thesis was on W UMa binary stars and I created a package for analyzing these systems. I am working on creating a pipeline for Ball State University's observatory but for a really good pipeline I need a working multi-aperture photometry program. I found your package while searching GitHub and I was wondering if you all had any intentions of making a working multi-aperture photometry program or the knowledge of making that.

My current, non-working, version is here (https://github.com/kjkoeller/EclipsingBinaries/blob/main/EclipsingBinaries/multi_aperture_photometry.py)

@viveikjha
Copy link
Owner

Hi,

Sorry for the late reply. Yes, I indeed plan to make it a flexible and workable aperture photometry package. In fact, one of the students successfully generated light curves for a few hundred sources using this code last month only. The only problem I see is that the code is not robust at the moment, and there are a few problems which need to be addressed manually. It'd be great if we could streamline it. 'final_notebook.py' is the latest version of the code, which performs all the steps in a single script. Please let me know if you face any problems using it.

@kjkoeller
Copy link
Author

Have you thought about incorporating comparison stars to find the magnitude rather than just using the relative flux?

@viveikjha
Copy link
Owner

Yes, I have tried that too, but the problem is that we won't have comparison stars in every frame. Another way would be to search for my sources on simbad and get the magnitudes for matching sources from there. We can then compare and see if there is a constant offset. It is working fine for most of the frames I have right now.

@kjkoeller
Copy link
Author

When you did attempt to use comparison stats, did you get the magnitude calculation to be accurate?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants