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

Consolidate scenarios / minimize code duplication for choice models #62

Open
sebhoerl opened this issue Jul 21, 2020 · 0 comments
Open

Comments

@sebhoerl
Copy link
Collaborator

A lot of the choice model code is duplicated across the scenarios. There are some options to go forward:

  • Remove different city projects altogether and have one general eqasim RunSimulation that works on all scenarios (with custom parameters, settings, etc.)
  • Keep the city projects but maybe move the general "does it all" choice model into a separate project

The reason is that I would, for instance, now like to use the ASTRA Zurich choice model for Paris, but it is not so easy, because there is a lot of implementational overhead. Whether to remove the city projects depends a bit pn how individual all the code around the choice model is (but I think there are not many individual components).

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

No branches or pull requests

1 participant