-
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
Fix MAG_ACA_ERR units for guide selection #123
Conversation
Did you check the #120 obsid? |
Yes, I commented over there on #120 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍 with #125 in place.
By "with #125 in place" did you mean with the issue in the list or with the test made? |
With the issue in the list. |
This is failing for me. Did it pass tests for you?
|
I did run the tests, but I guess I've got to be better about having the terminal print branch and commit. I must have retested in master or the like instead of properly testing in my branch. |
OK, I'll make a fix. |
Thanks. And I just figured out what I did. I checked out master to reproduce the error in #120 and then forgot that I was in the wrong branch for my run-for-record test. So less a general process fail and more a specific process fail related to trying to see an error in another branch. |
I've been more in the habit lately of running all tests before making a commit, esp. for something that I expect to pass (not a WIP). And likewise I'm trying to run all tests immediately before pushing to GitHub. This is part of why I want to keep our unit tests reasonably fast. |
Fix MAG_ACA_ERR units for guide selection
I considered adding a new column to the candidate list, but then just used the 0.01 conversion in the two new places that this is used thanks to #105 .
This fix and mag err use in general probably needs more review and better tests, but this might be enough for an updated release candidate for today.
Closes #120