> 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/arby/asasyat-alnmthjh/parameters/others/annual-harmonic-series-parameter.md).

# معلمة السلسلة التوافقية السنوية

## وصف عام

أ *المعلمة* والتي تقوم بإرجاع القيمة من سلسلة متناسقة سنوية.

هذه *المعلمة* يشتمل على دالة جيب التمام من السلسلة N بفترة 365 يومًا. يتم إجراء الحساب باستخدام يوم جوليان من السنة ناقص 1. هذا يسبب انقطاعًا بسيطًا في السنوات غير الكبيرة. [API المرجع](https://pywr.github.io/pywr-docs/master/api/generated/pywr.parameters.AnnualHarmonicSeriesParameter.html#pywr.parameters.AnnualHarmonicSeriesParameter)

$$f (t) =أ+ن=1 نانو⋅كوس ((2хnt) /365+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>

## مثال

قريبًا...

«جسون» {

}

```
```


---

# 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://water-strategy.gitbook.io/waterstrategy/arby/asasyat-alnmthjh/parameters/others/annual-harmonic-series-parameter.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.