> For the complete documentation index, see [llms.txt](https://strydtaiwan.gitbook.io/stryd/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://strydtaiwan.gitbook.io/stryd/guide-book/introduction-to-run-power/about-stryd.md).

# 關於Stryd

Stryd除了可以測量並紀錄功率（Power）之外，也可以紀錄到很多相關的數據（[點我查看目前支援的裝置](https://strydtaiwan.gitbook.io/stryd/setup-stryd/connect-with-your-watch/ke-zhi-yuan-she-bei)），包括：

* **姿勢功率（Form Power）**
* **配速（Pace）**
* **步頻（Cadence）**
* **觸地時間（Ground contact time）**
* **垂直振幅（Vertical Oscillation）**
* **下肢彈簧剛性（Leg Spring Stiffness）**
* **距離（Distance）**
* **高度（Elevation）**
* **風 (wind)**

功率就是指做功（work）的速率：它是在測量你用多快的速率做了多少功，單位為瓦特（Watt，W）。只要你用愈快的速度從A點移動到B點，你的功率輸出就愈高，因為你在更短的時間內做相同的功。在計算自行車功率時，由於踩踏的動作是固定的，所以功率計是測量踩踏的力量 x 迴轉速，即：\
**功率 = 力量(Force) x 速度(Velocity)**

\
然而，跑步時雙腿的動作並沒有固定軌跡，所以Stryd是採用以下的方程式計算功率：\
功率 = 質量(Mass) x 加速度(Acceleration) x 速度(Velocity)

\
由於我們在跑步時身體的質量（體重）是固定的，所以Stryd是透過測量動作的加速度與速度來推算出功率，並即時傳送到手錶螢幕上。\
\
因此，當動作的幅度愈大或速度愈快，跑步功率就愈高。功率可以準確測量身體當前的能量代謝消耗（metabolic energy expenditure），不受風向、地形等的影響，同時由於其即時測量的特性，所以相對於配速與心率，功率顯然是一個絕佳的運動強度指標。


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://strydtaiwan.gitbook.io/stryd/guide-book/introduction-to-run-power/about-stryd.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.