Code Monkey home page Code Monkey logo

wb-team-issues's People

Contributors

jeljaik avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar

wb-team-issues's Issues

TorqueBalancing with QP for forces

After #21 in WBI-Toolbox is finished and tested we have to port it to C++.
I think the real-robot testing of torque balancing can be postponed after this issue, so we can save some (tuning) time.

@barrelback @DanielePucci

Test ICP-based open loop walking on iCub

cc @luca-fiorio @francesco-romano

After successful open loop simulation on the real robot we can proceed to test things on the real platform. The steps to follow are described next.

  • "Fine" calibration of the robot.
  • PID tuning of leg joints 0, 1, 2 and 5 mainly.
  • Playback with robot in the air.
  • Playback with robot on the floor.
  • Further tuning (?)

Modify WBI-T according to the new ID-System

  • Robot number of DOF specified at configuration time via the ResourceFinder
  • Proper abortion when initialization isn't finished correctly. (The fix worked perfectly in this branch @traversaro Thanks!!)
  • icubWholeBody* => yarpWholeBody*
  • wbi::LocalId => wbi::wbiId
  • Write a yarpWholeBodyInterfaceTest module for the branch new_wbi_ID
    robotology-legacy/codyco-modules@aa68122
  • Test COMPoseTesting works correctly.
  • Stopping the simulation is not finishing correctly as it makes Matlab crash right after maxJntLimits deleted.
  • Perform single tests for each block in the Toolbox:
    • jointAngles
    • jointVelocities
    • forwardKinematics
    • jacobian
    • ⚠️ set velocities
    • ⚠️ set angles
    • set torques
    • computeh
    • massMatrix
    • dJdq
    • jointAccelerations
    • jointTorques
    • inverseDynamics
    • jointLimits
    • angularMomentum
    • ⚠️ EEWrench @traversaro Please let me know when this part is ready in yarpWholeBodyInterface
    • setWorldRefFrame
    • param Forward Kinematics
    • param Jacobians
    • param dJdq
  • Remove this DEBUG message: [DEBUG] yarpWholeBodyStates::getEstimates: called getEstimates ESTIMATE_JOINT_POS
  • Test WBI-Toolbox with different robots, e.g. COMAN, iCubHeidelberg01
    • The variable ROBOT_DOF is necessary also outside the c++ code, i.e. in
      the MATLAB environment for those blocks that have null inputs at the most inner level. The config file for each robot must be read somehow by MATLAB as well... 😩 For now let the user specify ROBOT_DOF from command line, along with robotName, Ts and localName
    • Change all blocks of the toolbox so that they use the MATLAB variable ROBOT_DOF.
    • Get COMPoseTest working with iCubHeidelberg01 @traversaro yayyy!! 😀
    • Get COMPoseTest working with COMAN
      • Write configuration file for COMAN
  • Change the logic of the MATLAB variables needed for simulation: robotName, 'localName' and 'Ts'. From now on, robotName should correspond to the usual robot name variable in iCub modules, i.e. either icub or icubGazeboSim, while localName is the prefix of the ports opened by the WBI. robotology-playground/WBI-Toolbox@78b9608
    Besides this change, remember that the robotName and localName input by the user from MATLAB's command line overwrites the default ones from configuration file.
  • Update all blocks from the toolbox to take into account ROBOT_DOF robotology-playground/WBI-Toolbox@78b9608
  • Update README.md with migration instructions. https://github.com/robotology-playground/WBI-Toolbox/blob/new_wbi_ID/README.md
  • Test yarpWholeBodyInterfaceIcubTest with COMAN
  • ⚠️ Get WBI-Toolbox working with the double pendulum model.

Pending Improvementes

  • ⚠️ Test Torque Balancing Demo with the WBI-Toolbox in branch new_wbi_ID
  • ⚠️ Make interface configuration happen only once by the first block that attempts to do so.
  • ⚠️ Parse configuration files in MATLAB to create list of possible links from param jacobians, etc.
  • ⚠️ Perform properly block input size checking. e.g. If input to a block does not have the proper size, Matlab is simply crashing with a hard to diagnose error message.

Simulink Synchronization

The block ySynchronizer in the WBI-Toolbox is in charge of controlling the simulation time of Gazebo given a desired simulation period.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.