in job/ app, allow modeling multiple outages

Open
#344 0 comments 0 reactions 1 assignee View on GitHub

@hdunham is already working on this.

Since Aug 3, 2022.

Assessment

This issue has not been assessed yet.

Description

  • I'm submitting a ...

    • bug report
    • feature request
    • support request => Please do not submit support request here, see note at the top of this template.

  • What is the current behavior?
    missing multiple outage modeling inputs and validation for v3 (job/ app)

  • What is the expected behavior?
    add the following ElectricUtilityInputs & required validation:

    • outage_start_time_steps::Array{Int,1}=Int[], # we minimize the maximum outage cost over outage start times
    • outage_durations::Array{Int,1}=Int[], # one-to-one with outage_probabilities, outage_durations can be a random variable
    • outage_probabilities::Array{R,1} where R<:Real = [1.0],
    • outage_time_steps::Union{Nothing, UnitRange} = isempty(outage_durations) ? nothing : 1:maximum(outage_durations),
    • scenarios::Union{Nothing, UnitRange} = isempty(outage_durations) ? nothing : 1:length(outage_durations),

And add associated outputs

  • What is the motivation / use case for changing the behavior?
    Allow for modeling multiple, probabilistic outages
Dominant language
Python
Stars
125
Forks
68
Avg merge
1d 21h
Merged PRs (30d)
1

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from NatLabRockies/REopt_API

All issues in NatLabRockies/REopt_API

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.