-
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
fix: blt slicing and other things for new uvdata 3.0 functionality #931
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #931 +/- ##
==========================================
- Coverage 97.25% 97.18% -0.08%
==========================================
Files 30 30
Lines 10766 10733 -33
==========================================
- Hits 10471 10431 -40
- Misses 295 302 +7
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.
Basically looks good to me. Just a couple of questions.
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.
Looks ok to me!
@jsdillon I'm inclined to merge even though not all lines are covered -- the remaining lines are very difficult to cover right now (most of them will be covered once pyuvdata 3 is out by default, and then we can remove some other code branches) |
Fine by me.
…On Wed, May 22, 2024 at 12:45 PM Steven Murray ***@***.***> wrote:
@jsdillon <https://github.com/jsdillon> I'm inclined to merge even though
not all lines are covered -- the remaining lines are very difficult to
cover right now (most of them will be covered once pyuvdata 3 is out by
default, and then we can remove some other code branches)
—
Reply to this email directly, view it on GitHub
<#931 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABIJK424Q54RAJCQFM45GHLZDTYVTAVCNFSM6AAAAABCTNBYC6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMRVGYZDGMRQGU>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Fixes #928
This fixes issues related to the
antpair2ind
update in pyuvdata v3.0. The biggest issue was that the output ofantpair2ind
is now no longer guaranteed to be an array of indices, but instead could be eitherNone
or aslice
object. Furthermore, the results of calls toantpair2ind
are now cached on the UVData object, and this cache needs to be refreshed on any update to the blt axis of the data. This is done inUVData.read()
but this method is over-written inHERAData
so it needed to be added manually.Bryna's comment:
It also fixes things for some other changes in pyuvdata v3.0. There's an update to the telescope metadata handling, which has deprecation but I went ahead and fixed some of the places this comes up. Also,
write_vis
andwrite_cal
broke when we actually removed support for the current array shapes. In the process of fixing these, I decided that it would be easier and better to just change them to use the.new
methods on those objects. That reduces the amount of code that needs to be maintained in this repo. Note that this makes #851 unnecessary.