Skip to content

hub.imu.settings() parameter order #167

@kai-morich

Description

@kai-morich

While trying out the fantastic import _imu_calibrate I looked at hub.imu.settings() output.

Setting parameters requires keywords, which is good as there are many parameters, but reading parameters returns a tuple without keywords.

I assumed the returned values match the order of the keywords listed at the documentation but it does not, e.g. heading_correction is the 6th parameter in the tuple, but the 3rd parameter in the documentation. As some sub-tuples are returned, it was possible to figure out the ordering, which I then also cross-checked withthe source code.

Might be better to return a dict when reading the settings.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions