> 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/recorders/statistical-recorders/mean-flow-node-recorder.md).

# 平均流量节点记录器

## 一般描述

记录节点的平均流量。

可以提供一个系数来调整总流量（例如，用于计算运营成本）。 [API 参考资料](https://pywr.github.io/pywr-docs/master/api/generated/pywr.recorders.MeanFlowNodeRecorder.html)

## 属性

<table><thead><tr><th width="155">姓名</th><th width="395">描述</th><th>必填项</th></tr></thead><tbody><tr><td>模型</td><td></td><td></td></tr><tr><td>名称</td><td>录音机的名字</td><td>可选</td></tr><tr><td>节点</td><td>清单 <em>pywr.core.node</em> 要记录的实例</td><td>可选</td></tr><tr><td>因素</td><td>适用于每个节点的因子列表</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/recorders/statistical-recorders/mean-flow-node-recorder.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.