-
Notifications
You must be signed in to change notification settings - Fork 8
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 FRF noise covariance calculation library #977
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #977 +/- ##
==========================================
+ Coverage 97.16% 97.20% +0.04%
==========================================
Files 31 31
Lines 11064 11140 +76
==========================================
+ Hits 10750 10829 +79
+ Misses 314 311 -3
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
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.
Thanks @mwilensky768. This all looks basically fine, just a couple of minor suggestions
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.
Assuming tests pass... Thanks @mwilensky768 !
This branch adds some noise propagation functions for the fringe rate filter + coherent averaging steps.
I've added the basic functions that are demonstrated in the single baseline power spectrum notebook, though they've been modified here to be slightly more general since the notebook versions used notebook-specific info. This PR and the corresponding one on that repo should probably coordinate.
I still need to add unit tests and think I should add a wrapper that goes from ee + nn autos/crosses all the way to a pI time-time cov. per freq so that there is a clearly implemented "pipeline" somewhere, though maybe that should just live in another repo as part of actual pipeline code.