Closed IngoScholtes closed 6 months ago
I have written a new lift_order
function that does not suffer from these issues, see notebook temporal_shortest_paths.ipynb
in the tutorials folder in the linked branch temporal-paths-mem-efficient.
Side notes:
torch_cartesian_prod
to generate all ordered pairs of source and target edge indices within the current time window, which might also be useful to suplify the general lift_order code
The current code to calculate temporal paths in a TemporalGraph suffers from explosive memory usage, which crashes the kernel. Also, despite using the GPU it is not efficient due to the intermediate calculation of all pairs of edges irrespective of their timestamps.