Casestudycvar#1560
Closed
florinelaseur wants to merge 11 commits intoTulipaEnergy:mainfrom
Closed
Conversation
077795d to
8028909
Compare
Member
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
WIP casestudycvar
-does not find value_at_risk_threshold_mu (in lines 139-140 or 144-145) (errors are that key does not exist and "var_value_at_risk_threshold_mu" not found). DuckDB queries do not have to be inserted for variables right? What is the correct way to call the optimal VaR both for the benchmark in this block (and I will repeat this later in main for each case study -and their 6 different numbers of rps - such that I can add the column to results_df?)
Example-tulipa-single-year with 3 scenarios is chosen as input data to reduce the computational complexity for first (not realistic for CVaR) test results.
Thank you!!
UPDATE
Hi Diego Thank you very much! I performed the steps. I cannot seem to create a new PR on the same branch (as this one is still open?) but in the current version of Tulipa, The line time_to_read = @Elapsed energy_problem_benchmark = TEM.EnergyProblem(connection_benchmark) gives "Error: No implicit schema for table named model_paramets". moving it to different folders then than the input_data_path did not work and it seems the only way to correctly read the 2 parameters for the benchmark, as we dont want them to be read from casestudy files. Could you please look at my final commit "Implicit schema for table named model_parameters"? Thanks! Cheers,
Florine
Checklist