You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
stvid currently uses a minimum number of points from raw points or hough3dlines -a configuration option of “proportional track points” would be useful in further limiting false positives.
For example, with a low limit on ntrkmin or nhoughmin induces a number of false positives - many of which have very long "phantom tracks, apparently stitched together from [10] points across the FOV.
A nice feature would be to look for something like “>50% fill” on track points across the image arc, which could be a small number of points for a slow satellite, or a large number of points for a large track.
It would probably still probably be appropriate to also enforce a "minimum" number of points, but this would allow setting the minimum lower.
Looking at how houghpoints works, this looks non-trivial, but I’ll put it in the wishlist anyway as a reminder.
The text was updated successfully, but these errors were encountered:
stvid/configuration.ini-dist
Lines 58 to 62 in 57b11b1
stvid currently uses a minimum number of points from raw points or hough3dlines -a configuration option of “proportional track points” would be useful in further limiting false positives.
For example, with a low limit on
ntrkmin
ornhoughmin
induces a number of false positives - many of which have very long "phantom tracks, apparently stitched together from [10] points across the FOV.A nice feature would be to look for something like “>50% fill” on track points across the image arc, which could be a small number of points for a slow satellite, or a large number of points for a large track.
It would probably still probably be appropriate to also enforce a "minimum" number of points, but this would allow setting the minimum lower.
Looking at how houghpoints works, this looks non-trivial, but I’ll put it in the wishlist anyway as a reminder.
The text was updated successfully, but these errors were encountered: