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

Features/#553 motorized individual travel #588

Merged
merged 28 commits into from
Jun 22, 2022

Conversation

nesnoj
Copy link
Member

@nesnoj nesnoj commented Dec 20, 2021

Closes #553

Includes #720
Requires #760 #799

Before merging into dev-branch, please make sure that

  • the CHANGELOG.rst was updated.
  • new and adjusted code is formated using black and isort.
  • the Dataset-version is updated when existing datasets are adjusted.
  • the branch was merged into the continuous-integration/run-everything-over-the-weekend- branch.
  • the workflow is running successful in test mode.
  • the workflow is running successful in Everything mode.

@nesnoj nesnoj added the 🏗️ integration Integrating a data processing step label Dec 20, 2021
@nesnoj nesnoj self-assigned this Dec 20, 2021
nesnoj added 3 commits May 31, 2022 07:29
* use EV driving load instead of charging load
* add SoC max and min constraints for EV battery and remove old DSM profile
@ClaraBuettner
Copy link
Contributor

In commit 1ee94f4 I added the dependencies to avoid problems with the etrago_ids. Could you cherry-pick this commit?

nesnoj added 23 commits June 1, 2022 18:04
Prior to this fix, the trip data was duplicated which lead to poor performance in timeseries generation due to newly loaded driving times for SoC costraints. Now the timeseries are generated for unique EVs only and subsequently scaled with the EV quantities.
The tasks for model data generation are dynamically generated using a predefined bunch size. An additional task for each scenario handles the remaining grid districts using the real number/ids of the grid districts.
* Split large session transaction into single transactions for each table
* Move those transactions to functions to handle the unique error handling correctly
* Temporarily pimp wrapper check_db_unique_violation() to retry 10 times when deadlock exception is raised
* Add a 3s sleep between retries
@nesnoj nesnoj marked this pull request as ready for review June 22, 2022 10:19
@nesnoj
Copy link
Member Author

nesnoj commented Jun 22, 2022

I'll now merge this one, as

  • most of it is already in the dev,
  • it has been successfully tested for SH and DE multiple times.
  • as Features/#760 zenodo v0.8 #805 has been merged, the eMob data diverged

However, the error handling which was introduced in 157e29a in check_db_unique_violation() should be streamlined, see #816.

However, #799 should be solved quickly.

@nesnoj nesnoj merged commit ad64942 into dev Jun 22, 2022
@nesnoj nesnoj deleted the features/#553-motorized-individual-travel branch June 22, 2022 11:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🏗️ integration Integrating a data processing step
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Integrate eMobility: motorized individual travel
2 participants