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

get_resolution not implemented for OptimizationProblemResults #1125

Closed
jd-lara opened this issue Jul 16, 2024 · 6 comments · Fixed by #1127
Closed

get_resolution not implemented for OptimizationProblemResults #1125

jd-lara opened this issue Jul 16, 2024 · 6 comments · Fixed by #1127
Assignees
Labels

Comments

@jd-lara
Copy link
Member

jd-lara commented Jul 16, 2024

Issue in line:

@GabrielKS GabrielKS self-assigned this Jul 24, 2024
@GabrielKS
Copy link
Contributor

Reported by @gmantegna

@GabrielKS
Copy link
Contributor

A quick repro using a PowerAnalytics.jl REPL:

] activate test  # must instantiate correctly, etc.
include("test/runtests.jl")  # running the PA tests gives us an `OptimizationProblemResults` to work with
PSI.get_realized_timestamps(problem_results)  # yields `MethodError: no method matching get_resolution(::OptimizationProblemResults)`

@GabrielKS
Copy link
Contributor

The root cause is that get_resolution(res::OptimizationProblemResults) got moved to IS.Optimization and isn't being imported into PSI. It is worth noting that we now have (at least) three different get_resolution functions in three different packages, suggesting that we should put some effort towards standardizing how things are imported from IS:
Screenshot 2024-07-24 at 10 23 42 AM

@GabrielKS
Copy link
Contributor

get_forecast_horizon is four different functions:
Screenshot 2024-07-24 at 10 33 35 AM

@jd-lara
Copy link
Member Author

jd-lara commented Jul 24, 2024

Yeah, we need to look into the method clean up here for the same function.

@GabrielKS
Copy link
Contributor

For now, I will just add the necessary imports to PSI to resolve this, but let's at some point come up with a principled solution to the whole importing problem here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants