You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Per lab meeting discussion on 1/9, we have to goal of unifying the fragmented C3 code split across branches in dairlib. This issue summarizes the core aim of this transition, with the aim of completion of steps 1-3 by the end of the spring semester.
Repository structure
C3 Repository (this)
This repository will house the core C3 algorithm and the LCS factory methods which construct linear complementarity systems from a URDF. This will require dependency on Drake for RigidBodyDynamics, URDF parsing, and for Drake's MathematicalProgram code.
This repository will be as clean and lightweight as possible, suitable for public use without requiring everything in dairlib.
Dairlib
Most of the C3-related code in dairlib will ultimately end up in the C3 repository. Examples in dairlib which require the construction of abstractions and simple models (and the corresponding use of the OSC) will continue to existin dairlib, which will bring C3 in as a dependency.
Code requirements
All commits should be well-documented
Unit tests should be created as appropriate
This repository will require functioning continuous integration
All merges should include Python bindings and README updates
Code should be passed through Drake's clang autoformatter before merging
Per lab meeting discussion on 1/9, we have to goal of unifying the fragmented C3 code split across branches in dairlib. This issue summarizes the core aim of this transition, with the aim of completion of steps 1-3 by the end of the spring semester.
Repository structure
C3 Repository (this)
This repository will house the core C3 algorithm and the LCS factory methods which construct linear complementarity systems from a URDF. This will require dependency on Drake for RigidBodyDynamics, URDF parsing, and for Drake's MathematicalProgram code.
This repository will be as clean and lightweight as possible, suitable for public use without requiring everything in dairlib.
Dairlib
Most of the C3-related code in dairlib will ultimately end up in the C3 repository. Examples in dairlib which require the construction of abstractions and simple models (and the corresponding use of the OSC) will continue to existin dairlib, which will bring C3 in as a dependency.
Code requirements
Core Commit Sequence
Next steps
Following the three primary pull requests above, next steps include
The text was updated successfully, but these errors were encountered: