PyPSA / PyPSA/pypsa-usa

TAMU Transformer pu conversion

Open
#742 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug question
Dominant language
Python
Stars
148
Forks
55
Avg merge
2d 11h
Merged PRs (30d)
18

Description

Version Checks (indicate both or one)
The Issue

The TAMU network groups lines and transformers together in the branches.csv file. When PyPSA-USA ingests this file, it adds lines and transformers separately. The pu/base unit conversions are the same, though?

https://github.com/PyPSA/pypsa-usa/blob/338af9912addbaf038c6098fe27e1e6ef099d8aa/workflow/scripts/build_base_network.py#L73-L101

The line calculations seem fine, however, PyPSA uses percentages of the nominal power ranking to describe x and r for transformers?

https://github.com/PyPSA/PyPSA/blob/c45f75089d22bc9972a9500929dd7b854acdd9fb/pypsa/network/power_flow.py#L773-L785

Therefore, when PyPSA calculates the pu value, wont they be off?

I don't have a processed PyPSA-USA/TAMU network on hand to check! So apologies if I am just missing a conversion somewhere.

Steps To Reproduce

No response

Error Message

Anything else?

No response

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Read workflow/scripts/build_base_network.py around lines 73-101, then compare its line and transformer unit handling with PyPSA's power_flow.py around lines 773-785. Use a processed TAMU network or construct the relevant input from branches.csv to verify whether transformer pu values are converted correctly; done when the discrepancy is confirmed and the conversion behavior is corrected or documented.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
data-engineering
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.