Thanks, but I'm looking for something a bit more specific. See below.
In the first place sorry for letting you without a high quality answer - my bad, thought that provided level of details should be enough in that case. I will try to elaborate more details below
I appreciate you are asking for those details - we are quite similar in that field, I must also understand all math and algorithms idea behind before I apply it
This way we might even engage our competitors to introduce similar measures or present and explain their approach to the same problems
Speed:
So is this simply a measure of the variance of speed, or is there some other measure that is incorporated?
It is not that simple. We correlate speed with skis vibrations to asses if you have still good control of them. Is it enough right now?
If not I will just mention that to analyze vibrations you can apply various signal analysis tools, i.e. frequency analysis with Fourier, Wavelets or DTW to mention in the first place. This is where we enter our secret sauce, where we have developed custom mixture of those and some other ones
Engagement:
This doesn't really describe what the measure is. Is this an estimate of carving or edge angle or what? It might be interesting if there was either, e.g. a measure of "slippage" of the ski across it base (edge engagement) or a measure of edge angle and the rate of change of it. But right now, I don't understand the specifics of what your measure is or how I'd use it.
You are right - after a second read a person who has never used the system could not get what it measures. We have a distribution of slope ratings according to different skiing levels. Knowing at which level you are we can say if that slope was hard or not. Additionally, knowing your style (long/short turns) we have a similar model for turns pace. A mixture of them allows us to asses your overall engagement - that is if this run was a piece of cake for you (far below your true capabilities) or it was challenging for you, pushing your skills to an edge. It has nothing to do here with quality or dynamics of your turns, it`s just a measure of your altitude to that run - you wanted to ski harder or just relax.
Turn IQ:
As I understand it, you have three sensors; one on each ski and one on the chest. How do you determine hip angulation versus knee angulation? I presume body balance is fore/aft pressure control, but how do you determine that given the variation in anatomy of weight distribution/femur and tibia length? And is the raw data, or sub-aggregations of your overall metric available to use in coaching? I'm not sure I'd find a "Turn IQ" aggregate metric to be useful, but might want to look at fore/aft or foot to foot pressure by phase of the turn.
For now we have two solutions - simple and complex one. Simple, seen in application right now, assumes that hip angulation is based on angle between chest and skis edge angle. Second one, at experimental stage, requires more high quality reference data as we build up an kinematic model of skier driven with data from our sensors. Unfortunately, amount of work to do with other features, which seems to be more interesting for users, forces us to move slower with that than we would like to :/ But this is definitely the direction we want to go with this task in the nearest future.
As for the body balance question: currently we present only an average statistics of a complete turn for body balance. Having said that, 48L/52R means that on average your body balance was 48% on the left ski and 52% on the right ski. We neglect the specificity in construction of individual bodies and their asymmetries in mass distribution. This is possible to take into account, but would require lots of advanced measurements before you would be able to start using the system. For some users this might be to difficult to perform or even impossible, as this is really pro approach requiring high precision and sophisticated knowledge. 3D scanner might be a solution here, but still - how many of us have access to such devices and would be able to provide required processed data as input to a system similar to Snowcookie? This is definitely a professional, super high performance approach which coaches have even not dreamed about I think.
But getting back to the question. It is possible to provide body balance in time (turn phases) instead of an aggregate for the whole turn and if enough users would ask for this we would have to think how and were present it in app. We already have this data, we are just not presenting it directly.
I did not get what you meant if our raw data or sub-aggregations are available to use in coaching. Could you explain this to me?
In general Turn IQ is a complete score of your entire turning. Looking at it you should know if turning has improved or not. Getting deeper you can observe it`s "ingredients" - edge angles, edge control, body balance and many others. This is just an aggregate and simplification. Is it useful for you? I would still say yes, but I have to agree that if you are working on a particular parameter of your turning it forces you right now to go through an additional level of abstraction that might cover what you were really looking for. Solution for that might be dedicated training program where you could define what you want to improve and there observe only those parameters. Something worth considering from our perspective for advanced and aware users.
Style:
How do you measure "fluency" of a turn? Do you have a way to measure pressure? The location of maximum pressure in the turn might be pretty useful as well as measuring foot to foot pressure. And I presume "correct" is from training a model to some metrics collected by some group of skiers. What parameters are you training the model to?
The fluency is calculated only for consecutive turns aggregated together as a streaks. For each streak we consider turn types, their quality, speed fluctuations between turns and transition times in between. The better the turns, the smaller speed changes, the smoother transitions and motion dynamics, the stable edge angles the better fluency you have. Hope this is enough as I am afraid I can not continue to much further as we will be touching some critical details, which we do not want to expose right now. But you can always ask, maybe I could explain it in a different way though?
As for the question about pressure - we do not measure pressure directly as Carv does, but we can do it indirectly, based on ski vibration analysis, as mentioned in Speed calculations and used for body balance in turns description too.
About turn correctness - you are right. There are several factors to assume turn to be correct. I will focus on carving turns only, as this is what we all want to perform mostly. We use turn initiation timings data (chest/skis, inner/outer ski delays), body balance, and some other turn quality parameters. Some aspects like transition time or turn initiation were already discussed here in this thread with other users.
Stance:
There are a lot of issues in measuring stance. Dorsiflexion, knee flexion, and hip flexion being one set, along with rotational alignment between the shoulders, pelvis, knees, and feet. What precisely is being measured?
The answer here is exactly the same as for hip angulation as this is almost the same model, but focused on different angles. We care here mainly for leaning forward/backward but as meantioned already we put additional speed layer on top of that as a weighting factor.
Stamina:
To translate time moving (presumably on snow) versus time not moving plus lift rides into an index still requires some sort of scoring. This metric is less interesting to me, but it still warrants some sort of description of how it is constructed.
To be honest I don`t know how to explain it even simpler. For every run you have some sort of time buffer for pauses/breaks. When you use all of it we start to penalize you for additional pause time. If some time has left you will get 100%. Is it clear right now? Basically it is all about spending time on skiing actively as much as possible.
Hope I have now fulfilled your demands about different system details
If not, I would be happy to continue where it is required and possible.
Mati