[PIPE2D-274] Identify start of new apertures more carefully. Created: 09/Mar/18  Updated: 09/Mar/18  Resolved: 09/Mar/18

Status: Done
Project: DRP 2-D Pipeline
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Normal
Reporter: cloomis Assignee: Unassigned
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

The findCenterPositionsOneTrace routine identifies one trace per call. It starts each time by stepping up through rows looking for the start of an "aperture": a wide-enough and bright-enough span of columns, then tracing the full aperture, marking it in the image, then returning. The logic to continue searching after hitting an old or a failed aperture match was not able to find multiple apertures which started at a given row.

Given the tricky book-keeping and logic, I now pass the next unexamined pixel on the first matched row back to the caller, which then passes that back in to findCenterPositionsOneTrace to initialize the next aperture search.



 Comments   
Comment by cloomis [ 09/Mar/18 ]

Merged in b96cb99

Generated at Sat Feb 10 15:50:27 JST 2024 using Jira 8.3.4#803005-sha1:1f96e09b3c60279a408a2ae47be3c745f571388b.