19 Oct

A more integrated interface

Gopi Suresh Robot Compiler

This past Friday, Christian Prathyush and I met with some of the newer members of our lab who are interested in working on RoCo. Before we completely move to a new project, we got together to discuss what RoCo's status would be by then. One of the topics discussed was the fairly fragmented nature of the RoCo interface. Currently, the interface allows users to create new tabs, which can be used to create or modify mechanical components, base code components, or composite components. This means that the user is able to work on many different parts of the robot concurrently.

While this is helpful to the user, it was decided that it would be more intuitive if the three interfaces were to be connected at a more fundamental level. For example, currently, if a user were creating a robot with the interface and decided to add a servo to the composite component interface this action would have no significance in the interface's understanding of the robot as a whole. If a robot has a servo, in order for the design that RoCo outputs to make sense, the robot must have a mount for the servo as well. However, as the interface is right now, the servo would appear in the composite component interface but the servo mount would not appear in a mechanical interface.

This raises some more issues. If the user is working on multiple mechanical components at the same time, how would the interface know which tab to add the servo mount to? Similarly, if a user added a servo mount to a mechanical component, which corresponding composite component interface would have a servo motor added to it? This scenario is even further complicated if the user is creating multiple robots simultaneously using the interface.

I spent this week thinking about these problems and decided to tackle this issue in the simplest manner. Whenever a component is added to any interface, if the component has both a code/electrical composable as well as a mechanical composable, a dialog box should pop up, asking the user which tab to include the complementing component to. This way, the user can ensure that there will be no missing pieces when creating the robot.

This modification will require a nontrivial amount of work since currently, the RoCo interface has no idea which components have which composables. I have started making provisions for this in the source code and have begun outlining a design to add this feature but may choose to hand this project over to someone else, after taking time into consideration.

Next Post Previous Post

Search

Popular Tags

foray origami robots blimp ducky vr edg SLAM computer vision computational design roco slam Origami rocolib arduino RoCo design Robot Compiler simulation Motion Planning autonomy edg-model create; kalman filter; mesh reinforcement learning; multi-agent; mean-field; logics imu contacts mesh network motors esp32 friction networking tank dynamics pushing auxetic esp now machine learning multi-agent visual processing communication wireless control i2c webapp ROCO pcbs structure path planning computer skill cars openmv Robotica reinforcement learning power consumption modeling origami dataset test visual odometry surface structure dash port-arrays Battery DARPA motor gondola machine vision controller semantic paper auxetics infrastructure feedback gestural interface frequency diversity mixed reality robot Consensus bistable auxetic unit cell gestural intuition crawler darpa; create; logic create; kalman filter; EM; structures Foray network open house propeller lidar sensors apriltags 433mhz optimization Quantum Information 4-wheeled FORAY perception control environmental design refactoring icra2021 radio Kullback-Leibler Divergence crazyflie DER Auxetics lasercutter distributed optimization blynk gate von Mises Fisher Distribution pushing problem experiment results or nodemcu offline reinforcement learning exam research proposal conference object detection simulink webots project management modeling contacts tutorial thrust IR motor configuration integration test localization UAV legs joystick altimeter decentralized ros2 balloon test painlessmesh mesh networking swarm vision processing arnhold matlab fusionbot RL arduino nano multi-agent path planning gazebo PCB rviz2 nonholonomic systems Integrated Demo reinforcement learning; slam; paper review vision Short Post trajectory optimization edg-examples serial monitor python Model-Free Machine Learning Q-Learning rssi controls feedback-controlled grant writing system ID multirobot system signal strength quasi-static pushing marginal cost pricing in-situ design IROS neural network hot plates cell reinforcement learning; multi-agent; mean-field; game theory; mean field; reinforcement learning current reinforcement learning; multi-agent; Xbee Zigbee robot compiler origami robot deployment spi dynamic modeling rhino boat literature review multipack buoyancy equations contact surp paper review Writing motorized boats throughput range surfaces ML reservoir computing multi-agent path finding solar cars detectionrate distance shape color edg-ide pain Characterization tool concept surface contact liquid crystal elastomer conferences release peripheral device differential keyboard swarm control car von Mises-Fisher von Mises Fisher port-array quasi-static modeling Kalman Filter Zero Elastic Energy modes Liquid Crystal Elastomers Discrete Elastic Rods Consensus Algorithms power pivoting Learning 3D-CHESS; kinematic_model elastic polymers 2.4 GHz 433 MHz creative Computer skill internal misc edg-refactoring 433 ceres debug coriolis force structured field dynamic model proposal wtf deep learning interpolation wireless signal strength reinforcement learning; multi-agent; decentralized reinforcement learning; multi-agent; mean-field; stationary demo video flytrap papers steering plastic multi-object tracking pvdf prelab actuation von Mises Distribution Barycenter Multi-Agent Systems integration flapping color_segmentation center of friction lab_data result segmentation on multiple object and centers finding competition ZMP buoyancy current sensor multiple blimps battery pid defender Synthesizable Radio integrated system 3d printing catching mechanism kalman filter barometer detection balloon slam; flowchart; depth estimation grid chiral square unit cell state space multi-robot pressure distribution model prediction thrust configuration kalman filter; ESP32 paper cutter COVID 19 manipulation fabrication code hardware offline Rl firmware protobuf #activecapturingmechanism #claw ensemble methods Bayesian networks 3D-CHESS; kalman filter bootstrapping model-based RL boxboat tracking lift force cad nylon scenic adaptive control motor driver MIMO communications Euler-Bernoulli beam newton's method spring-mass submission kalman filtering point cloud 2.4ghz latency der codesign sma-based actuator presentations machine training cameras preliminary exam multiple devices inkscape material delta tolling semantic segmentation instance segmentation pdms silicone optitrack multirobot solidworks ICLR design tool board design HDL pixracer pixhawk ardupilot flight controller regression fly test motor distribution Python DNN ICRA game theory ICML guassian processes probabilistic neural networks graph generators MBRL ide batch learning ros sensor fusion von Mises-Fisher Distributions edg-compiler Bessel functions iot