-
Notifications
You must be signed in to change notification settings - Fork 9
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
Stefcal crashes with a completely flagged slot #78
Comments
I see the division-by-zero message a lot and assumed it was for fully flagged tiles, but it's never caused it to bail out. But then also, I've never solved for B.
Maybe it's been fixed in a more recent version than whatever repo this was installed from? |
Hmm yea I will have to dig. It is probably a B jones thing. We solve for G (so take DC out) then B in chunks to get the SNR. This usually gives better results than just one G term. This is as recent as it gets - KERN 3. |
It's initialized as integer 0, then accumulated... so yeah, if an entire tile is flagged, it just remains integer 0. |
I need to add a check for this so it doesn't just fall over stupidly. |
We've recently done similar things to stefcal in our cal pipeline to avoid
crashes on fully flagged data - might be useful to compare notes.
…On 21 December 2017 at 14:01, Oleg Smirnov ***@***.***> wrote:
I need to add a check for this so it doesn't just fall over stupidly.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#78 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAX70J7NkJjHK2xt9nuhJaAzV1dgTTo8ks5tCkipgaJpZM4RJkqK>
.
|
Sharmila reported this. On one of the particularly bad datasets a previous round of selfcal flagged particularly aggressively and the chisq is 0. Why is this an integer?
The text was updated successfully, but these errors were encountered: