-
Notifications
You must be signed in to change notification settings - Fork 61
Consolidating test database creation #239
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
Open
ParticularlyPythonicBS
wants to merge
1
commit into
unstable
Choose a base branch
from
ref/consolidating_testing_dbs
base: unstable
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Some comments aren't visible on the classic Files Changed page.
There are no files selected for viewing
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
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
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,73 +1,21 @@ | ||
| # this config is used for testing in test_full_runs.py | ||
| scenario = "test run" | ||
| scenario_mode = "perfect_foresight" | ||
|
|
||
| input_database = "tests/testing_outputs/annualised_demand.sqlite" | ||
| output_database = "tests/testing_outputs/annualised_demand.sqlite" | ||
| neos = false | ||
|
|
||
| # solver | ||
| solver_name = "appsi_highs" | ||
|
|
||
| # generate an excel file in the output_files folder | ||
| save_excel = false | ||
|
|
||
| # save the duals in the output .sqlite database | ||
| save_duals = false | ||
|
|
||
| # save a copy of the pyomo-generated lp file to the outputs folder (may be large file!) | ||
| save_lp_file = false | ||
| time_sequencing = "representative_periods" | ||
| reserve_margin = "static" | ||
|
|
||
| # ------------------------------------ | ||
| # MODEL PARAMETERS | ||
| # these are specific to each model | ||
| # ------------------------------------ | ||
|
|
||
| # What seasons represent in the model | ||
| # Options: | ||
| # 'consecutive_days' | ||
| # Seasons are a set of days in order, with each season representing only one day. Examples | ||
| # might be a model of a representative week with 7 days or a whole-year model with 365 days. | ||
| # Seasonal storage need not be tagged and the time_season_sequential table can be left empty. | ||
| # 'representative_periods' | ||
| # Each season represents a number of days, though not necessarily in any particular order. | ||
| # If using inter-season constraints like seasonal storage or ramp rates, the true sequence | ||
| # must be defined using the time_season_sequential table. Seasonal storage must also be tagged in | ||
| # the technology table. | ||
| # 'seasonal_timeslices' | ||
| # Each season represents a sequential slice of the year, with one or many days represented per | ||
| # season. We assume that the true sequence is the same as the TimeSeason sequence, so the | ||
| # time_season_sequential table can be left empty. Seasonal storage must still be tagged. | ||
| # 'manual' | ||
| # The sequence of time slices is defined manually in the TimeNext table (which is commented out | ||
| # in the schema). This is an advanced feature and not recommended for most users. Seasonal | ||
| # storage must be tagged and the time_season_sequential table filled. | ||
| time_sequencing = 'representative_periods' | ||
|
|
||
| # How contributions to the planning reserve margin are calculated | ||
| # Options: | ||
| # 'static' | ||
| # Traditional planning reserve formulation. Contributions are independent of hourly availability: | ||
| # capacity value = net capacity * capacity credit | ||
| # 'dynamic' | ||
| # Contributions are available output including a capacity derate factor (e.g., forced outage rate). | ||
| # For most generators, contributions are available (derated) output in each time slice: | ||
| # capacity value = net capacity * reserve capacity derate * capacity factor | ||
| # For storage, contributions are (derated) actual output in each time slice: | ||
| # capacity value = flow out * reserve capacity derate | ||
| reserve_margin = 'static' | ||
|
|
||
| # --------------------------------------------------- | ||
| # MODE OPTIONS | ||
| # options below are mode-specific and will be ignored | ||
| # if the run is not executed in that mode. | ||
| # --------------------------------------------------- | ||
| [MGA] | ||
| cost_epsilon = 0.03 # 3% relaxation on optimal cost | ||
| iteration_limit = 15 # max iterations to perform | ||
| time_limit_hrs = 1 # max time | ||
| axis = "tech_category_activity" # use the tech activity Manager to control exploration based on categories in Tech | ||
| weighting = "hull_expansion" # use a convex hull expansion algorithm to weight exploration | ||
| cost_epsilon = 0.03 | ||
| iteration_limit = 15 | ||
| time_limit_hrs = 1 | ||
| axis = "tech_category_activity" | ||
| weighting = "hull_expansion" | ||
|
|
||
| [myopic] | ||
| myopic_view = 2 # number of periods seen at one iteration | ||
| myopic_view = 2 |
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,71 +1,19 @@ | ||
| # this config is used for testing in test_full_runs.py | ||
| scenario = "test run" | ||
| scenario_mode = "perfect_foresight" | ||
|
|
||
| input_database = "tests/testing_outputs/emissions.sqlite" | ||
| output_database = "tests/testing_outputs/emissions.sqlite" | ||
| neos = false | ||
|
|
||
| # solver | ||
| solver_name = "appsi_highs" | ||
|
|
||
| # generate an excel file in the output_files folder | ||
| save_excel = false | ||
|
|
||
| # save the duals in the output .sqlite database | ||
| save_duals = false | ||
|
|
||
| # save a copy of the pyomo-generated lp file to the outputs folder (may be large file!) | ||
| save_lp_file = false | ||
| time_sequencing = "seasonal_timeslices" | ||
| reserve_margin = "static" | ||
|
|
||
| # ------------------------------------ | ||
| # MODEL PARAMETERS | ||
| # these are specific to each model | ||
| # ------------------------------------ | ||
|
|
||
| # What seasons represent in the model | ||
| # Options: | ||
| # 'consecutive_days' | ||
| # Seasons are a set of days in order, with each season representing only one day. Examples | ||
| # might be a model of a representative week with 7 days or a whole-year model with 365 days. | ||
| # Seasonal storage need not be tagged and the time_season_sequential table can be left empty. | ||
| # 'representative_periods' | ||
| # Each season represents a number of days, though not necessarily in any particular order. | ||
| # If using inter-season constraints like seasonal storage or ramp rates, the true sequence | ||
| # must be defined using the time_season_sequential table. Seasonal storage must also be tagged in | ||
| # the technology table. | ||
| # 'seasonal_timeslices' | ||
| # Each season represents a sequential slice of the year, with one or many days represented per | ||
| # season. We assume that the true sequence is the same as the TimeSeason sequence, so the | ||
| # time_season_sequential table can be left empty. Seasonal storage must still be tagged. | ||
| # 'manual' | ||
| # The sequence of time slices is defined manually in the TimeNext table (which is commented out | ||
| # in the schema). This is an advanced feature and not recommended for most users. Seasonal | ||
| # storage must be tagged and the time_season_sequential table filled. | ||
| time_sequencing = 'seasonal_timeslices' | ||
|
|
||
| # How contributions to the planning reserve margin are calculated | ||
| # Options: | ||
| # 'static' | ||
| # Traditional planning reserve formulation. Contributions are independent of hourly availability: | ||
| # capacity value = net capacity * capacity credit | ||
| # 'dynamic' | ||
| # Contributions are available output including a capacity derate factor (e.g., forced outage rate). | ||
| # For most generators, contributions are available (derated) output in each time slice: | ||
| # capacity value = net capacity * reserve capacity derate * capacity factor | ||
| # For storage, contributions are (derated) actual output in each time slice: | ||
| # capacity value = flow out * reserve capacity derate | ||
| reserve_margin = 'static' | ||
|
|
||
| # --------------------------------------------------- | ||
| # MODE OPTIONS | ||
| # options below are mode-specific and will be ignored | ||
| # if the run is not executed in that mode. | ||
| # --------------------------------------------------- | ||
| [MGA] | ||
| slack = 0.1 | ||
| iterations = 4 | ||
| weight = "integer" # currently supported: [integer, normalized] | ||
| weight = "integer" | ||
|
|
||
| [myopic] | ||
| myopic_view = 2 # number of periods seen at one iteration | ||
| myopic_view = 2 |
Oops, something went wrong.
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.
Uh oh!
There was an error while loading. Please reload this page.