You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
chrisnatali
changed the title
Handle dependency on NetworkPlanner
Remove dependency on NetworkPlanner
Feb 26, 2016
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.
The text was updated successfully, but these errors were encountered: