1 / 3

Proposed XRT Timing Patterns (18 Sept 2003)

Proposed algorithm aims to classify events in XRT data by optimizing pattern recognition with "islands" and rejected patterns, ensuring accurate identification. Modification of existing scheme is suggested to enhance recognition precision.

yardley-rosario
Download Presentation

Proposed XRT Timing Patterns (18 Sept 2003)

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Proposed XRT Timing Patterns (18 Sept 2003) • We need: • Event “islands” separated by blank pixels • Smallest event “islands” possible (to minimize algorithm pile-up) • Recognition and classification of all events up to 3 pixels wide • Recognition and classification of all rejected patterns • Algorithm needs: • Event patterns centered on maximum pixel • Constant pattern size • We can accomplish both by a small modification of Julian’s proposed event classification scheme. • In order to accommodate the PD 3 pixel off-centered events, we need a 7 pixel pattern • In order to minimize island size, we need “don’t care” pixels • “Don’t care” pixels should not be dropped from pixel list

  2. Proposed XRT Timing Patterns (18 Sept 2003) Valid Invalid 0 6 X X X X X X 1 7 X X X X WT 2 8 X X X X 3 9 X X X X PD 10 X 11 Valid for PD modes 4 X X 12 X 5 X X 13 14 15

  3. Problems with event recognition Potential problem with invalid “islands”: cannot remove from event list because you need them to classify adjacent pixels. Examples: 15 6 X X Can this be solved by retaining the pixels for invalid events in the event list? Will that cause other problems?

More Related