Page MenuHomePhabricator

Logging of absolute time stamps is not possible
Open, NormalPublic


When navigation data is logged via the IGT Tracking Toolbox, only the relative elapsed time is written to the log file. From the log file itself, the reference point in time is not clear.

By default, the elapsed time since the start of tracking is logged. The NavigationDataRecorder contains a flag (m_StandardizeTime) to control whether the elapsed time should be logged with respect to the start of logging.

The default elapsed time originates from TrackingDeviceSource::GenerateData() where IGTTimeStamp::GetInstance()->GetElapsed() is used. Are there any specific reasons why the current time stamp is not used (e.g. Unix time stamp that can then be converted to a human-readable date)?

Steps to reproduce:

  • Open IGT Tracking Toolbox
  • Select Virtual Tracker
  • Add Single Tool
  • Connect and start tracking
  • Switch to Logging tab
  • Enable Limit Number Of Logged Frames
  • Click Start Logging

--> The first column of the CSV file contains the elapsed time

Event Timeline

eisenman triaged this task as Normal priority.Sep 13 2019, 3:19 PM
eisenman created this task.
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

A fix of this bug is available here: (thanks to @kannberg !). However, while testing the fix, I found a logging bug which is probably more important and should be fixed first: T29082. Afterwards the time stamp fix can be tested properly and be merged.