-
Notifications
You must be signed in to change notification settings - Fork 29
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
Adding new Telescope attributes for feeds and mounts #1521
base: main
Are you sure you want to change the base?
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #1521 +/- ##
========================================
Coverage 99.93% 99.93%
========================================
Files 63 63
Lines 21746 22044 +298
========================================
+ Hits 21731 22029 +298
Misses 15 15 ☔ 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.
⚠️ Performance Alert ⚠️
Possible performance regression was detected for benchmark.
Benchmark result of this commit is worse than the previous benchmark result exceeding threshold 2
.
Benchmark suite | Current: d7816f1 | Previous: bca6cf0 | Ratio |
---|---|---|---|
tests/utils/test_bls.py::test_bls_to_ant[min=0-len=1] |
168682.51670325958 iter/sec (stddev: 0.0002299602645136317 ) |
1296803.9086480543 iter/sec (stddev: 0.000005510650430395054 ) |
7.69 |
This comment was automatically generated by workflow using github-action-benchmark.
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.
This is looking interesting, I have some questions.
dedc267
to
ab29403
Compare
Noting here that we've had our first successful external test using CASA's |
ca78d58
to
a3d367b
Compare
Alright, I'm moving this out of draft since major work here is completed. Still need to do some documentation work, which I could use some guidance on where to put that, but otherwise I'm at a point where I'd like to make sure that folks are on board with what is effectively the proposed deprecation of |
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.
This is looking really good to me, I'm comfortable with the approach you took for the x_orientation deprecation. Just a few other comments.
I will work on PRs for the external tests that are failing, but I may not get them done until week after next when I'm back from vacation. |
51a19d8
to
0d4dad1
Compare
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.
LOVE the new convention page! @steven-murray can you take a look and see if anything is missing for you?
I also really like the condensed way you treated the antenna_mount in the docstring!
Just had a couple comments:
@kartographer that convention doc page is fantastic, thanks! It'd be great to add a polarization convention section there as well (i.e. |
…R, UVH5, UVFITS, MIRIAD, and MS formats
…and fixing feed string case
…blank strings) to prevent CASA errors.
fix minor typos
47dabda
to
cc592b4
Compare
I started poking at pyuvsim to figure out what needed to be done there and realized we need to harmonize UVBeam with these changes. UVBeam doesn't have a telescope object on it, in large part because it doesn't need anything to do with antenna layout information. But it does have |
Adds feed orientation and mount information to Telescope class, deprecates
x_orientation
.Description
A few new attributes have been added to the Telescope class:
Nfeeds
, which describes the number of polarizations captured by each antenna;feed_array
, which records the polarizations for each antenna (one of 'x', 'y', 'l', 'r');feed_angle
, which records the feed position angle (where 0 is aligned to vertical polarization); andmount_type
which records the optics of the antenna. As part of putting together this PR, I've also taken a first (significant) pass at a "conventions" page for the docs, which describes some of the finer details of these new attributes (along with some other conventions pieces).Note: This is a late-stage WIP, but I'm putting in a PR now so that interested parties can review while we conduct some additional testing. As per usual, me updating the CHANGELOG will denote when I think everything is wrapped up.
Motivation and Context
SMA is in the process of adding polarimetric support in CASA, and adding these new attributes are one of the first big steps/hurdles for that.
Closes #1470
Closes #854
Closes #1235
Closes #1425
Open items:
mount_type
needs to live.Types of changes
Checklist:
Breaking change checklist: