-
Notifications
You must be signed in to change notification settings - Fork 0
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
acqs.make_report() throws IndexError #234
Comments
That's pretty weird, I cannot reproduce on my mac at exactly the same version.
|
And I get a pass from that example on HEAD linux ska3-flight. |
I'll look at this more later
|
FWIW I ran the same on fido and did not get an error. I even went into your git repo and ran from that (with |
"real problem"? |
"real problem" => something that makes proseco work differently on a different platform for a correctly configured user environment. (E.g. when SOT MP runs proseco). |
Well, so far I've gotten it to fail twice as the ACA user in what I think is a correctly configured environment, and what I think is a correctly configured environment for me is now failing intermittently. So it is certainly interesting. I took minor offense at "real problem" because this was a real problem for me when I couldn't make an acq report for 48492 in JAN1419A. |
OK well maybe it is a real problem (in the code), not user configuration error. hmm. |
Heck, it probably is a user configuration error of some kind, but if the user can't figure it out the code may have to provide more breadcrumbs. I was doing most of my broken tests with proseco.catalog.get_aca_catalog and with a pylab ipython session, but didn't narrow it down more to figure out why the acqs._bad_star_mask sometimes seems to get set to a value that is inconsistent with the acqs. But already tried too many combinations today trying to get it to break to get useful debug. |
I still can't reproduce, even as |
Dang, I thought the pylab might have been the problem. In general using |
OK. It was intermittent even with pylab but if you narrowed it down to something in there that's fine. I wasn't sure if the problem was somewhere in matplotlib that was just "showing its face" more with pylab. |
I forgot the second half of the first sentence, namely, "but no, it still worked for me". |
Hah. OK, I'll make some time this week to see if I can reproduce it as the ACA user with --matplotlib . |
Well I ran 3 times in a row with |
Yes, I'm working in NX (even when I'm on console I tend to work in the NX session). But if related to nx this would be the first really intermittent issue. |
The text was updated successfully, but these errors were encountered: