SVM-Based Glitch Detection and Removal#97
Merged
Merged
Conversation
Contributor
|
Add what you did to test this code |
jjd330
requested changes
Aug 5, 2025
…tis names to account for SVM function
left "for bti in glitch_btis" as bti...only swapped glitch_btis
katefoyle
commented
Aug 6, 2025
katefoyle
commented
Aug 6, 2025
Contributor
|
Once you change evdata to evdata0, can you run through one of the test cases one more time? Also can you make this pull request not a draft? |
katefoyle
commented
Aug 8, 2025
katefoyle
commented
Aug 8, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This pull request transforms the glitch detection pipeline into a machine learning approach (with an SVM classifier) capable of finding instrumental glitches at lower S/N thresholds and removing only those with glitch likelihoods exceeding a specified threshold (set to .45).
Key Changes
Added SVM glitch detection:
Interval handling:
Why?
Testing: