Skip to content

Commit e7c4409

Browse files
readme update
1 parent 2ea092e commit e7c4409

File tree

1 file changed

+8
-8
lines changed

1 file changed

+8
-8
lines changed

README.md

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -125,13 +125,13 @@ Those embeddings can then be utilized in a novel way thanks to their dim-wise in
125125

126126
## Key technical features of Cleora embeddings
127127
The embeddings produced by Cleora are different from those produced by Node2vec, Word2vec, DeepWalk or other systems in this class by a number of key properties:
128-
- efficiency - Cleora is two orders of magnitude faster than Node2Vec or DeepWalk
129-
- inductivity - as Cleora embeddings of an entity are defined only by interactions with other entities, vectors for new entities can be computed on-the-fly
130-
- updatability - refreshing a Cleora embedding for an entity is a very fast operation allowing for real-time updates without retraining
131-
- stability - all starting vectors for entities are deterministic, which means that Cleora embeddings on similar datasets will end up being similar. Methods like Word2vec, Node2vec or DeepWalk return different results with every run.
132-
- cross-dataset compositionality - thanks to stability of Cleora embeddings, embeddings of the same entity on multiple datasets can be combined by averaging, yielding meaningful vectors
133-
- dim-wise independence - thanks to the process producing Cleora embeddings, every dimension is independent of others. This property allows for efficient and low-parameter method for combining multi-view embeddings with Conv1d layers.
134-
- extreme parallelism and performance - Cleora is written in Rust utilizing thread-level parallelism for all calculations except input file loading. In practice this means that the embedding process is often faster than loading the input data.
128+
- **efficiency** - Cleora is two orders of magnitude faster than Node2Vec or DeepWalk
129+
- **inductivity** - as Cleora embeddings of an entity are defined only by interactions with other entities, vectors for new entities can be computed on-the-fly
130+
- **updatability** - refreshing a Cleora embedding for an entity is a very fast operation allowing for real-time updates without retraining
131+
- **stability** - all starting vectors for entities are deterministic, which means that Cleora embeddings on similar datasets will end up being similar. Methods like Word2vec, Node2vec or DeepWalk return different results with every run.
132+
- **cross-dataset compositionality** - thanks to stability of Cleora embeddings, embeddings of the same entity on multiple datasets can be combined by averaging, yielding meaningful vectors
133+
- **dim-wise independence** - thanks to the process producing Cleora embeddings, every dimension is independent of others. This property allows for efficient and low-parameter method for combining multi-view embeddings with Conv1d layers.
134+
- **extreme parallelism and performance** - Cleora is written in Rust utilizing thread-level parallelism for all calculations except input file loading. In practice this means that the embedding process is often faster than loading the input data.
135135

136136
## Key usability features of Cleora embeddings
137137

@@ -302,4 +302,4 @@ Every `SparseMatrix` object allocates space for:
302302
- `|V|` objects, each occupying 40 bytes,
303303
- `2 x |E|` objects (in undirected graphs we need to count an edge in both directions), each occupying 24 bytes.
304304

305-
During training we need additonal `2 x d x |V|` objects, each occupying 4 bytes (this can be avoided by using memory-mapped files, see `--in-memory-embedding-calculation` argument for the program).
305+
During training we need additonal `2 x d x |V|` objects, each occupying 4 bytes (this can be avoided by using memory-mapped files, see `--in-memory-embedding-calculation` argument for the program).

0 commit comments

Comments
 (0)