Skip to content

Adding registration/RMS error for cartesian poses #8

Open
@adeguet1

Description

@adeguet1

Most tracking systems (optical, magnetic...) provide some kind of information to help determine how reliable the pose estimation is. For example, Atracsys and NDi provide a single floating point RMS error. The meaning and scale of these numbers is likely vendor/implementation dependent so it's hard to standardize them. As usual, the two questions are what to provide and how:

  • What:
    • At least the raw number provided by the device
    • Maybe a reference number to allow the user to determine what is good or bad. Alternatively, we could add an enum with predefined values: good, marginal, bad, not_found
  • How:

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions