link to this project on github

test-driving instructions

Too often, we feel, mechanical engineers design case-specific solutions to general problems: calculations are done, and their end result (after catalog-scouring) is a choice of one bolt. We shouldn't need to keep rewriting the same equations and re-scanning the same catalogs: we should tell the computer how to do the calculations only once, and then let the machine handle repetition.

how to use sprocket

This is a proof-of-concept: given requirements (specified in 'Requirements' on the left) and a overall optimization goal ('Cost'), these scripts will compare thousands of springs, along with options for motors and encoders, to reach an optimal design for a serial elastic actuator.

we need to know what you think

How could this be more useful? Where are we on the wrong track, and where on the right? Please email us.

P.S. - You can also use the 'add function' button to create your own scripts that work off of these data sources, or click on the names of existing scripts to change them.