RandomTracking Device should be able to generate statistical noise:
Gaussian noise around some calculated 'path' in space would be useful for further testing of IGT.
Description
Related Objects
Event Timeline
Assigning this to default assignee because mbi-bug-manager is not a person and cannot evaluate/reassign this bug. Would you please assign it to the correct product/component and estimate whether it is relevant for the 1.0 release? Thank you.
nice feature for MITK-IGT Release 2, but not for MITK 1.0. Party bug that can be done by everyone.
re-assign to default assignee.
I think this should be part of the next IGT implementation cycle after the BVM.
After discussion with requester we chose to add functionality to mitkVirtualTrackingDevice to enable a normalVariateGenerator to add gausian noise to tracking coordinates. In a first step a defined track will be generated and its positions will be distorted by noise. In the future a file shall be specified to open with a TrackingPlayer and thus to simulate more realistic tracking paths.
This is meant to be implemented to test noise reduction filters that are hung up in the IGT pipeline and denoise the tracking coordinates.
Wiki Specification to be written shortly!
(In reply to comment #4)
In the future a file
shall be specified to open with a TrackingPlayer and thus to simulate more
realistic tracking paths.
VirtualTrackingDevice/RandomTrackingDevice should not open files with stored paths, that's the job of mitk::NavigationDataPlayer
needs core modification; Wiki specification page written.
Core modification requests are only needed for mitk/Core and mitk/CoreUI folders, not for the modules.
Resetting the flag. I'd have accepted the request, however, because it relates to test enhancements.
Removed party keyword.
This bug was assigned to me last year when I began working here as part of a practice project. Had no time to work on it so far. I will take a look at it in the next weeks.
Resetting all bugs without active assignee flag to "CONFIRMED". Change status to IN_PROGRESS if you are working on it.
I would suggest to separate the statistical noise from the tracking device class into a NavigationDataToNavigationData Filter that adds noise to its inputs. This could then be reused more easily for all kinds of tracking sources.
User cheray has pushed new remote branch:
bug-2176-GaussianNoiseForVirtualTrackingDevice