nicklesterrides

@Dougal-SC: That is an easy way to do it, and a valid way to test one aspect of the component, but doesn't necessarily reflect how it applies to a real-world application and the whole system. There's a time and place for controlled environment testing and real-world testing in my opinion, as well as correlation between the two.

@CyclingAbout: It's a combination of stiffness/compliance in 3 different axes, but also the amount of energy transferred through the suspension chassis in those 3 axes. This is affected by rider style, terrain inputs, system weight (sprung, unsprung, rider and bike). So the Compliance Profile code I've written is designed to be used with the same rider on the same bike in order to understand how component changes (e.g. carbon wheels vs aluminium wheels) and component modifications (e.g. spoke tensions, spoke coating, spoke dimensions) can be used to deliver the configuration best optimised for that rider, on that bike, at that specific track. Track evolution plays a part in this, but this can usually be accommodated for by making changes in suspension setup which will have been optimised as a result of running the correct compliance profile. Its a work in progress though.

I don't work with a university, I'm not sure how good I would be as a teacher or lecturer. I do have a Patreon channel where I share DAQ use cases, tips, how to analyse the data etc. I will be more active on there in the future too.