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
I've spent the last three days pouring through the documentation with the goal of building a SpatioTemporalDataset, and while I think I understand most parts of the library, I'm stuck on whether it's possible to implement a dynamic graph topology in a SpatioTemporalDataset.
My understanding is that I can set the edge connections and weights through SpatioTemporalDataset.set_connectivity() but it only accept objects that are not indexed by time. However I do see the Data class contains functionality to pass lists into edge_index, presumably indexed by time. Since SpatioTemporalDataset creates samples of Data objects, it seems like it could be possible to express the graph topology changing with time, or am I misunderstanding something?
Going through this package and its documentation has been super educational for me, thanks for putting in all the hard work to build!
The text was updated successfully, but these errors were encountered:
I've spent the last three days pouring through the documentation with the goal of building a
SpatioTemporalDataset
, and while I think I understand most parts of the library, I'm stuck on whether it's possible to implement a dynamic graph topology in aSpatioTemporalDataset
.My understanding is that I can set the edge connections and weights through
SpatioTemporalDataset.set_connectivity()
but it only accept objects that are not indexed by time. However I do see theData
class contains functionality to pass lists intoedge_index
, presumably indexed by time. SinceSpatioTemporalDataset
creates samples ofData
objects, it seems like it could be possible to express the graph topology changing with time, or am I misunderstanding something?Going through this package and its documentation has been super educational for me, thanks for putting in all the hard work to build!
The text was updated successfully, but these errors were encountered: