Page MenuHomePhabricator

No error message displayed when incorrectly using Polhemus tracker
Closed, WontfixPublic

Description

  • Unplugging one sensor while tracking gives no error or warning, but stops the tracking completely.
  • Editing the tools in the Tool Manager, namely changing to a wrong identifier does not lead to any error or warning, and tracking still works fine.

Event Timeline

aguilera created this task.
seitela renamed this task from Robustness test with Polhemus tracker to No error message displayed when incorrectly using Polhemus tracker.Feb 6 2018, 5:18 PM
seitela moved this task from Wishlist to In Progress on the IGT board.
  • Unplugging one sensor while tracking gives no error or warning, but stops the tracking completely.

The id of the last data frame is not updated after being unplugged.

When unplugging the sensor, the tracking tool coordinate system is not anymore displayed inside the tracking surface. Instead, it appears in a point far away (the 3D display may needed to be moved in order to see it). Consequently, the coordinates change to a range 900-1300 and stay with those static values en the last data frame. The same procedure is reproduced in the Polhemus tracking software (PiMgr), and the tracked tool moves to a position far away as well.

One possible solution could be to calculate the difference between the last two data frame positions, and in case of being too big, popping up a MITK error.

Tried to take into account the change in the tool co-ordinates. But the tool co-ordinates doesn't change in every frame read. So there is no robust way to detect the unplugging of tool via the change in tool co-ordinates .

This should be re-investigated. Not clear yet why a detection of a sudden change in coordinate values is not possible.
Detection of unplugging the sensor / the field generator is an important security feature.

kislinsk removed aguilera as the assignee of this task.
kislinsk added a project: Auto-closed.
kislinsk added a subscriber: kislinsk.

Hi there! 🙂

This task was auto-closed according to our Task Lifecycle Management.
Please follow this link for more information and don't forget that you are encouraged to reasonable re-open tasks to revive them. 🚑

Best wishes,
The MITK devs