Question about the Track creation and confirmation about eagermot HOT 2 CLOSED

I have the same question. It seems that the code implementation only tracks the objects with 3D detection. The 2D-only detections are not used to create tracks.

from eagermot.

@ideasplus
You are right that the text is not totally correct
time_since_2d_update is used to decrease track confidence if it has been too long since the last 2D confirmation
hits, which is counted for both 3D or 2D matches is used to actually confirm tracks for reporting.
So, it is not required to have a recent 2D match, but if there were no 2D matches for a long time, track confidence will be lower and it will probably be lower than the evaluation threshold

@ideasplus @Deephome There is no such thing 2D-only objects since we do 3D MOT only. It is possible to initialize tracks with 2D only and then match 3D boxes to it, but since you cannot actually report them until you have 3D boxes on them, it is pointless to initialize early.

Sorry for the late reply, was busy with other stuff and did not get proper notifications. Check out my latest work https://polarmot.github.io/

from eagermot.