> 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.md).

# Recorders

This page describes the process of creating a new Recorder in WaterStrategy and a selection of the most commonly used Pywrrecorder types, and most commonly used attributes. The full list of built-in recorders and their exhaustive list of attributes are [here](https://pywr.github.io/pywr-docs/master/api/pywr.recorders.html).

{% embed url="<https://youtu.be/ZAGU8HQ78to>" %}

## 1. Creating a Recorder in WaterStrategy

In a Network page, click the 'Recorders' Tab:

<figure><img src="/files/KgNJg0gXlH9hNtjZjRLd" alt=""><figcaption><p>CLick the 'Recorders' Tab</p></figcaption></figure>

Next to the 'Recorders-Type Categories' Text, click the '+' button and select 'PYWR\_RECORDER':\\

<figure><img src="/files/3rjhU67JfdZomOMUA9yJ" alt=""><figcaption></figcaption></figure>

Enter the name of your recorder. This can be anything you like, <mark style="color:red;">**but must be unique within the network**</mark>**.**

<figure><img src="/files/WkeN6yM6rbfAK9r28EtO" alt=""><figcaption></figcaption></figure>

Populate the recorder in the JSON editor:

<figure><img src="/files/Ja7aquQzso2WRiaUhpKB" alt=""><figcaption></figcaption></figure>

## 2. Recorder editors in WaterStrategy

Currently, there are two different ways to input a Recorder in WaterStrategy. ....

## 3. NumpyArrayNodeRecorder

Recorder for timeseries information from a Node. [API Reference](https://pywr.github.io/pywr-docs/master/api/generated/pywr.recorders.NumpyArrayNodeRecorder.html#pywr.recorders.NumpyArrayNodeRecorder)

This class stores flow from a specific node for each time-step of a simulation. The results of a recorder are output on the Network Attributes panel, and will be named 'simulated\_\<recordername>'

### 3.1. Attributes

<table><thead><tr><th width="196">Name</th><th width="243">Description</th><th>Required</th><th>Default value</th></tr></thead><tbody><tr><td>type</td><td>numpyarraynoderecorder</td><td>Yes</td><td>None</td></tr><tr><td>node</td><td>Name of the node to record</td><td>Yes</td><td>None</td></tr><tr><td>temporal_agg_func</td><td></td><td>Optional</td><td>mean</td></tr><tr><td>agg_func</td><td></td><td>Optional</td><td>mean</td></tr></tbody></table>

### 3.2. Example

```json
{
	"type": "NumpyArrayNodeRecorder",
	"node": "Reservoir 1",
	"temporal_agg_func": "mean",
	"agg_func": "mean"
}
```


---

# 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/modeling-basics/recorders.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.