-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Execution Block ID uid://A001/X15a0/Xca Sgr_A_st_h_03_TM1 #142
Comments
The actual data and final images look good here, but there are a few areas in the calibration that I feel should have been addressed during QA2. I've listed some of the more obvious ones below. I think they're relatively minor issues in the end, but should probably still be flagged out. It'd be great if someone else could check through this to get another opinion(s). Stage 7 (Tsys): Some examples of contamination in the Tsys data in the science SPWs (spikes that coincide with the frequency range of the science SPWs which are shown as coloured bars at the bottom). This is almost always present in our data, but is usually flagged out during QA2.Stage 9 (WVR): DA42 seems to have some phase jumps in the first scan.Stage 19 (applycal): Absorption and phase spread for phase calibrator J1744. This is a persistent issue for this calibrator and is usually flagged before delivery. |
As mentioned earlier, the calibration here could be improved by adding a few more flags. However, the final calibration looks reasonable, and the images look good. I think we can safely leave this for now, and consider re-running the PL with additional flags at a later date. I will take responsibility for that. Other than this, the only outstanding issues relate to the size mitigation:
Once these are resolved, this should be good to go. |
Latest PL run (Pipeline Run 20220622T040354) failed at cube imaging stage, with errors:
|
@keflavich the cleaning parameters have been updated in #299. Once this PR has been merged, the cleaning for this region should be executed again to undo cube size mitigation and avoid divergence in SPW 33. |
Co-authored-by: g25238dw <[email protected]>
Reimaging has been started. spw35 finished waaaay too fast... |
Very odd. spw35 reported success even though it was an extreme failure - this is a constant annoyance with CASA, since it doesn't use python's traceback system properly. The failure was:
I've never seen this before - the error message doesn't tell us clearly what's going on, but I suspect there was a filesystem issue of some sort? This is particularly scary, because it did end up creating entirely useless (corrupt) .image files |
All cubes have been imaged at full spectral resolution, and SPW 33 doesn't seem to have diverged this time. Marking this one as done. (Though note that we still have the calibration issues that we're investigating more generally ...) |
Sgr_A_st_h_03_TM1
uid://A001/X15a0/Xca
Observations completed?
Delivered?
Downloaded? (specify where)
Weblog unpacked
Weblog Quality Assessment?
Extra Weblog Sgr_A_st_h_03_TM1_0 -> pipeline-20220622T040354, Extra Weblog Sgr_A_st_h_03_TM1_1 -> pipeline-20220522T194503
Imaging: Continuum
Imaging: Lines
Product Links:
Reprocessed Product Links:
The text was updated successfully, but these errors were encountered: