Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fast PyG Data Object for Dynamic Node Label / Features #19

Closed
shenyangHuang opened this issue Apr 26, 2023 · 1 comment · Fixed by #30
Closed

Fast PyG Data Object for Dynamic Node Label / Features #19

shenyangHuang opened this issue Apr 26, 2023 · 1 comment · Fixed by #30

Comments

@shenyangHuang
Copy link
Owner

implement fast and efficient data object in PyG for dynamic node label / features, a few key characteristics as below. Node label and node feature can be treated interchangeably here as they are both vectors.

  • should support tuple like representation (time, node id, node label vector).
  • [!] not all nodes have labels for all timestamps
  • [!] node label timestamps are often more coarse grain than edge timestamps and there might not be edges that share timestamp of the node labels
  • should update or remove find_next_labels_batch function in dataset.py
  • node labels should be broken down into days (or a fixed time intervals depending on the application)
  • if no node label for a given day, return None when querying the dataset object
@shenyangHuang
Copy link
Owner Author

shenyangHuang commented May 1, 2023

As an improved approach, try the following:

  • construct a dict of node labels where key is the unix_timestamp of the day, item = (node_id, node_label_vec)
  • ensure the timestamps of the node labels are assigned correctly, the day labels are shift by 1 as the edges from the day are used to predict the future (double check)
  • find_next_labels_batch function in dataset.py should now be improved to query the nearest timestamp in the batch or signaled by the edgelist

@shenyangHuang shenyangHuang linked a pull request May 8, 2023 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant