See e.g. the MS elwood:/home/kassaye/KAT_sources/PKS1939-6342.MS (reported by @Ermiasabebe). This has multiple observation IDs stuck together, so when it is processed in a single gulp, MSSeqOutputChannel starts throwing exceptions when it gets to a chunk where time has stepped backwards:
The right solution is to either (a) sort by TIME on the input (which may be a performance hit, especially when 99.9% of MSs are sorted by time anyway), or (b) throw an error on the input. After all, a user can pre-sort an MS once and for all to avoid this problem.
See e.g. the MS
elwood:/home/kassaye/KAT_sources/PKS1939-6342.MS(reported by @Ermiasabebe). This has multiple observation IDs stuck together, so when it is processed in a single gulp, MSSeqOutputChannel starts throwing exceptions when it gets to a chunk where time has stepped backwards:The right solution is to either (a) sort by TIME on the input (which may be a performance hit, especially when 99.9% of MSs are sorted by time anyway), or (b) throw an error on the input. After all, a user can pre-sort an MS once and for all to avoid this problem.