-
Notifications
You must be signed in to change notification settings - Fork 42
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
Add wisp finder monitor #1666
Add wisp finder monitor #1666
Conversation
Hello @bhilbert4, Thank you for updating ! Cheers ! There are no PEP8 issues in this Pull Request. 🍻 Comment last updated at 2025-01-21 20:41:21 UTC |
Here's a good test case for both test and ops servers: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@bhilbert4 this is awesome! I am approving, with a few tasks:
- Add the django model
- Updates to the default config file.
Django model and migration file are both present in the PR now. |
I've updated the config files on all three servers to include the new entry. |
Add an automated wisp finder monitor to JWQL. This tool finds new data, creates a scaled image of it, and uses a neural network to predict whether there is a wisp in the image. If a wisp is found, it sets the wisp flag in the Anomalies instance for the appropriate RootFileInfo instance.
This model is trained and currently works only for the wisps on NIRCam's B4 detector.