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

Remove dependency on NetworkPlanner #32

Open
chrisnatali opened this issue Apr 6, 2015 · 1 comment
Open

Remove dependency on NetworkPlanner #32

chrisnatali opened this issue Apr 6, 2015 · 1 comment

Comments

@chrisnatali
Copy link
Contributor

chrisnatali commented Apr 6, 2015

tldr; Networker should no longer be run via the networkplanner_runner module. It should be removed with that functionality (see below) coming from other tools. Networker should only be run via the networker_runner module.

Details

Metrics (i.e. nodal costs) and summary/aggregate calculations still depend on NetworkPlanner's "metric model", "variable store" and "dataset store". All of which add unnecessary complexity and have dependencies on sunsetting library versions (SQLAlchemy 0.6).

Networkers main job of computing an "optimal" network via demand nodes with a budget is sufficiently complex that it invokes the "do one thing well" rule. Therefore, computing metrics and aggregating them is outside the scope of this tool.

@chrisnatali chrisnatali changed the title Handle dependency on NetworkPlanner Remove dependency on NetworkPlanner Feb 26, 2016
@chrisnatali
Copy link
Contributor Author

This is happening in the infrastructure-planning project

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