GNU Astronomy Utilities - Tasks: task #15884, Add a column in the log file for...
You are not allowed to post comments on this tracker with your current authentication level.
task #15884: Add a column in the log file for equal matchings in Kd-tree matching
Submitter: | Sachin Kumar Singh <sks_15> | ||
Submitted: | Sat 16 Jan 2021 05:36:47 PM UTC | ||
Should Start On: | Sat 16 Jan 2021 12:00:00 AM UTC | Should be Finished on: | Sat 16 Jan 2021 12:00:00 AM UTC |
Category: | Match | Priority: | 5 - Normal |
Item Group: | Enhancement | Status: | None |
Privacy: | Public | Percent Complete: | 0% |
Assigned to: | None | Open/Closed: | Open |
Effort: | 0.00 |
Mon 18 Jan 2021 11:18:35 PM UTC, comment #4: |
Mohammad Akhlaghi <makhlaghi>![]() |
Mon 18 Jan 2021 05:27:36 PM UTC, comment #3: Should we include these equidistant points in the final output or just take any one of them and report this to the user? |
Sachin Kumar Singh <sks_15>![]() |
Sun 17 Jan 2021 06:00:33 PM UTC, comment #2: Sorry, by "reported" I meant it is only seen in k-d tree matching. For simple coordinate based matching, it simply uses the top point in the sorted list of points. |
Sachin Kumar Singh <sks_15>![]() |
Sat 16 Jan 2021 08:17:14 PM UTC, comment #1: Thanks for raising this very interesting point Sachin!
|
Mohammad Akhlaghi <makhlaghi>![]() |
Sat 16 Jan 2021 05:36:47 PM UTC, original submission:
In real world scenarios, the distance between 2 objects cannot be precisely equal due to presence of noise in datasets. But to account for such anomalies we should report them in the log-file during matching. This is currently reported for cases which use Kd-tree for matching.
|
Sachin Kumar Singh <sks_15>![]() |
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Follows 1 latest change.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2021-01-16 | sks_15 | Assigned to | sks_15 | ![]() |
None |
For now, take the first node that is found (or the simplest solution in general). After everything works, we can add the extra column to let the user know of the problem.