microsoft / microsoft/3DTelecommunications

Expose TIMESTAMP_SCALE from BufferAggregator.cpp as a 3DTelemedicine.cfg config file parameter

Open
#6 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C++
Stars
24
Forks
5
PR merge metrics
No merged PRs in 30d

Description

The TIMESTAMP_SCALE is a Fusion parameter similar to the MaximumTimeSeparationOfSubFrames calibration parameter. Both define the number of microseconds that should be accepted between two frames of different Kinects to consider that the capture is synchronized for a given timepoint.

Ideally, both parameters should be set to 2000.0 given that, with ideal hardware configuration, up to 10 Kinects can be synchronized within that time scale. However, difference in hardware and environment configuration (e.g., sync cable length, temperature) might affect the sync signals requiring that value to be raised. IMPORTANT: the need for raising this value often indicates that something hardware-related is not ideal with the 3DTM system.

Currently, TIMESTAMP_SCALE is hardcoded to 2000.0 in the Networking/BufferAggregator.cpp file and we would like to expose it as a parameter of the [Fusion] section in the 3DTelemedicine.cfg file. This can be achieved by making TIMESTAMP_SCALE a member variable of the BufferAggregator class, and update the value in the DataCaptureNetworkMultiView subclass with the value read from the FusionConfig::current() conf object.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with Networking/BufferAggregator.cpp and locate the hardcoded TIMESTAMP_SCALE value and the BufferAggregator class. Then inspect DataCaptureNetworkMultiView and the Fusion section of 3DTelemedicine.cfg, including FusionConfig::current(). Done means TIMESTAMP_SCALE can be configured there instead of remaining hardcoded at 2000.0.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
networking
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.