-
Notifications
You must be signed in to change notification settings - Fork 9
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
Setting a vertex along with an ROI #47
Comments
Currently can draw vertex. Need to decide how to save that information into an ROI. |
Looks like @drinkingkazu has written storage class for 2D vertex: a22f14b. going to merge master with tmw_roi_feature and then utilize object to store hand-scanned vertex. |
Lauren found a bug. Occurs when loading ROIs from file.
|
@twongjirad a clarification on 2D stuff in 2 categories: Simple product for pixel location info Sophisticated product for geometrical calculation (algorithm to be ported from another geometrical computation package) I think anything a user will do from GUI has no better precision than a pixel point, so Pixel2D should be enough. |
I finished the save feature here. Will check into tmw_roi_feature soon. |
finished: d839117 |
For certain scanning tasks, we might want to be able to set a vertex in conjunction with the ROI. The immediate use case is for scanning Michel electrons. The ROI encapsulates the entire shower while the vertex marks the point of the decay. Together, along with Kalman filter, we'd start from vertex and follow muon in order to mask it, leaving only the electron charge. Also, vertex provides target for regression.
I've made a first attempt at 0511351
An example of what a user might label is here:
If can develop algorithm to follow muon, then we can avoid having users mark pixels directly.
The text was updated successfully, but these errors were encountered: