> For the complete documentation index, see [llms.txt](https://water-strategy.gitbook.io/waterstrategy/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://water-strategy.gitbook.io/waterstrategy/zhong-guo-ren/jian-mo-ji-chu-zhi-shi/parameters/others/annual-harmonic-series-parameter.md).

# 年度谐波系列参数

## 一般描述

一个 *参数* 它返回年度谐波序列的值。

这个 *参数* 包括一个周期为 365 天的系列 N 余弦函数。使用一年中的朱利安日减去 1 进行计算。这在非闰年中会造成轻微的不连续性。 [API 参考资料](https://pywr.github.io/pywr-docs/master/api/generated/pywr.parameters.AnnualHarmonicSeriesParameter.html#pywr.parameters.AnnualHarmonicSeriesParameter)

$f (t) =a+n=1nan⋅COS ((2^nt) /365+0\_\_n) $$

## 属性

<table><thead><tr><th width="158">姓名</th><th width="473">描述</th><th>必填项</th></tr></thead><tbody><tr><td>意思</td><td>序列的平均值（即零次谐波的位置）</td><td>是的</td></tr><tr><td>振幅</td><td>N 谐波余弦函数的振幅。必须与阶段的长度相同</td><td>是的</td></tr><tr><td>阶段</td><td>N 谐波余弦函数的相移。长度必须与振幅相同</td><td>是的</td></tr></tbody></table>

## 示例

即将推出...

\`\`json {

}

```
```


---

# 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://water-strategy.gitbook.io/waterstrategy/zhong-guo-ren/jian-mo-ji-chu-zhi-shi/parameters/others/annual-harmonic-series-parameter.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.