Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Develop needed constraints for MVS (ongoing) #133

Open
2 tasks
smartie2076 opened this issue Feb 26, 2020 · 3 comments
Open
2 tasks

Develop needed constraints for MVS (ongoing) #133

smartie2076 opened this issue Feb 26, 2020 · 3 comments
Assignees
Labels
enhancement New feature or request question Further information is requested

Comments

@smartie2076
Copy link
Collaborator

smartie2076 commented Feb 26, 2020

There are a number of constraints that will need to be introduced to the MVS.
@SabineHaas please think of possible constraints and also give a (sentence long) desctiption of the subsequent constraint.
Examples: Capacity limiter, net zero energy system, emissions, connection of transformer in/out

Ongoing list of necessary constraints (with descriptions):

Details for specific constraints should be discussed in own issues as to limit this thread´s lenght.

@smartie2076
Copy link
Collaborator Author

Connection of capacities of optimized transformers that cover an input/output flow

Currently, when optimizing a transformer, only the uni-lateral necessary capacity is optimized. For example, when optimizing a battery charging controller, both the charging capacity (rectifier from AC) and discharging capacity (inverter from DC) are optimized individually. This requires cost data for both capacities or a intentional setting of one of the costs to zero (expected lower flow). The capacities can be of different value (eg. peaks of charges due to PV while discharge takes place with a constant low flow, ie. rectifier-part sized large and inverter-part sized small).

However, it might be that the inverter/rectifier capacity in this example are connected or of equal size. This should be considered by linking the capacities:

def backup(model, transformer_in, transformer_out, bus):

    def equal_capacity_rule(model, t):
        expr = model.InvestmentFlow.invest[transformer_in, bus] 
        expr = - model.InvestmentFlow.invest[transformer_out, bus]
        return expr == 0
            
    model.stability_constraint = po.Constraint(
        model.TIMESTEPS, rule=equal_capacity_rule
    )

    return model

Touches issue #24

@smartie2076
Copy link
Collaborator Author

Feedin-limit avoid unbound solutions

As described in issue #1 it could make sense to introduce constraints to feed-ins, possibly only to allow to display an error message instead of simply terminating the simulation.

@smartie2076 smartie2076 added this to To do in Issues Feb 27, 2020
@SabineHaas
Copy link
Collaborator

SabineHaas commented Jun 16, 2020

maximum installed capacity constraint (maximumCap) was added for

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request question Further information is requested
Projects
Issues
  
To do
Nice_to_have
  
To Do
Development

No branches or pull requests

2 participants