Replies: 1 comment 1 reply
-
I don't think this necessarily requires a heterogeneous graph. I am not an expert on this topic, but wouldn't it make more sense to see each "Stop" as a node, such that you regress the delay per node (which also removes the need to deal with varying sizes of features). |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi all, I'm trying to work on a delay prediction transport problem, where different services are different nodes in the graph. I'm trying to predict the delay at future stops for a service, given its timetable, and its observed arrival and departure times up to the current timestep.
In a simple case this node data might be:
Where the goal is to predict the times marked by ?. Services are linked if they share any stops within a certain period, and have a higher weight if they share more stops, or if the timetabled departure for the shared stop is closer together.
I'm interested in a graph where services are the nodes, as it should be agnostic of the stop geometry, and hopefully allow for better propagation of delays between different services.
I've looked at works with STGCNS as well as feature propagation for node feature completion but am struggling to make any headway given the varying size of node schedule features.
Will it be necessary to use a heterogenous graph for this or is there any elegant solutions that i'm missing? Similarly, I suspect that encoding the shared stops and the expected time between arrivals in links would yield better performance than just a weight, but again this would result in non uniform features on the links, given different services share different numbers of stops.
Any help or relevant works to read over would be greatly appreciated! Thanks!
Beta Was this translation helpful? Give feedback.
All reactions