Skip to content
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

Continuum pipeline flow - round1 waits for all beams #109

Open
tjgalvin opened this issue May 27, 2024 · 1 comment
Open

Continuum pipeline flow - round1 waits for all beams #109

tjgalvin opened this issue May 27, 2024 · 1 comment

Comments

@tjgalvin
Copy link
Owner

In the current continuum imaging and self-calibration workflow there is a draining of works waiting for all beams to finish imaging + source finding while the initial set of images (pre self cal) are produced. This means that some significant mount of time may be wasted waiting for one beams to finish image. The other beams should still be able to go through all rounds of self-cal.

I believe that this is happening for two potential reasons:

  • Getting the MSSummary object after imaging. If this is not respected properly the self-cal task would zip the MS up, and the MSSummary would be unable to run.
  • waiting for all images to complete to get a common beam out, which might go into the FieldSummary

In either cases, one of these two stages is getting itself into the dependencies of the self-calibration task. I see that the masking stages all happening asap, so there is something going into the self-cal task that is not in the masking tasl that is causing things to block.

@tjgalvin
Copy link
Owner Author

tjgalvin commented Jun 4, 2024

Perhaps the better approach is to make all the images in on go, and only bother with the linmos and validation plots at the very end. This is alternative to the current form, which is image -> linmos -> image -> linmos.

By linmos I mean convolving to common beam, co-adding, source finding.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant