> 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/parameters/hydropower-parameters.md).

# Hydropower Parameters

{% embed url="<https://www.youtube.com/watch?v=12UO16e5GJU>" %}
Video using the Hydropower Target parameter
{% endembed %}

## General Description

The **hydropower target parameter** is a parameter that returns flow from a hydropower generation target. This parameter calculates the flow required to generate a particular hydropower production target. It is intended to be used on a node representing a turbine where a particular production target is required each time-step.[ API Reference](https://pywr.github.io/pywr-docs/master/api/generated/pywr.parameters.HydropowerTargetParameter.html#pywr.parameters.HydropowerTargetParameter)

## Attributes

<table><thead><tr><th width="223">Name</th><th width="295">Description</th><th>Required</th></tr></thead><tbody><tr><td>type</td><td>hydropowertarget</td><td>Yes</td></tr><tr><td>target</td><td>Hydropower production target. Units should be in units of energy per day</td><td>Optional</td></tr><tr><td>water_elevation_parameter</td><td>Elevation of water entering the turbine. The difference of this value with the <em>turbine_elevation</em> gives the working head of the turbine</td><td>Optional</td></tr><tr><td>max_flow</td><td>Upper bounds on the calculated flow. If set the flow returned by this parameter is at most the value of the max_flow parameter</td><td>Optional</td></tr><tr><td>min_flow</td><td>Lower bounds on the calculated flow. If set the flow returned by this parameter is at least the value of the min_flow parameter</td><td>Optional</td></tr><tr><td>min_head</td><td>Minimum head for flow to occur. If actual head is less than this value zero flow is returned</td><td>Optional</td></tr><tr><td>turbine_elevation</td><td>Elevation of the turbine itself. The difference between the <em>water_elevation</em> and this value gives the working head of the turbine</td><td>Optional</td></tr><tr><td>efficiency</td><td>The efficiency of the turbine</td><td>Optional</td></tr><tr><td>density</td><td>The density of water</td><td>Optional</td></tr><tr><td>flow_unit_conversion</td><td>A factor used to transform the units of flow to be compatible with the equation here. This should convert flow to units of m3/day</td><td>Optional</td></tr><tr><td>energy_unit_conversion</td><td>A factor used to transform the units of total energy. Defaults to 1e-6 to return MJ</td><td>Optional</td></tr></tbody></table>

## Example

```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/modeling-basics/parameters/hydropower-parameters.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.