...
The pipeline will occasionally produce a long solution interval on the order of 1000s. This happens when an 8bit setup is used two or more times, separated by a different setup. The sol int will span from the last phase scan of the first group to the first phase scan of the next group of same setup. This is related to combine='scan' in gaincal. In the worst cases, an additional effect seems to be that the pipeline somehow averages data between different fields.
Action items
- We may rerun affected data sets once the new VLASS pipeline release is out, which should include the sol int fix. Record data sets here (beginning March 2022):
22A-213.sb41491377.eb41616712.59644.96001018518
22A-241.sb41377957.eb41680272.59649.890064039355
22A-241.sb41378125.eb41689787.59650.7527708912
22A-241.sb41375602.eb41690397.59650.81631440972
22A-384.sb41328518.eb41743936.59667.038647291665
22A-384.sb41327578.eb41747213.59670.45745663195
22A-241.sb41375602.eb41690397.59650.81631440972
22A-458.sb41707771.eb41715281.59655.09601050926
22A-384.sb41328223.eb41722982.59659.21360027778
22A-384.sb41329155.eb41734310.59662.292689884256
maybe:
22A-113.sb41269220.eb41716197.59655.43097969907
22A-059.sb41209756.eb41667846.59648.560902627316
22A-423.sb41178301.eb41746986.59668.50978758102