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

RAGAVI error #1577

Open
LeonMtshweni opened this issue Apr 6, 2024 · 3 comments
Open

RAGAVI error #1577

LeonMtshweni opened this issue Apr 6, 2024 · 3 comments

Comments

@LeonMtshweni
Copy link
Collaborator

Having a ragavi error that seems a little inexplicable (to me at least)

I've attached my crosscal log file

It seems that K0, G0 and B0 successfully go through and the issue starts when ragavi has to plot the B0 solutions

all the other plots were created just fine, it's just the bandpass ones that seem to be struggling

log-for-my-homie-kman.txt

@Athanaseus
Copy link
Collaborator

Athanaseus commented Apr 8, 2024

Hi @LeonMtshweni, thanks for opening this issue. It's a duplicate of #1565.
Can you please try reproducing this outside the pipeline to see if it has anything to do with resources inside the container or if it's a bug?
Make a fresh virtualenv to run ragavi solely. pip install ragavi.

ragavi-gains --table FullBandWidth32kModeData-1582940762_sdp_l0-1gc1_primary.B0 --corr --cmap coolwarm --field 0 --htmlname FullBandWidth32kModeData-1582940762_sdp_l0-1gc1_primary.B0 --plotname FullBandWidth32kModeData-1582940762_sdp_l0-1gc1_primary.B0.png

To confirm the table is fine, plot it using CASA plotcal and see the output.

@SpheMakh
Copy link
Collaborator

Try refining your calibration (change solution intervals, etc.) then re-run the crosscal, but make sure that you set use_existing_gains to false

@LeonMtshweni
Copy link
Collaborator Author

Thanks, @Athanaseus, but I'd forgotten about this.

My "solution" was not to plot at all; since I'd seen the visibilities so much, I just disabled it.

This happened twice to me, seeing that I opened two separate issues (apologies)

I'll be sure to try this @SpheMakh.

Cheers

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

3 participants