{"id":1971,"date":"2014-10-16T19:08:20","date_gmt":"2014-10-17T02:08:20","guid":{"rendered":"http:\/\/bestperformancegroup.com\/?page_id=1971"},"modified":"2015-06-30T12:45:54","modified_gmt":"2015-06-30T19:45:54","slug":"body-angular-rate-calculation","status":"publish","type":"page","link":"http:\/\/bestperformancegroup.com\/?page_id=1971","title":{"rendered":"Local (Body) Angular Rate to Euler Rate Transformation"},"content":{"rendered":"

McGhee et al. 2000<\/a> presented a non-orthogonal transformation that links body rate angular velocity to Euler angle rate. \u00a0This transformation matrix that allows one to specify angular velocities in local (body) axes from Euler angle rates calculated in global axes. The formulation is given in Appendix A of the linked paper, and is also copied below in figure form. \u00a0This is a very powerful transformation matrix that can be used to transform Euler angle rates into body angular rates, which makes direct comparison of angular velocities measured using any Euler\/Cardan sequence. \u00a0A working example is presented here.<\/p>\n

At Callaway Golf, I ran multi-sensor swing studies (MS3) using multiple advanced measurement technologies for Product Player Matching initiatives. \u00a0The projects that I was in charge of included Player Profiling<\/a>, Digital Human Modeling<\/a>, and Club Fitting<\/a>. \u00a0A central component to these 3 projects was an inertial measurement unit (IMU) on-board diagnostic (OBD) shaft-based data acquisition system<\/a>, that would link all 3 projects together. \u00a0One of the more difficult aspects of the project was verifying angular velocity measurements between the modular IMU sensor shuttle<\/a>\u00a0and motion capture measurements collected in the Player Performance Bay which were used as inputs to the digital human modeling efforts.<\/p>\n

In the Player Performance Bay, we used an active optoelectronic motion capture system to record player swing data and also used instrumented clubs to record club motion. \u00a0An example of the shaft marker prong used on tested clubs is shown below. \u00a0Inside the butt end of the shaft of the club was the modular IMU sensor shuttle<\/a>, also shown below.<\/p>\n

\"optotrakclub\"<\/a>\"obd\"<\/a><\/p>\n

In order to synergistically use the data from the 2 very different systems, we needed to be able to get the data outputs into a common coordinate system. \u00a0The modular IMU sensor shuttle<\/a>\u00a0directly measures accelerations and angular rates relative to the local (body) axes defined by the internal board configuration, which was placed inside the shaft of the club. An orientation system had to be used to ensure that the modular shuttles could be inserted the same in every club relative the club head. \u00a0Similarly, the shaft marker prong was installed on the tested shaft, and an orientation process was used to align the marker and define club axes relative to the club head. \u00a0There was actually a third coordinate system used in these tests with markers placed on the club head to define club head axes as well, but that is not necessary for this discussion. \u00a0\"optotrakclubcs\"<\/a><\/p>\n

As we knew the axes definitions for both the modular IMU sensor shuttle<\/a>\u00a0and the shaft marker prong for the instrumented club, it was possible to compare the angular rate measurements between the two systems using the non-orthogonal\u00a0body rate to Euler rate transformation matrix given below. \u00a0The IMU club used angular rate sensors that were operating well beyond their technical specs; the sensors were individually bench top tested to calibrate them. \u00a0It was desired to compare the two systems directly to ensure dynamic operation of the out-of-spec sensors. \u00a0This was done for each modular shuttle to verify the calibrated dynamic outputs.<\/p>\n

Due to confidentiality concerns, I can not show those outputs here. \u00a0However, we had undertaken a very similar test with SmartSwing<\/a> instrumented clubs. \u00a0Their board layout is shown below. \u00a0A few graphs from\u00a0that test were presented at a conference so can be displayed here. \u00a0The main reason for testing the SmartSwing clubs was to evaluate the dynamic response of the accelerometers and the angular rate sensors. \u00a0As in our internal modular IMU sensor shuttle<\/a>\u00a0design, there were no available sensors at that time that had the necessary technical specifications to dynamically measure the angular rates found in the golf swing of a professional golfer. \u00a0We wanted to test the dynamic response of the SmartSwing club as we had done with our own IMU clubs to evaluate dynamic operation.<\/p>\n

\"smartswing\"<\/a><\/p>\n

Below are plots that show the SmartSwing outputs plotted directly against the motion capture outputs that were transformed into the local SmartSwing axes using the transformation matrix described below. \u00a0As one can see, we obtained very good dynamic results comparing the two systems. \u00a0There were some instances where the accelerometers clipped as was expected given their specs. \u00a0There were also some irregularities with the angular rate outputs near impact at the maximum values. \u00a0One other interesting note in these plots is the fact that the motion capture sampling rate is much lower, so there were some instances where the absolute peak angular rate is missed with the motion capture system because the sampling rate was not high enough for this very high-speed motion. \u00a0The instrumented club sampled at 1000 Hz and did not suffer from this problem. \u00a0This transformation technique was very powerful and allowed us to directly compare results from two entirely different measurement systems in a local body coordinate system.<\/p>\n

\"imuclub4\"<\/a><\/p>\n

\"bodyimu2\"<\/a><\/p>\n

\"bodyimu1\"<\/a><\/p>\n

\u00a0Reference:<\/strong><\/span><\/p>\n

McGhee et al. 2000<\/a>\u00a0Rigid Body Dynamics, Inertial Reference Frames, and Graphics Coordinate Systems: A Resolution of Conflicting Conventions and Terminology<\/strong><\/p>\n

\"mcgheenpsmoves\"<\/a><\/p>\n

Share this:<\/h3>