Details
-
Type:
Bug
-
Status: Done
-
Resolution: Done
-
Fix Version/s: None
-
Component/s: meas_astrom
-
Labels:
-
Story Points:2
-
Epic Link:
-
Sprint:Alert Production S17 - 5
-
Team:Alert Production
Description
Bugs have been found in the latest refactor of matchPessimsiticB that effect performance of the matcher.
failedPatternList persists between runs of MatchPessimisticBTask when running a range of ccds in the same processCcd run.
failedPatternList is not currently used properly in the matcher loop.
The pair_id lookup table is not filled with the correct data for half of the matrix.
Attachments
Activity
| Field | Original Value | New Value |
|---|---|---|
| Epic Link |
|
| Status | To Do [ 10001 ] | In Progress [ 3 ] |
Discovered two bugs in the code.
The first was that the lastMatchedPattern and failedPatternList were not properly filled or used. The second was more substantial and effected code performance.
The lookup table the code uses to quickly grab data for each of the candidate spokes (_pair_id_array) was filled incorrectly. Specifically the lower triangular portion of the matrix (which is filled on line 130) was, instead of being filled with the first id of the pair, filled with the second id of the pair. This resulted in half the data being unusable and degraded performance (I ran some CFHT data I had previously and noticed significantly more failures.) The performance has now ben restored with this fix.
| Reviewers | Russell Owen [ rowen ] | |
| Status | In Progress [ 3 ] | In Review [ 10004 ] |
Looks good. A few comments in github.
| Status | In Review [ 10004 ] | Reviewed [ 10101 ] |
Completed code review, Jenkins CI, and pushed to master.
| Resolution | Done [ 10000 ] | |
| Status | Reviewed [ 10101 ] | Done [ 10002 ] |
Created new ticket branch and started search for bugs in the code.