Skip to content

Unify C3 code - Part II #28

@Meow404

Description

@Meow404

Per lab meeting discussion on 2/20, we have the goal of continuing to mature the C3 repository into a stable, well-documented, and hardware-validated library. This issue summarizes the core aims of this transition, with the goal of completing the primary milestones by the end of the spring semester.

Repository Goals

The C3 repository continues to serve as the canonical home for the core C3 algorithm and LCS factory methods. The focus this semester is on consolidating fragmented code still living in dairlib, hardening the library for external adoption, and broadening its accessibility through improved documentation and framework flexibility.

Code Requirements

The same standards established last year remain in effect: all commits should be well-documented, unit tests should be created as appropriate, continuous integration must remain functional, all merges should include Python bindings and README updates, and code should be passed through Drake's clang autoformatter before merging.

Core Work Items

push_anything_dev

Plate-Balancing

User Tutorial and Documentation

Library Adoption

Progress on these subissues should be used to gauge completion toward the goals for unifying and maturing the C3 library.

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