Make handling of freq_interp_kind
flexible for future pyuvdata changes
#442
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.
Description
This fixes some things that break in a pending pyuvdata PR (RadioAstronomySoftwareGroup/pyuvdata#1378).
For now, this just makes sure we track
freq_interp_kind
on the BeamList object and either set it on the object or pass it to theinterp
functions depending on the version of pyuvdata (assessed by whether the attribute exists on UVBeam).Long term, once we require a version of pyuvdata that doesn't have it as an attribute, I think we can entirely remove the
uvb_params
handling intelescope.py
which will clean up that code substantially.Motivation and Context
Types of changes
Checklist:
For all pull requests:
Bug fix checklist: