> 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/espanol/conceptos-basicos-de-modelado/node-types/water-output/output-node.md).

# Nodo de salida

## Descripción general

El **nodo de salida** ([API Referencia](https://pywr.github.io/pywr-docs/master/api/generated/pywr.nodes.Output.html)) es una salida general en cualquier punto de la red. Los nodos de salida eliminan el agua del sistema.

Los nodos de salida son necesarios al final de un río y, en este caso de uso, generalmente no tienen una penalización de asignación ni un flujo máximo asignado.

Los nodos de salida también se utilizan para representar las demandas de agua para el consumo. En este caso de uso, suelen asignarles penalizaciones de asignación negativas, de modo que el programa lineal les asigna agua además de un caudal máximo, que puede ser una constante o un parámetro que represente la demanda de agua.

## Atributos principales

\_flujo

<table><thead><tr><th width="181.33333333333331">Nombre</th><th width="342">Descripción</th><th>Necesario</th><th></th><th></th></tr></thead><tbody><tr><td>penalización de asignación</td><td>El costo por unidad fluye a través del nodo</td><td>Opcional</td><td></td><td></td></tr><tr><td>máximo_</td><td></td><td></td><td></td><td></td></tr><tr><td>flow</td><td>La restricción de flujo máxima del nodo</td><td>Opcional min</td><td>La restricción de flujo mínima del nodo</td><td>Opcional</td></tr></tbody></table>

## Ejemplos

próximamente...


---

# 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/espanol/conceptos-basicos-de-modelado/node-types/water-output/output-node.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.