There seems to be an issue when the ordering of the input UVData is not "time". I came across this in testing for the hera_sim wrapper. The TLDR is that if you reorder the UVData object to anything but "time", then put it into pyuvsim, then reorder back to time, the resulting data array doesn't look right (eg. looking at data for non-redundant baselines gives the same visibilities, which can't be true).
I'll put a not-quite-minimal failing example below, copied from the hera_sim tests. Note that we run this test over all our wrappers (eg. VisCPU and Healvis) and it passes for them.
There seems to be an issue when the ordering of the input UVData is not "time". I came across this in testing for the hera_sim wrapper. The TLDR is that if you reorder the UVData object to anything but "time", then put it into pyuvsim, then reorder back to time, the resulting data array doesn't look right (eg. looking at data for non-redundant baselines gives the same visibilities, which can't be true).
I'll put a not-quite-minimal failing example below, copied from the hera_sim tests. Note that we run this test over all our wrappers (eg. VisCPU and Healvis) and it passes for them.