Upload DATASETS_README.md with huggingface_hub
Browse files- DATASETS_README.md +17 -0
DATASETS_README.md
ADDED
@@ -0,0 +1,17 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
1 |
+
## Descriptions of data files in the paper *Towards Better Evaluation for Dynamic Link Prediction*
|
2 |
+
|
3 |
+
The original networks are saved as <network>.csv.
|
4 |
+
|
5 |
+
The networks are formatted as follows:
|
6 |
+
* Each edge is denoted in one line.
|
7 |
+
* Each line has the following format: source_node, destination_node, timestamp, edge_label, comma-separated arrays of edge features.
|
8 |
+
* Please note that if there is no edge label available, the edge_label column will be filled with 0s only for loading purpose; these labels are not used in the link prediction task.
|
9 |
+
* The first line denotes the network format.
|
10 |
+
* Edge features should include at least one feature. If there is no edge feature available, a 0 value is used for all the edges.
|
11 |
+
|
12 |
+
The network edge-lists can be pre-processed by ```preprocess_data/preprocess_data.py```.
|
13 |
+
After pre-processing the network edge-list, there are three files that are used by the models:
|
14 |
+
* <ml_network>.csv: this file contains the timestamp edge-list.
|
15 |
+
* <ml_network>.npy: this file contains the edge features in the dense `npy` format that has the features in binary format.
|
16 |
+
* <ml_network_node>.npy: this file contains the node features in the dense `npy` format that contains the node features in binary format.
|
17 |
+
Please note that when the edge features or node features are absent, we use a vector of zeros is used as the node/edge features in line with the baseline methods.
|