Let's Play Peekaboo

Unveiling the concept of my new method for the Environment Model class.

Posted by Nelson Raphael November 25th, 2017

Under Construction...literally because the function is still not finished yet

In order to make progress in the project the team has asked for a function to identify where certain links of the snake are located in relation to certain areas of the environment. When approaching problems that require you to code the solution it is good to break it into different parts.

So when we look at this problem we can break it into the following parts. If we want it to identiy where certain links of the snake are that will be using the foward kinematics of the snake in realtion to the environment. A method to calculate the foward kinematics of the snake given the angles read from the motors from the dynamixel, the location of the tailframe, and the link lengths passed in during the snake model class initialization. Thus not much needs to be done there.

They also what it in relation to a certain area of the environment. So we know this part will be an environment model method. There already exists a method that takes in the model and plots it. So if we just want a certain area of the environment the same function can be mimiced but also constrained to the measurements of the region.

Lastly if you want certain links of the snake in relation to certain areas of the environment then you could pick the corresponding x and y value from the foward kinematics potion and subtract that from the region you are observing. Since it is better to make the function as user friendly as possible we could have the values stored in a table with each column corresponding to a specific motor link and each row corresponding to a specific point or obstacle in the region. Then if you just want a specific region or motor link you can index accordingly.

Leaving the drawing board and handling implementation

So I have created the structure for the environment method that just grabs a particular region, hence its name being regionGrabber. However, while I was doing a debug I realized the conversion from pixel to length (in mm) is incorrect at least for the x-direction. For MATLAB if you do not have the corresponding x value for each y value it is unable to plot. Once I work through that conversion error then this portion will function.

The motorLinkGrabber will just require the snake kinematics but to output it into a matrix, which is not difficult at all.

Placeholder text by Nelson R.. Photographs by NASA on The Commons.