-
Notifications
You must be signed in to change notification settings - Fork 5
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
Conceptualize and implement a "realistic" stochastic load agent #691
Labels
enhancement
New feature or request
Comments
t-ober
added
enhancement
New feature or request
good first issue
Good for newcomers
labels
Jan 4, 2024
t-ober
changed the title
Conceptualize and Implement a "realistic" load agent
Conceptualize and implement a "realistic" stochastic load agent
Jan 4, 2024
pierrepetersmeier
added a commit
that referenced
this issue
Apr 11, 2024
…ent-a-realistic-stochastic-load-agent' into pp/#691-conceptualize-and-implement-a-realistic-stochastic-load-agent
danielfeismann
added a commit
that referenced
this issue
May 23, 2024
…t-a-realistic-stochastic-load-agent
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We are currently lacking a load agent that is "realistically" stochastic. Our current Agents consist of
ProfileLoadAgent
: Which represents standard load profiles. Which is only really realistic when looking at a multitude of loads in that respective category, since it basically depicts their average behavior.FixedLoadAgent
: Which has a fixed load.RandomLoadAgent
: Which is kind of what we want, but not really. The problem here is, that the household picks a random value from a distribution. That means the previous value has nothing to do with the last value (we probably should double check, that that is in fact true).We need a household that is stochastic, but without the limitation of the
RandomLoadAgent
, meaning that not only the individual values depict a expected distribution, but also the sequence of values is sensible. One modeling approach could be to go for a Markov chain type of process, similar as our half-finished implementation here.The text was updated successfully, but these errors were encountered: