> For the complete documentation index, see [llms.txt](https://docs.velogicfit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.velogicfit.com/zh/di-02-jie-shi-yong-velogic-studio/pedal-angular-velocity.md).

# 踏板角速度可视化

了解如何在 Velogic Studio v4 中可视化整个踩踏过程中的踏板角速度

Velogic Studio v4 的新功能之一是能够可视化踏板在整个踩踏过程中角速度的变化。

如果你 [锁定单次采集以供回顾](/zh/di-02-jie-shi-yong-velogic-studio/reviewing-fit-artifacts.md#locking-a-capture-for-review) （或 [比较 2 次采集](/zh/di-02-jie-shi-yong-velogic-studio/reviewing-fit-artifacts.md#comparing-2-different-captures)），然后点击踏频指标：

![MotionMetriqs 面板中的踏频指标，可用于访问踏板角速度可视化](https://2529810062-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FjxwtZYYk0lvusnMTywNR%2Fuploads%2Fgit-blob-abc2ac66f9a31771c690ed7f03419b433e1e8dff%2Freviewing-fit-artifacts-cadence-metric.png?alt=media)

……你会看到一个可视化图表叠加在曲柄角度拖动条上，位于动作分析视频的顶部：

![踏板角速度图，显示曲柄角度分析，蓝线表示速度变化](https://2529810062-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FjxwtZYYk0lvusnMTywNR%2Fuploads%2Fgit-blob-fb0428135504a602956456028f3509dbece8e430%2Fpedal-angular-velocity-viz.png?alt=media)

在这个可视化中：

1. 横轴表示曲柄角度
2. 横轴上的小点表示 Velogic Studio 纳入分析的帧
3. 大点表示当前显示的曲柄角度
4. 蓝色图线是 Velogic Studio 对该曲柄角度下踏板角速度的测量，围绕平均值上下分布。

通常，你会期望在发力阶段看到踏板角速度出现一个峰值或“隆起”。在上面的示例中，发力阶段似乎呈“二峰型”，这可能是你在拟合过程中会想要研究的内容。

你可以使用这个可视化来了解踏板/曲柄在整个踩踏过程中是如何加速或减速的。尤其是在对比两次采集时，它非常有效，有助于理解某项干预的效果，并且可能值得进一步研究与……的相关性 [踝关节屈曲](/zh/di-02-jie-shi-yong-velogic-studio/ankle-flexion-metrics.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.velogicfit.com/zh/di-02-jie-shi-yong-velogic-studio/pedal-angular-velocity.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.