Skip to content

Add presets to seperate building the grids from optimizing them - #744

Draft
ClaraBuettner wants to merge 1 commit into
devfrom
features/#742-preset-for-prebuilding-grids
Draft

Add presets to seperate building the grids from optimizing them#744
ClaraBuettner wants to merge 1 commit into
devfrom
features/#742-preset-for-prebuilding-grids

Conversation

@ClaraBuettner

Copy link
Copy Markdown

Description

Introduces two new presets:

  • prepare_and_save_grid
  • optimize_prebuild_grids

The first one creates the grid and adds all components for the scenario and saves it into the given directory.
The second one imports a grid build with the previous preset, adds overlying grid data, selects relevant timesteps and optimizes the grid.
This way, calculation time can be reduced and the distribution of charging points (see #742) is the same in different model runs.

Could be a solution for #742

Warning: Line

path: "/hdd-disk/ego-results/prepared_grids"
still includes a hard-coded path because I didn't know how to wire it to edisgo correctly.

@joda9 and @MoritzSchloesser: Feel free to close this PR if you want to fix this differently :)

Type of change

Please delete options that are not relevant.

  • New feature (non-breaking change which adds functionality)

Checklist:

  • New and adjusted code is formatted using the pre-commit hooks
  • New and adjusted code includes type hinting now
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes
  • The Read the Docs documentation is compiling correctly
  • If new packages are needed, I added them the setup.py, and if needed the rtd_requirements.txt, the eDisGo_env.yml and the eDisGo_env_dev.yml.
  • I have added new features to the corresponding whatsnew file

This way, calculation time can be reduced and the distribution of charging points
(see #742) is the same in different model runs.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant