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

Changed delay times of cycle loads to obtain annual demand and cycles #25

Merged
merged 1 commit into from
Mar 9, 2020

Conversation

cprotopa
Copy link
Contributor

@cprotopa cprotopa commented Mar 2, 2020

I noticed that for cold appliances, which are cycling loads, using the given cycle length and delay (between cycles) resulted in too many cycles in a year, and consequently too high annual demand (compared to reference from Richardson's CREST model). Assuming that what is more important is the annual consumption, and taking as given inputs the power and cycle length, I adjusted the delay time such that the annual consumption fits the desired one.
There is still some variation among households taken into account by sampling the cycle length and delay around the mean values.
This is not the one and only correct way to do it, but I think it's more clean and respects the values given in Appliances.py.

@SilkeVerbruggen
Copy link
Contributor

I see that you both changed the delay time in the appliances.py and in residential.py. It seems to me a bit strange that you increase the delay time in one part and decrease it in the other.
Is it not possible to just increase the delay time in the appliances.py file, in order to get the same amount of cycles? or did I completely misinterpreted this?

@cprotopa
Copy link
Contributor Author

cprotopa commented Mar 5, 2020

In Apppliances.py I indeed changed the "nominal" values of the delay, so that on average the annual demand is correct. However, to avoid that all fridges in all houses work exactly the same, the actual delay time for each created household is sampled from a normal gauss distribution with mean the nominal self.delay and standard deviation self.delay/10. The std used to be self.delay/4, and I changed to have a narrower spread, but with no particularly good justification actually (up for discussion, if anybody has a better suggestion).
Furthermore, to avoid that all start approximately at the same time I initiate the starting time that is left as left = random.gauss(delay/2, delay/4), thus somewhere in the middle of the delay period. Also up for discussion, as it's only an assumption.

@SilkeVerbruggen
Copy link
Contributor

Okay I understand. I think the change of 'left' is logical. I just don't know about the change in 'delay' as it seems a bit randomly chosen now. But I understand what you did and I think you can merge this to the main branch.

@cprotopa cprotopa merged commit 69e87bf into master Mar 9, 2020
@cprotopa cprotopa deleted the cycle_loads branch March 9, 2020 08:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants