{"id":207,"date":"2012-03-07T13:10:05","date_gmt":"2012-03-07T21:10:05","guid":{"rendered":"http:\/\/research.engineering.ucdavis.edu\/biosport\/?p=207"},"modified":"2014-06-19T12:36:54","modified_gmt":"2014-06-19T20:36:54","slug":"pin-pin-collision-detection-and-response","status":"publish","type":"post","link":"https:\/\/research.engineering.ucdavis.edu\/biosport\/pin-pin-collision-detection-and-response\/","title":{"rendered":"Pin-pin collision detection and response"},"content":{"rendered":"

by Andrew Kickertz<\/p>\n

Collision detection via meshes, and rough calculation of post-impact velocities.<\/p>\n

\n
\n

Over the past couple weeks I’ve been developing a method to detect collisions between pins, modeling them as meshes. \u00a0I’m also thinking about describing the pins as parametric surfaces, but that’s another can of worms. \u00a0The radius of the pin is defined at 15 heights as specified by the USBC:<\/p>\n

\n
\"USBC<\/a><\/dt>\n
As specified in the USBC 2010 Equipment specifications and certification manual<\/dd>\n<\/dl>\n

These radii, heights, and the number of desired lines of longitude are fed into a custom cylinder-mesh-generation function:<\/p>\n

function [x y z] = mycylinder(r,zIn,nLong)\r\nfor i=1:length(r)\r\n    for j=0:nLong\r\n        x(i,j+1) = r(i)*cos(2*pi*j\/nLong);\r\n        y(i,j+1) = r(i)*sin(2*pi*j\/nLong);\r\n        z(i,j+1) = zIn(i);\r\n    end\u00a0\r\nend\u00a0<\/pre>\n
For example, here is a pin mesh composed of the 15 prescribed radii and heights and 25 lines of longitude:<\/p>\n
\n
PinMesh-eps-converted-to<\/a><\/dt>\n
<\/dt>\n
Rainbow colored pin mesh with 15 radii and heights, and 25 lines of longitude.<\/dd>\n<\/dl>\n
Collision is deemed to have occurred if the distance between any node on 1 pin is sufficiently close to any node on another pin:<\/p>\n
distance(i,j) = dx^2 + dy^2 + dz^2;<\/pre>\n
Here is an example of collision detection for 2 roughly-meshed pins:<\/p>\n