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

Flow's full_load_time depends on time horizon #1104

Open
p-snft opened this issue Aug 15, 2024 · 0 comments
Open

Flow's full_load_time depends on time horizon #1104

p-snft opened this issue Aug 15, 2024 · 0 comments

Comments

@p-snft
Copy link
Member

p-snft commented Aug 15, 2024

Currently, we have parameters full_load_time_min and full_load_time_max, respectively.

    flow = solph.flows.Flow(nominal_value=2, full_load_time_min=4.5)

Assuming kW as the base unit for flows, means, that at least 9 kWh have to go through that flow. For short time horizons, that can be a low number, for time horizons lower than 4.5 h, the problem becomes infeasible. In my opinion, we should replace this by a minimum and maximum average load, respectively.

    flow = solph.flows.Flow(nominal_value=2, minimum_average_load=0.25)

This would mean 18/4 = 4.5 full load hours for a time horizon of 18 hours but 8760/4 = 2190 full load hours if a full year is optimised.

@p-snft p-snft added this to the v0.5.x milestone Aug 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant