Closed LaurentBerder closed 1 year ago
I realize that my mistake was to combine everything in numpy arrays, while it should remain lists of arrays.
Deleting the lines in _get_edges()
and _get_targetsand_features()
where I combined the lists into arrays, I get rid of the error when building the DynamicGraphTemporalSignal
.
Hi,
First of all, thanks a lot for all the work you've put in the library, it's really amazing.
I'm working on a project with a set of edges and nodes both containing features, with static node features (their values are constant over time), but with dynamic edge features (their values change over time). And the target nodes are also dynamic: I'm planning a node feature regression over a few timesteps in the future.
I'm having a hard time figuring out what kind of signal would suit my needs best. I see that ChickenpoxDatasetLoader is not appropriate as everything is static there, so probably more something in the line of METRLADatasetLoader which is a
StaticGraphTemporalSignal
.So I tried taking inspiration from this example which uses METRLA. But it only seems to take node data into account and I see no mention of the edges and their potential features.
I saw in #84 an interesting rewrite of the dataloader, so tried myself out and came up with the following:
As you can see, I have the following figures:
I cannot seem to find information on which shape to construct my nodes & edge objects for them to be inputs to a Signal object.
My intention is building a signal where each time step is a
torch_geometric
graph, like so: