Right now, the new lstbin_simple.py assigns times/JDs to files that can cause visibilities to load out of order in pyuvdata. Here's an example:
This leads to annoying effects when loading large waterfalls. For example:
Since the JDs are arbitrary, we should pick a starting LST and a JD that corresponds to, and then all LSTs after that (even after the 2pi phase wrap) would correspond to larger JDs.
Right now, the new
lstbin_simple.py
assigns times/JDs to files that can cause visibilities to load out of order in pyuvdata. Here's an example:This leads to annoying effects when loading large waterfalls. For example:
Since the JDs are arbitrary, we should pick a starting LST and a JD that corresponds to, and then all LSTs after that (even after the 2pi phase wrap) would correspond to larger JDs.
This came up in H1C, which is why
LST2JD
has some utility parameters to make this easier: https://github.com/HERA-Team/hera_cal/blob/e68775af51dead44879d2ed3bc8860185bda3c51/hera_cal/utils.py#L550