Skip to content
Snippets Groups Projects

WIP: Resolve "Add time stamp tolerance to problem::check()"

1 unresolved thread

Closes #340 (closed)

Merge request reports

Pipeline #5748 passed

Pipeline passed for 70017378 on 340-add-time-stamp-tolerance-to-problem-check

Merged by Joaquim Casals BuñuelJoaquim Casals Buñuel 5 years ago (Jul 2, 2020 10:13am UTC)

Loading

Pipeline #5783 passed

Pipeline passed for 0abdcf54 on devel

Activity

Filter activity
  • Approvals
  • Assignees & reviewers
  • Comments (from bots)
  • Comments (from users)
  • Commits & branches
  • Edits
  • Labels
  • Lock status
  • Mentions
  • Merge request status
  • Tracking
375 375 << " -X-> Cap" << id();
376 376 log.assertTrue((f->getCapture() == _cap_ptr), inconsistency_explanation);
377 377 }
378 //Check that the capture is within time tolerance of some processor
379 auto frame = getFrame();
380 double time_diff = fabs(getTimeStamp() - frame->getTimeStamp());
381
382 //It looks like some gtests add captures by hand, without using processors, so the processor list is empty.
383 //This inicialization is needed because if the list empty the execution does not go into the loop and the
384 //assertion fails
385 bool match_any_prc_timetolerance;
386 if(getSensor() != nullptr )
387 {
388 match_any_prc_timetolerance = getSensor()->getProcessorList().empty();
  • Please register or sign in to reply
    Loading