A passive dynamic walker (PDW) is a biped robot that does not draw energy from any supply (ie. batteries, gasoline, etc) and only relies on the potential energy of walking down a decline. It fundamentally represents a walking human as seen from the side (sagittal view), while the upper body is represented as a larger hip mass.
This PDW is a so-called compass gait, or 2-link, walking model, in that there are only two effective linkages representing the walker's system. Essentially, this compass gait model is a inverted double-pendulum rotating about the ground contact.
While typical biped simulations rely on symmetrical leg properties such as mass and mass position, this PDW model allows the masses to be asymmetrical and to be distributed any way along the legs.
In addition in this model it is possible to change each foot shape such that the walker rolls over its feet in a variety different ways.
The result output of this simulation model yields raw data and visual plots that include:
- Kinetic, Potential, and Total Energy
- Ground Reaction Forces
- Leg Trajectory (Angular position, velocity, acceleration)
- Limit Cycle Plot
- Step Length Asymmetry'
- Collision event information
- Global and per-step data
- and more ....
- What is This Even Good For
- Compatibility
- Installation
- Simulation Options
- Walker Parameters
- Run
- Results
- Changing Variables over Multiple Runs
- Citing This Work
- Author
- Licence
There are a few reasons why you would be interested in this walking simulation model
- Presentation - It looks nice and would definitely look cool when showing off MATLAB animations.
- Walking Dynamics Research - If you are a researcher that is focused on walking dynamics analysis, this may be cool to mess with. The powerful thing about a computer simulation like this one is that you are able to quickly change walker parameters, and change them a lot, while finding interesting patterns and insights.
- Building a PDW - This simulation can be a great aid of picking and experimenting with a variety of different walker parameters to predict and verify the behavior of a physical PDW.
- Boredom - If you don't know what you are doing with your life and happen to have MATLAB around, this is 100% for you before you go get your stuff together and get off the couch.
This PDW simulaton model was created and tested on MATLAB R2017b and R2018b on a Windows 10 operating system. Although this program was created within those software versions and operating systems, it may work in other environments as well.
I would love to hear about usage on earlier or later MATLAB versions and other operating systems.
- Clone this repository to a computer with git.
- Use the ol' git machine to clone this repository to to a local directory
git clone https://github.com/ismet55555/PDW-Asym-2Link.git- Note that you don't have to use the scary terminal, you can use one of many git graphical interfaces such as GitHub Desktop
- Download this repository as a .zip file.
- Go to this repository's front page: https://github.com/ismet55555/PDW-Asym-2Link
- On the right, press the green "Clone or Download" button
- Select the "Download zip" option on the right.
- Once downloaded, extract the .zip file on your computer
All simulation based options are stored in the p struct variable in sim.
For example, p.sim.dt will hold the simulation time step.
These settings are for the general simulation behavior.
p.sim.dt- Time Step, dt (s) - The time between simulation iterations.p.sim.total_strides- Total Walker Strides - Specifies the goal of the walker. Unless the walker fails, at this number of strides the walker will stop walking.p.sim.g- Gravity Constant (m/s^2) - The gravity constant applied to the walker.p.sim.theta- Walking Ramp (rad) - The slope of the ramp on which the walker walks. Positive values is a decline, negative values is a incline.
The walker's leg angular positions at the beginning of the simulation are:
p.sim.init.q1- Stance Leg angular position (rad)p.sim.init.q2- Swing leg angular position (rad)
The angular velocities at the beginning of the simulation are:
p.sim.init.qd1- Stance Leg angular velocity (rad/s)p.sim.init.qd2- Swing leg angular velocity (rad/s)
The direction of these dynamics can be seein in the image below:
TIP: To find a set of stable initial conditions, you can iterate through different parameters, then pause the model at the beginning of the left stance phase, viewing stance and swing angular positions and velocities.
Each simulation output run can produce a variety of output plots and animations. The following options can be set to true if you would like to enable them. In order to turn them off, set them to false. The potential output plots are as follows.
p.sim.output.animation- When this is set, the animation will show the walker as it is being simulated in an animation.p.sim.output.energy- These plots will show the walker's kinetic, potential, and total energy over time. One plot for the entire simulation, and one per-step plot overlayed.
p.sim.output.force- These plots will show the walker's ground reaction forces in the direction along (parallel) the ramp,Rx, and perpendicular to the ramp,Ry. One plot for the entire simulation and one per-step plot overlayed.
p.sim.output.step_length- This plot shows the step length of each step. This is particularly useful when specifying asymmetric walker parameters.
p.sim.output.limit_cycle- This shows the limit cycle plot of the walker left and right leg. A limit cycle plot shows the relation ship of the leg's angular position (q) and angular velocity (qd)
p.sim.output.angle- This option will output the angle over time and per-step for the walker's legs (q)
p.sim.output.anglular_vel- This option will output the angular velocity over time and per-step for the walker's legs (qd)
p.sim.output.angular_accel- This option will output the angular acceleration over time and per-step for the walker's legs (qdd)
Note: If you would like to change any of the output plots to your need, you can do so by changing them in file \Simulation\Dependents\plot_results.m.
Note: If you are interested in an iteration of multiple simulation runs, it may be best to set all visual outputs to false.
Each walker simulation run will result in a variety of results.
p.sim.output.result_output_filename- The file in which the simulation data text will be stored. Each simulation run yields one row of information. This isDATA.txtby default, however can be changed. In general all information related to anything yielded by the simulation run will be stored in theresultsstruct variable (More information on that is explained below). A specified subset ofresultsis automatically stored in a specifiedDATA.txtfile. This file is made such that each row is one simulation run. You may add or remove the parameters saved into this file, by adjusting the file\Simulation\Dependents\save_parameters.mp.sim.output.save_plots- Saves any specified output plots. (Under construction for now, however you can manually save each plot using the commonSave as ...)p.sim.output.results_dir- The directory into which the data text file will be saved.
This passive dynamic walker simulation model has the ability to be defined asymmetrically in its masses and mass positions along the walker's legs. There are two masses per leg, while one single mass defines the hip. The two masses along each leg can be distributed in any way along the leg for each side.
The parameters are defined as show in the figure below:
This model is unique because it is possible to alter the foot shape (or roll over shape) of either foot. The foot shape for this model can be defined as a continuous and variable radius around the walker's ankle as:
radiusfoot = angle*A + B
In this equation angle is the angle around the ankle in radians, A is the change constant (how the foot shape changes), and B is the offset constant.
In addition it is possible to offset the ankle along the top of the foot with a constant d as shown in the figure below.
To help visualize a foot shape before applying it to the simulation model, you can use the foot_shape_viewer.m utility located in the utility directory. That is, simply adjust the parameters outlined in the foot_shape_viewer.m and run it.
There is not much to write in this section. To fire up the damn thang, just simply run RUN.m.
When you do run the script the command window should look like something like this for a quick 4-stride successful walker simulation run:
[18:59:26.188][INFO ] : Simulation started
[18:59:26.250][INFO ] : Number of strides: 4
[18:59:26.291][INFO ] : Starting walker step sequence ...
[18:59:26.302][INFO ] : Stride: 1 - Step: 1 - Left Stance
[18:59:29.611][INFO ] : Stride: 1 - Step: 2 - Right Stance
[18:59:33.124][INFO ] : Stride: 2 - Step: 3 - Left Stance
[18:59:33.616][INFO ] : Stride: 2 - Step: 4 - Right Stance
[18:59:33.933][INFO ] : Stride: 3 - Step: 5 - Left Stance
[18:59:34.231][INFO ] : Stride: 3 - Step: 6 - Right Stance
[18:59:34.553][INFO ] : Stride: 4 - Step: 7 - Left Stance
[18:59:34.984][INFO ] : Stride: 4 - Step: 8 - Right Stance
[18:59:35.371][INFO ] : Simulation complete
[18:59:35.373][INFO ] : Simulation duration: 9.19s
[18:59:35.375][INFO ] : Plotting any specified plots ...
[18:59:38.158][INFO ] : Saving simulation data to file ...
[18:59:38.225][INFO ] : Simulation run complete
This program utilizes a custom MATLAB logging add-on. Essentially, this logger allows you to inspect what the program is doing, while giving you some basic troubleshooting tools. If you are interested in how to utilize these tools, visit the logger's page. In order to turn on any Debug level logging statements, in RUN.m, set log.default_level = 1
Each time this simulation model runs, it produces a diverse and large set of organized data. This data is saved and available in the results struct variable. An example output of the results variable can be viewed here.
There are currently 7 different results data categories:
- sim: General information about the simulation run such as time, number of steps, success/fail, etc
- motion: Angular position, velocity, and acceleration data for the walker.
- energy: Kinetic, potential, and total energy of the walker.
- force: Ground reaction forces parallel and perpendicular to the walking surface.
- collision: Information of all walker heel collision events during the simulation.
- other: Other un-categorized metrics such as hip height, and step length.
- fail: Information about any walker failure, if failure occurs.
Please review the complete list of the results struct variable here.
Note that often times the data is pre-processed as follows:
- Divided up into left and right leg
- For convenience the data has supplemental basic statistics calculated such as mean, meadian, min, max
- Per step data is interpolated for other elected post-processing steps such as averaging per step data.
To help visualize the results struct variable, you can use the struct_map.m utility located in the utility directory. That is, simply type struct_map(results).
In a lot of research and exploration related situations, you may be wanting to vary specific walker parameters over multiple runs. For example, you may want to see the effects on walker dynamics of moving a leg mass up the leg gradually with each simulation run. Fundementally, currently to accomplish this, you can alter the specific variable and repeatably executing the following code block that is located in RUN.m. If you are running multiple and unsupervised runs of the simulation model, it is advised that all plotting and animation options are set to false (see above).
%Start Simulation Timer
tic
log.info('Simulation started')
log.info(sprintf('Number of strides: %i', p.sim.total_strides))
%Calling Walker_Control function to start simulation
[p, results] = Walker_Control(p);
% Log how long it took to run the single simulation run
results.sim.run_time = toc;
log.info('Simulation complete')
log.info(sprintf('Simulation duration: %4.2fs', results.sim.run_time))
% Plot specified result plots
log.info('Plotting any specified plots ...');
plot_results(p, results)
%Saving Simulation Data
log.info('Saving simulation data to file ...');
save_parameters(p, results)
log.info('Simulation run complete')In order to change one variable gradually over a series of simulation runs, you may want to encompass the above block in a for loop, while changing parameters in the p struct variable at each iteration. If more than one variable is to be changed over multiple simulation, you may want to use nested for loops.
However, for serious, heavy duty work, running a vast number of iterations over a many different variables, you may want to explore MATLAB's Parallel Processing Toolbox , using a parfor loop. A simple example of a parfor loop can be seen here.
If you are using this work in any publication of any sort, please be kind to cite and acknowledge this repo and myself.
Handzic, I. (n.d.). Passive Dynamic Walker (PDW) Simulation Model, Compass Gait, Asymmetric Variable Foot Shape Radius. Retrieved <MONTH NAME> <DAY NUMBER>, <YEAR NUMBER>, from https://github.com/ismet55555/PDW-Asym-2Link
Handzic, Ismet. “Passive Dynamic Walker (PDW) Simulation Model, Compass Gait, Asymmetric Variable Foot Shape Radius.” Logger, GitHub, https://github.com/ismet55555/PDW-Asym-2Link.
Handzic, Ismet. "Passive Dynamic Walker (PDW) Simulation Model, Compass Gait, Asymmetric Variable Foot Shape Radius." Passive Dynamic Walker Compass Gait Variable Foot Simulation Model. June 6, 2020. Accessed <YEAR NUMBER>. https://github.com/ismet55555/PDW-Asym-2Link.
@misc{handzic, title={Passive Dynamic Walker (PDW) Simulation Model, Compass Gait, Asymmetric Variable Foot Shape Radius}, url={https://github.com/ismet55555/PDW-Asym-2Link}, journal={Logger}, publisher={GitHub}, author={Handzic, Ismet}}
Ismet Handžić - GitHub: @ismet55555
This project is licensed under the Apache 2.0 License - Please see the LICENSE file for details.