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

IntertemporalRaoInput class #1219

Closed
bqth29 opened this issue Dec 6, 2024 · 0 comments · Fixed by #1232
Closed

IntertemporalRaoInput class #1219

bqth29 opened this issue Dec 6, 2024 · 0 comments · Fixed by #1232
Labels
feature New feature or request good first issue Good for newcomers intertemporality Encompasses the use of multi-time-steps optimization and intertemporal constraints wait-for-requirements This issue cannot be addressed for the moment as new features must be added to the code first

Comments

@bqth29
Copy link
Collaborator

bqth29 commented Dec 6, 2024

Describe the current behavior

No response

Describe the expected behavior

As introduced in #1208 (in this comment), we need a new IntertemporalRaoInput class for intertemporal computations.

This class will at first contain two main attributes:

  • a TemporalData<RaoInput> time series with all the inputs for each timestamp
  • a Set<PowerGradientConstraint> that contains all the PGCs of the problem
  • a set of RaoParameters with an inter-temporal-parameters-extension for specific settings regarding parallel computations on various timestamps (topological actions, sensitivity computations)

as currently done for single-TS RAO inputs, the parameters can be provided outside the RaoInput

  • Add TemporalData API #1217 will have to be addressed first so you can use the TemporalData API
  • wait for the inter-temporal-parameters-extension (see Add inter-temporal-parameters extension to RAO Parameters #1230) to have been created for another issue, or do not forget to add a RaoParameters to IntertemporalRaoInput's attributes if you tackle this issue first
  • as discussed in the aforementioned comment, the individual RaoInputs of the RAO input time series shall only contain a CRAC and a network (GLSKs and reference programs are not required for the intertemporal POC and will be dealt with in future works; and states/perimeters are irrelevant as we currently only focus on preventive optimization)

Describe the motivation

No response

Extra Information

Not mandatory for implementation but start thinking about relevant methods that could be defined for this class and list them in this issue.

First ideas:

  • TemporalData<Crac> getCracTemporalData()
  • TemporalData<Network> getNetworkTemporalData()
  • Set<PowerGradientConstraint> getAllPowerGradientConstraints(String networkElementId)
@bqth29 bqth29 added feature New feature or request good first issue Good for newcomers wait-for-requirements This issue cannot be addressed for the moment as new features must be added to the code first intertemporality Encompasses the use of multi-time-steps optimization and intertemporal constraints labels Dec 6, 2024
@bqth29 bqth29 added this to the Intertemporal RAO milestone Dec 6, 2024
@bqth29 bqth29 moved this to Ready in OpenRao Planning Dec 6, 2024
@github-project-automation github-project-automation bot moved this from Ready to Done in OpenRao Planning Dec 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New feature or request good first issue Good for newcomers intertemporality Encompasses the use of multi-time-steps optimization and intertemporal constraints wait-for-requirements This issue cannot be addressed for the moment as new features must be added to the code first
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant