CP testing template with IMU hooks

I built a streamlined 3‑min + 12‑min protocol and worksheet to estimate CP/W′, with auto flags for pacing drift >3% and fields to ingest tibial acceleration from RunScribe/Shimmer so we can map impact peaks to W′ balance. Happy to share the file; has anyone landed on practical cutoffs for peak tibial accel (e.g., >6 g vs >8 g) during threshold bouts on a 1% grade treadmill?

‌⁠‍⁠​‍​‍‌⁠‌​​‍​‍​⁠‍‍​‍​‍‌⁠​⁠‌⁠​​‌‍⁠⁠‌⁠​‍‌⁠‌​‌⁠​⁠‌‍⁠‌‌‍‌‌‌‍‌​‌‍‍‌‌‍​⁠‌‍‍‌‌‍⁠‍‌‍‌‌​‍​‍​‍⁠​​‍​‍‌‍‍⁠​‍​‍​⁠‍‍​‍​‍‌‍⁠‍‌‍‌‌‌⁠‌⁠‌‌⁠⁠‌⁠‌​‌‍⁠⁠‌⁠​​‌‍‍‌‌‍​⁠​‍​‍​‍⁠​​‍​‍‌‍‍‌‌‍‌​​‍​‍​⁠‍‍​‍​‍‌‍⁠‍‌‍‌‌‌⁠‌⁠​‍​‍​‍⁠​​‍​‍‌‍‌​​‍​‍​⁠‍‍​‍​‍​⁠​‍​⁠​​​⁠​‍​⁠‌‌​⁠​‌​⁠​​​⁠​‍​⁠‌‌​‍​‍​‍⁠​​‍​‍‌‍‍​​‍​‍​⁠‍‍​‍​‍‌​​‍‌​⁠‌‌⁠‍‍‌‌​‌‌​⁠​‌​‌​‌​‍⁠‌​‍​‌‌⁠⁠‌​‍‌‌‍‌​​⁠‌⁠‌​⁠‍‌⁠‍‌​⁠‌​​⁠​‌​‍​‍‌⁠⁠‌

On 1% treadmill, I flag heel strikers “>8 g”, forefoot “>10 g”; belt stiffness skews.

‌⁠‍⁠​‍​‍‌⁠‌​​‍​‍​⁠‍‍​‍​‍‌⁠​⁠‌⁠​​‌‍⁠⁠‌⁠​‍‌⁠‌​‌⁠​⁠‌‍⁠‌‌‍‌‌‌‍‌​‌‍‍‌‌‍​⁠‌‍‍‌‌‍⁠‍‌‍‌‌​‍​‍​‍⁠​​‍​‍‌‍‍⁠​‍​‍​⁠‍‍​‍​‍‌⁠​‍‌‍‌‌‌⁠​​‌‍⁠​‌⁠‍‌​‍​‍​‍⁠​​‍​‍‌‍‍‌‌‍‌​​‍​‍​⁠‍‍​⁠‌‌​⁠‍​​⁠‌⁠​‍⁠​​‍​‍‌‍‌​​‍​‍​⁠‍‍​‍​‍​⁠​‍​⁠​​​⁠​‍​⁠‌‌​⁠​‌​⁠​​​⁠​‍​⁠‍​​‍​‍​‍⁠​​‍​‍‌‍‍​​‍​‍​⁠‍‍​‍​‍​⁠​⁠‌​‍‌​⁠‍‌‌‌‍‍‌‌‍‌‌‌‍‌‌​‌‌‌​‍‍‌​⁠‌‌‍​⁠‌‌‍‍‌‌‍​‌‍‌‍‌​‍​​⁠​​‌‍⁠⁠​‍​‍‌⁠⁠‌

I’ve been running a similar “3‑min + 12‑min” on a 1% Woodway with Shimmer; when W′bal dips <25% in the last 5–6 min, sustained tibial peaks >7.5 g in midfoot runners pop up, and a 3–4% cadence bump trims about 1 g without wrecking pacing. Belt stiffness and sensor filtering make this jumpy — — so my flags are device‑specific: RunScribe >7 g, Shimmer >8 g, only if “pacing drift >3%” isn’t the culprit. If you share the sheet, I can try anchoring peaks to W′bal percentiles instead of fixed cutoffs — interested?

‌⁠‍⁠​‍​‍‌⁠‌​​‍​‍​⁠‍‍​‍​‍‌⁠​⁠‌⁠​​‌‍⁠⁠‌⁠​‍‌⁠‌​‌⁠​⁠‌‍⁠‌‌‍‌‌‌‍‌​‌‍‍‌‌‍​⁠‌‍‍‌‌‍⁠‍‌‍‌‌​‍​‍​‍⁠​​‍​‍‌‍‍⁠​‍​‍​⁠‍‍​‍​‍‌⁠​‍‌‍‌‌‌⁠​​‌‍⁠​‌⁠‍‌​‍​‍​‍⁠​​‍​‍‌‍‍‌‌‍‌​​‍​‍​⁠‍‍​⁠‌‌​⁠‍​​⁠‌⁠​‍⁠​​‍​‍‌‍‌​​‍​‍​⁠‍‍​‍​‍​⁠​‍​⁠​​​⁠​‍​⁠‌‌​⁠​‌​⁠​‌​⁠​​​⁠​‍​‍​‍​‍⁠​​‍​‍‌‍‍​​‍​‍​⁠‍‍​‍​‍​⁠‌​​⁠​‌‌‌​‌‌​⁠⁠‌‍‍‌‌‌‌‍‌​‌‍​⁠‍‌‌‍‍‌‌‍⁠‍‌‌‍‍‌​‌⁠​⁠​‌‌‍‍‌​⁠​‍‌‌‍‍​‍​‍‌⁠⁠‌