-
Notifications
You must be signed in to change notification settings - Fork 10
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
Read pyuvdata-formatted beamfits beam models #301
base: master
Are you sure you want to change the base?
Conversation
An example beam fits file is available here: https://github.com/rlbyrne/rlb_LWA/blob/1db84dcbec1071b2039886c48130047bc1009b1d/LWAbeam_2015.fits |
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.
Here's an initial run-through for changes. Once implemented, I'll do some checks that it doesn't break existing beams
5c307c0
to
ca206f3
Compare
@nicholebarry Thank you for the memory speedup! I'm afraid I don't understand the images you posted. How are you finding that the images are wrong? I would expect that the pyuvdata beam wouldn't be exactly equal to the MWA beam contained within FHD. |
Fixed the problem with the mem reduction. There is now some push towards combining some of the beamfits code as pyuvdata_beam_import is quite small. @rlbyrne can you check that the change does not affect LWA data? I need to rerun, because the beam is ever so slightly off, but I didn't include the recent commits. So I will set that up now and have it finished soon. |
@nicholebarry Thank you. I will run an LWA test. Please let me know what you find with your test. |
I just tested the latest version of the branch on LWA data and the results look good. @nicholebarry are there any more tests we need to run? |
This PR allows the user to specify the beam model by supplying the path to a *.beamfits file.