PyPSA / PyPSA/PyPSA

Add custom constraints to the network's data model

Open
#322 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

gap IO
Dominant language
Python
Stars
2.2k
Forks
699
Avg merge
2d 10h
Merged PRs (30d)
13

Description

Original idea: store extra_functionality by string.

Updated version (by @FabianHofmann)

Custom constraint and their duals should become a officially supported part of the data model with IO functionality. This will be realized by leveraging efforts in https://github.com/PyPSA/linopy/issues/561.

Contributor guide

Open the contributing guide

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

The issue names PyPSA's network data model and IO, but no files or tests. Begin with the linked linopy issue #561, then locate the existing network data-model and IO entry points; done means custom constraints and their duals are supported as part of the model and its persistence.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
backend, data
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.