Closed adeliegorce closed 1 year ago
@adeliegorce I merged the fix for the hera_cal stuff, but this branch looks like it's still failing the pyuvdata stuff?
It is failing because there is a requirement pyuvdata<=2.2.8
. At this time pyuvdata
wanted complex data arrays for beams but newer versions require float data arrays. Runs are passing locally without this PR and with the updated hera_cal
. Not sure why it was failing before?
@adeliegorce ah I see. You probably have a newer version of pyuvdata locally, which works with this. Let's relieve the version of pyuvdata on the branch and see...
Base: 95.98% // Head: 95.98% // No change to project coverage :thumbsup:
Coverage data is based on head (
418a260
) compared to base (5275bd5
). Patch has no changes to coverable lines.
:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.
Had to modify a beam file used in tests because the
data_array
was filled with complex numbers, whichpyuvdata
does not support anymore (release 2.2.12). If tests are still failing, it is because of the future array shapes inpyuvdata
. With this PR, the tests triggering the errorValueError: UVParameter _data_array is not the appropriate type. Is: <class 'complex'>. Should be: <class 'float'>.
are fixed but theValueError: non-broadcastable output operand
remain.