Adding parentIds for motion scan effect

[PhRosenberger]

As written in #45, the motion scan effect node is currently flying around besides the tree.
This PR should solve it.

[ClemensLinnhoff]

See my comment in the corresponding issue. I do not see the motion scan effect producing false positives or false negatives. The detections are all valid, just at a different position than expected.

[PhRosenberger]

See my comment in the corresponding issue. I do not see the motion scan effect producing false positives or false negatives. The detections are all valid, just at a different position than expected.

I just inserted the detection state error node for this.

[PhRosenberger]

@TimoHinsemann as this PR inserts several parentIDs, I guess I also need to provide references for each of these new connections, right?

[PhRosenberger]

This PR relates to #37 based on #36. We should somehow merge/discuss both concepts.

[ClemensLinnhoff]

What about this PR @TimoHinsemann? Is it out-dated and can be closed?

[TimoHinsemann]

What about this PR @TimoHinsemann? Is it out-dated and can be closed?

Hey @ClemensLinnhoff, yes, with the last update of the develop-branch, the issues #36, #42, #45 and #48 should be solved. So this PR here can be closed. A double-check from your side - to be on the safe side - would be maybe useful. After that, we should merge the develop-branch into the main-branch. I will create a PR for that now.

@PhRosenberger I am very sorry for not reaching out after your last comment here, not only the thesis was stealing my time but also I missed to change my Notification-Mail-Adress to the company adress. I hope the new commits are in your interest!