Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revision | Next revisionBoth sides next revision |
huibintemaspampipeline [2019/02/18 11:37] – huibintema | huibintemaspampipeline [2019/02/18 11:37] – [Old hardware-correlator observations] huibintema |
---|
</code> | </code> |
| |
The second option is to turn on baseline-based calibration, BUT ONLY AFTER VERY CAREFUL CONSIDERATION. In an ideal world, baseline-based calibration would never be necessary. However, I have witnessed situations using hardware-correlator data in which residual gain errors on baselines did not seem to be solely antenna-based. Baseline-based calibration is something to try as a last resort, and can be switched on in the pipeline as shown below. Please note that this is implemented under strict limitations: baseline-calibration is applied only in the final stages of the processing, and is determined on a per-observation base (meaning only one correction per observe session). | The second option is to turn on baseline-based calibration, BUT ONLY AFTER VERY CAREFUL CONSIDERATION. In an ideal world, baseline-based calibration would never be necessary. However, I have witnessed situations using hardware-correlator data in which residual gain errors on baselines did not seem to be solely antenna-based. Baseline-based calibration is something to try as a last resort, and can be switched on in the pipeline as shown below. Please note that this is implemented under strict limitations: baseline-calibration is applied only in the final stages of the processing, and is determined on a per-observation base (meaning only one correction per baseline per observe session). |
<code python> | <code python> |
process_target( target_uvfits_file_name, do_blcal = True ) | process_target( target_uvfits_file_name, do_blcal = True ) |