While trying to merge #216 came across some issue related to the coordinates it seems Astropy has been gradually tightening the API around frames and Time specifically:
- Frame attributes must be scalar or strictly broadcastable
- Time (hashing, shape handling, broadcasting edge cases involving None / masked values).
This mean the current implantation breaks looking back I don't think having obstime_end as frame attribute is a good approach a frame is only valid with a scalar time or array of times broadcast able to the coordinates or vice versa.
Move the observation time range to a different object (visibilities or map) and keep frame with single time obstime.
While trying to merge #216 came across some issue related to the coordinates it seems Astropy has been gradually tightening the API around frames and Time specifically:
This mean the current implantation breaks looking back I don't think having obstime_end as frame attribute is a good approach a frame is only valid with a scalar time or array of times broadcast able to the coordinates or vice versa.
Move the observation time range to a different object (visibilities or map) and keep frame with single time
obstime.