-
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 errors in reprocessing #29
Conversation
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.
This all looks basically fine, you just need to document completion of functional testing.
astromon/cross_match.py
Outdated
@@ -747,6 +747,7 @@ def simple_cross_match( | |||
matches['dz'] = matches['x_z_angle'] - matches['c_z_angle'] | |||
matches['dy'] = matches['x_y_angle'] - matches['c_y_angle'] | |||
matches['dr'] = np.sqrt(matches['dy']**2 + matches['dz']**2) | |||
matches['cat_order'] = table.Column(length=len(matches), dtype=int) |
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.
You can do with in one line with:
matches['cat_order'] = np.full(len(matches), 200)
With modern astropy the Column
class constructor is almost never needed for user code.
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.
I adopted this suggestion.
…an empty table (instead of using the Column constructor)
Description
This PR fixes small errors found in reprocessing.
Interface impacts
None
Testing
Unit tests
Independent check of unit tests by [REVIEWER NAME]
Functional tests
All OBSIDs that showed errors previously were processed without error.