Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Intergrate other detection algorithm. #85

Open
lff12940 opened this issue Dec 15, 2020 · 3 comments
Open

Intergrate other detection algorithm. #85

lff12940 opened this issue Dec 15, 2020 · 3 comments

Comments

@lff12940
Copy link

I integrated other detection algorithms and used the provided scripts for message conversion, but I encountered the following problems:

[ WARN] [1608023759.960176417, 1439557604.073015311]: Jump back in time detected. Deleting all existing tracks. Old time was 1439557603.966, new time is 1439557603.945 (dt=-0.021 sec)!
[ WARN] [1608023760.593699488, 1439557604.198680538]: Jump back in time detected. Deleting all existing tracks. Old time was 1439557604.099, new time is 1439557604.057 (dt=-0.042 sec)!
[ WARN] [1608023761.217882125, 1439557604.323381596]: Jump back in time detected. Deleting all existing tracks. Old time was 1439557604.233, new time is 1439557604.138 (dt=-0.095 sec)!

The detection algorithm is: DROW and DR-SPAAM person detectorshttps://github.com/VisualComputingInstitute/DR-SPAAM-Detector

Can anyone help me? How to solve this problem?

THanks.

@tlind
Copy link
Member

tlind commented Dec 15, 2020

Hi, it seems that your messages arrive slightly out-of-order. An easy workaround would be to add a small tolerance in delta time in the condition of the if statement within the tracker:

if(currentTime < m_cycleTime) {
// This usually happens when playing back a bagfile and looping
ROS_WARN("Jump back in time detected. Deleting all existing tracks. Old time was %.3f, new time is %.3f (dt=%.3f sec)!", m_cycleTime, currentTime, currentTime - m_cycleTime);

Are you running multiple detectors in parallel (all publishing to the detected persons topic that is input to the tracker), and they are not temporally synchronized?

@lff12940
Copy link
Author

Thanks. It worked when I add a tolerance in delta time.

I replaced the laser detectors with DR-SPAAM-Detector in the launch file tracking_on_bagfile.launch.
At present, I have integrated DR-SPAAM detector and upper-body detector using front_laser and front_rgbd, but the fused detections are not good. There are many false detections in the test results. How should I fine tune for better result?

Thanks.

@tlind
Copy link
Member

tlind commented Dec 21, 2020

Which detector is mostly causing these false alarms? Or are the detections from the individual detectors okay, and the problem is at the fusion stage? Maybe you could attach a picture or short video.

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

No branches or pull requests

2 participants