> 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/modeling-basics/recorders/flow-duration-curve-recorders/flow-duration-curve-recorder.md).

# Flow Duration Curve Recorder

## General Description

This recorder calculates a flow duration curve for each scenario. [API Reference](https://pywr.github.io/pywr-docs/master/api/generated/pywr.recorders.FlowDurationCurveRecorder.html#pywr.recorders.FlowDurationCurveRecorder)

## Attributes

<table><thead><tr><th width="158">Name</th><th width="473">Description</th><th>Required</th></tr></thead><tbody><tr><td>model</td><td>pywr.core.Model</td><td>Yes</td></tr><tr><td>node</td><td>The node to record</td><td>Yes</td></tr><tr><td>percentiles</td><td>The percentiles to use in the calculation of the flow duration curve. Values must be in the range 0-100</td><td>Yes</td></tr><tr><td>agg_func</td><td>function used for aggregating the FDC across percentiles. Numpy style functions that support an axis argument are supported</td><td>Yes</td></tr><tr><td>fdc_agg_func</td><td>optional different function for aggregating across scenarios</td><td>Yes</td></tr></tbody></table>

## Example

coming soon...

```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 following URL with the `ask` and `goal` query parameters:

```
GET https://water-strategy.gitbook.io/waterstrategy/modeling-basics/recorders/flow-duration-curve-recorders/flow-duration-curve-recorder.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 `build a script that syncs our docs to a CMS` 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.