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

DM-38385: Write fastStarTracker analysis code #37

Merged
merged 16 commits into from Mar 24, 2023
Merged

Conversation

mfisherlevine
Copy link
Contributor

No description provided.

Copy link

@cmsaunders cmsaunders left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks good to me. I just have some minor comments.


def checkResultConsistency(results, maxAllowableShift=5, silent=False):
"""Check if a set of results are self-consistent.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How likely is it that you will have issues with sources at the edge of detectors? Having the brightest star at an edge seems like it will have a lot of unwanted consequences if it scatters or drifts off the detector.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Quite likely, and I totally agree that will cause problems. That was kind of the thrust of the consistency checking helper function. My thinking is that if it slips off the edge the you either get a massive jump in centroid, or a different number of source counts, or a huge jump in brightness, or something else. Hopefully that will help people find things when it's happening, but I don't think there's much that can be done about it, at this stage at least.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If it looks necessary, I think that coming back to all this code and implementing a better way of doing source association between the images would be a good plan, but 1) this was all written on a plane, and 2) all the data so far has no problems in source association, so I just didn't need to do it, and so didn't given the great urgency with all this stuff 🙂

@mfisherlevine mfisherlevine merged commit efd82db into main Mar 24, 2023
1 check passed
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

Successfully merging this pull request may close these issues.

None yet

2 participants