Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
    • Help
    • Support
    • Submit feedback
    • Contribute to GitLab
  • Sign in
bob
bob
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 3
    • Issues 3
    • List
    • Boards
    • Labels
    • Milestones
  • Merge Requests 0
    • Merge Requests 0
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • bob
  • bobbob
  • Issues
  • #54

Closed
Open
Opened May 16, 2012 by André Anjos@andre.anjos💬
  • Report abuse
  • New issue
Report abuse New issue

LBPTopOperator is untested and seems to be buggy

Created by: laurentes

The current LBPTopOperator implementation is a port of some older torch5spro code. Unfortunately, it suffers from the following problems (non-exhaustive list):

  • No unit test!
  • Does not seem to work!
  • Poor python bindings (no helper functions to get information about the expected size of the output)
  • Generic C++ core exceptions rather than specialized ones
  • Few check on the input/output array size are performed

This requires some serious revision.

Assignee
Assign to
v1.1
Milestone
v1.1
Assign milestone
Time tracking
None
Due date
None
4
Labels
C++ Issues Design Issues Needs Attention Python Issues
Assign labels
  • View project labels
Reference: bob/bob#54