RouteE Compass Road Network

[robfitzgerald]

RouteE Compass can be an optional dependency for HIVE and used in-the-loop as the road network during simulation.

[robfitzgerald]

noticing a challenge here. while building out the logic that converts a RouteE route to a HIVE route, i thought about the energy modeling. it seems like our goal should be to let RouteE Powertrain do the energy simulation in HIVE. when we compute a route, we get that information in the RouteE route. however, HIVE expects us to report energy via the Mechatronics interface. so, when we compute a route via the route method on a RoadNetwork, all we get back is a route, which is a list of LinkTraversal records:

class LinkTraversal(NamedTuple):
    link_id: LinkId
    start: GeoId
    end: GeoId
    distance_km: Kilometers
    speed_kmph: Kmph

nowhere to stash energy information here. probably a good idea too. but does this mean we need to load RouteE Powertrain as a Mechatronics provider? that's probably the right idea. this also creates an opportunity for human error if there is a mismatch between the models used in Compass vs Powertrain.