Skill

---
name: brotools-loadflow-simulator
description: "Opens Adjie Brotools' Load Flow Simulator (https://tool.adjiebrotots.com/loadflow-simulator/) on the user's own scenario with one link, and the tool computes the answer. Use when the user asks about power system load flow (power flow) studies: bus voltages, line loading and losses on a network such as the IEEE/WSCC 9-bus, a distribution feeder or an HVDC case, AC Newton-Raphson or DC. Also use when they mention tool.adjiebrotots.com/loadflow-simulator."
---

# Load Flow Simulator on tool.adjiebrotots.com

Load Flow Simulator is a free calculator that runs in the user's browser. This skill turns the user's question into **one link** that opens the tool on their scenario. The tool, not you, works out the result: its figures come from its own model and data, and anything you work out separately can differ from what the user then sees.

## What it decides

- **Load Flow Simulator** (`loadflow-simulator`): How a power network behaves at one operating point: the voltage at every bus, the active and reactive power on every line, transformer and link, the losses, and which buses or branches fall outside their limits. It solves an AC (Newton-Raphson) or DC load flow on a single-line diagram.

## Workflow

1. **Pick the page.** Read the user's request and choose the page above that answers it. Open its reference (`references/<page>.md`, listed under Files) and read the LINK FORMAT, the most important keys and the Quick Starts. The reference is long: read the parts you need.
2. **Separate what the user said from what you must choose.** Every figure the user gave goes in as they gave it (convert units or periods only to match the field, and say so).
3. **Fill every other input that matters with a researched assumption.**
   - If you can search the web, do it for figures that change over time or by place. For this tool that usually means standards and grid codes (IEEE, IEC, EN 50160, the network operator's code), typical line, cable and transformer data, and the operating limits that apply. Prefer official and primary sources and note each source and its date.
   - If you cannot search, use your own knowledge and say it is an estimate as of your knowledge date.
   - Start from the nearest Quick Start (`qs`) for the user's place and case, and keep its figures unless you have a better one for this user. Send only what differs from it.
   - Prefer what the user said earlier in the conversation over general figures. Never invent a figure the user gave differently.
4. **Build the link with the script** (it checks every key, range and choice, and encodes the link exactly):
   ```bash
   python3 scripts/build_link.py --fields loadflow-simulator --find <words>     # look up keys
   python3 scripts/build_link.py --quickstarts loadflow-simulator --find <words> # look up Quick Starts
   python3 scripts/build_link.py spec.json                                   # build the link
   ```
   `spec.json` holds `page`, `qs`, `set` (key: value, in the units the field shows on screen, numbers written plainly: `800000`, `6.5`, never `800,000` or `6,5`), `why` (key: your reason, 200 characters at most, shown to the user beside the value; a list key or `json` can have one too), `note` (one line, such as the place and date), `json` (an object, for a page whose reference defines it). If it prints NOT BUILT, fix what it lists and run it again. Use the link it prints exactly as printed.
   The script checks every form field: its key, range, step and choices. List keys, part settings (`el....`) and `json` are checked by the tool when the link opens, so write them exactly in the syntax the reference gives (its COMPACT LISTS and JSON sections), with the names it lists. A Quick Start sets only what its line in the reference lists; when a list key (a set of tickers, portfolios or offers) replaces what the Quick Start holds, send every setting you want with it.
   If you cannot run code, build the link by hand from the LINK FORMAT in the reference, using only keys and values listed there, and check each value against its range.
5. **Reply in the format below, and stop.**

## Reply format

Your whole reply has these four parts, in this order, written in the user's language (keys and the link stay as they are):

1. **Your inputs**: a short list of what the user stated, each with the value that goes in the link.
2. **Assumptions**: a numbered list (or a table: Input | Value | Source or rationale), one entry per input you chose, each with its value and its source with the date for anything you looked up, or "estimate" and your reason for anything from your own knowledge. Put the same reason, shortened, in that key's `why`.
3. **The link**, as a clickable Markdown link to tool.adjiebrotots.com/loadflow-simulator/..., and again inside a code block so the user can copy it if their chat app breaks a long link.
4. The sentence: **Open the link to see the result.** You may add one line inviting the user to correct any assumption, and then you will send a new link.

**Do not state results.** No verdict, figure, estimate, range, "roughly", "likely", or preview of what the tool will show, not even if the user asks. The only numbers in your reply are the inputs in the link. If the user asks what the answer is, explain that the tool works it out from these inputs and the link opens it, and offer to change any input.

If the request is outside what this tool does, say so, give the tool's address and help the user as you normally would.

## Link format (summary)

```
https://tool.adjiebrotots.com/loadflow-simulator/#load&v=1&qs=<quick start>&<key>=<value>&why.<key>=<reason>&note=<one line>
```
- `#load` then `key=value` pairs joined by `&`, each value percent-encoded. `v=1` always.
- Values in the units the field shows: `6.1` for 6.1 %, `800000` for 800,000. A choice takes its listed value.
- The tool starts from the Quick Start (or its defaults) and applies each key. Keys not named keep their base value.
- Out of range numbers are pulled into range and unknown keys are skipped, and the tool tells the user. The script stops you before either happens.
- Never use the keys `s`, `open` or `embed`.

## Worked example

**User:** using tool.adjiebrotots.com/loadflow-simulator, on the WSCC 9-bus case, what happens to the voltages if the load at bus 5 rises to 150 MW?

**Spec** (`loadflow-simulator`):

```json
{
  "page": "loadflow-simulator",
  "set": {
    "el.LoadA.p_set": "150"
  },
  "why": {
    "el.LoadA.p_set": "The load at bus 5 is Load A in the WSCC 9-bus case; the user's 150 MW replaces its active power"
  },
  "qs": "wscc9",
  "note": "WSCC 9-bus case, load at bus 5 raised to 150 MW"
}
```

**Reply:**

**Your inputs**

- el.LoadA.p_set: 150

**Assumptions**

1. Network: the WSCC 9-bus Quick Start (qs=wscc9), unchanged apart from the load below.
2. Load at bus 5: Load A, the load on bus 5 in that case. Its active power is set to 150 MW (el.LoadA.p_set) and its reactive power stays at the Quick Start's figure.
3. Solver and limits: the Quick Start's own: the ac method (ac is the full AC load flow), voltage limits of 0.95 to 1.05 p.u. and a branch loading limit of 100%.

[Open Load Flow Simulator on this scenario](https://tool.adjiebrotots.com/loadflow-simulator/#load&v=1&qs=wscc9&el.LoadA.p_set=150&why.el.LoadA.p_set=The%20load%20at%20bus%205%20is%20Load%20A%20in%20the%20WSCC%209-bus%20case%3B%20the%20user%27s%20150%20MW%20replaces%20its%20active%20power&note=WSCC%209-bus%20case,%20load%20at%20bus%205%20raised%20to%20150%20MW)

```
https://tool.adjiebrotots.com/loadflow-simulator/#load&v=1&qs=wscc9&el.LoadA.p_set=150&why.el.LoadA.p_set=The%20load%20at%20bus%205%20is%20Load%20A%20in%20the%20WSCC%209-bus%20case%3B%20the%20user%27s%20150%20MW%20replaces%20its%20active%20power&note=WSCC%209-bus%20case,%20load%20at%20bus%205%20raised%20to%20150%20MW
```

Open the link to see the result.

## Files

- `references/loadflow-simulator.md`: Load Flow Simulator. Every key with its label, unit, range and default, the Quick Starts and what each sets, list and json syntaxes, and an example.
- `references/params.json`: the same keys as data (what the script checks against).
- `scripts/build_link.py`: builds and checks the link. `python3 scripts/build_link.py --help` explains it.

Source: https://tool.adjiebrotots.com/loadflow-simulator/ai/ (this skill, kept up to date with the tool).