-
Notifications
You must be signed in to change notification settings - Fork 4
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
Bad error message on data without "common good" coarse channels #139
Comments
The recent changes we made to the error handling now mean that the error messages look like this.
These error messages used to be very helpful for diagnosis, as without this message, you need to download the raw files to see what's going on, so I'll see what I can do to make the display of this error message a little more detailed. |
Can you point to the code that you claim have now made error messages look this way? |
I'm seeing a few of these failures in ASVO recently. Do we really want the main thread panicing? Since we can catch this specific error, why not exit properly with a return code and message? (as opposed to a panic) |
Yep, basically all that needs to happen is:
|
i.e.
(I assume Birli attempted to preprocess the obsid into a ms/uvfits.) This happens on obsid 1150224192 (I have the data on /astro).
Ideally,
Birli
shouldn't have anyunwrap
s; all instances of unrecoverable errors should emit a human-readable error message instead. I'm happy to offer experience here as I've tried to be thorough withhyperdrive
. The presence ofunwrap
here is ultimately responsible for the bad error message.The text was updated successfully, but these errors were encountered: