Fixing an issue with UVData objects being incorrectly added #1105
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.
Fixes a bug with
UVData.__add__
when objects are sorted differently.Description
UVData.__add__
that checks for the ordering of records along time-baseline, polarization, and frequency when twoUVData
objects have "overlap" in these domains. If there is overlap, but the ordering of the data is different, the new code will reorder the (meta-)data of one of the objects so that data are concatenated as expected.Motivation and Context
Fixes a nasty bug were data could be concatenated incorrectly when the sorting order is different (e.g., #1102).
Closes #1102.
Types of changes
Checklist:
Bug fix checklist: