Skip to content
This repository has been archived by the owner on Feb 4, 2020. It is now read-only.

NITE dependency, is it necessary? #9

Open
tanismar opened this issue Nov 10, 2015 · 2 comments
Open

NITE dependency, is it necessary? #9

tanismar opened this issue Nov 10, 2015 · 2 comments

Comments

@tanismar
Copy link

Hi,
I was just wondering whether it would be possible to modify the wrapper so that NITE is only optional and not required like now. In the end, most (or at least many) of us using RGBD images do not care too much about skeleton recognition, and it adds complication to the instalation. Moreover, I guess that the wrapper could also run faster if it didn' t have to perform skeleton recognition. It is not an urgent or critical enhancement, but I think it would make things easier and faster to run and install.

Best,
Tanis

@barbalberto
Copy link

👍 It'd be nice
The option I see is to have some skeleton related code under #ifdef and add a CmakeFlag to enable the compilation of this part.
It is not so clean to do and it is not easy to notify the client of this configuration.

Better option would be to create a depthCamera wrapper with only rgb and depth info and then having the kinectWrapper to derive from this adding the skeleton functionality. This requires more work but would be more general.

@pattacini
Copy link
Contributor

Needless to say that temporary workarounds are to be discouraged 😏.
Then, it's only a matter of finding resources to address this request.

Whoever is interested should volunteer to make a PR.

Before starting developing, please report here any work plan you might have in mind, so that we can discuss it and possibly save your time, if we deem it'd go towards the wrong way.

/cc @Tobias-Fischer

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants