-
Notifications
You must be signed in to change notification settings - Fork 6
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
Crash when plotting AMP vs. FREQ over 8 SPWs #94
Comments
Btw, when installing shadeMS via pip (following #95), I get the same error. |
Ok perhaps I should have checked #85... It's a different error that is output though. |
Same underlying cause as #85 I'll bet. Good excuse to bite the bullet and sort out SPW support properly. Could you please split out one scan of your MS for me @Jordatious, for testing? |
Hey @o-smirnov, Sure! I put the first scan of the target (scan 3) here:
Interestingly, I get the same error when I try to plot this manually... I have no idea how
|
That's not too surprising. I suppose |
Ahhh ok that makes sense. You may already know, but this works for me, which you can see corresponds to the channel count from here:
|
Yep so this is working for me when I iterate over the above, and it's quite fast actually. The plotting bit is what takes so long... Just a quick correction to the above, which I've edited - this was the run where I have all 8 SPWs, without overlap, only avoiding RFI bands, so there's no missing bands. It's the one for which I'm running CubiCal, which was partially successful, and which I'll report back about later. Part of determining why it wasn't 100% successful is plotting the |
I'm getting the error below when calling shadeMS in the following way:
I managed to get it working when plotting amplitude as a function of time, but not as a function of frequency, as with this call.
Here's some info about the data in case it's useful. There are discontinuities between SPWs, either side of RFI bands. And then obviously the number of channels isn't consistent between SPWs. I'm not sure if that's problematic or not.
Log:
The text was updated successfully, but these errors were encountered: