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

EV & Sector wise Demands #51

Closed
2 tasks
MPavicevic opened this issue Oct 3, 2019 · 2 comments
Closed
2 tasks

EV & Sector wise Demands #51

MPavicevic opened this issue Oct 3, 2019 · 2 comments

Comments

@MPavicevic
Copy link
Member

@squoilin and @kavvkon People are telling me that we should introduce separate demand curves as inputs which are provided as .csv time-series:

  • Electric vehicles
  • Commercial, Residential, Industrial

Although i do agree that it might make sense for the EV's but I'm not convinced that we would get any useful insights from the second one. The only thing that comes to my mind when we speak about individual demand curves is that it might be easier to decide how much load shedding is available (e.a. industry gets cut off first....), but then again we usually don't analyze systems that lack capacity

@kavvkon
Copy link
Member

kavvkon commented Oct 4, 2019

In the long term from a data point of view I would say it is a good idea, as the explicit representation of data and sectors packaged along with the model is one of the strong points of Dispa-SET. But the breakdown of the demand in such sectors is a big work by itself...

From a modelling point of view I do not think that is worth parametrizing those electrical loads differently in the model, apart from the ability to flexibilize them by allowing it to defer it by set number of hours (#8).
Different costs in load shedding would be a nice feature as well if we study extreme events. e.g. What would you accept to be interrupted in a long cold spell without wind ? your heat pump, your EV or the industry ?
To conclude not a priority but as a first step we can include the data when we have it and modify the preproccesing accordingly. I leave it open for discussion...

@squoilin
Copy link
Member

I would remove it from the open issues for now since this is really not a priority. The differentiation between different demands should be done upstream of the dispaset database, and result in the EV storage profiles, flexible demand times series, load shedding time series, etc.

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

3 participants