why loss=dh*h?
- Dominant language
- C++
- Stars
- 2.9k
- Forks
- 553
- PR merge metrics
- No merged PRs in 30d
Description
As the scalablegcn code shows:
```
def _optimize_store(self, node, node_embeddings):
if not self.gradient_stores:
return tf.zeros([]), tf.no_op()
losses = []
clear_ops = []
for gradient_store, node_embedding in zip(
self.gradient_stores, node_embeddings):
embedding_gradient = tf.nn.embedding_lookup(gradient_store, node)
with tf.control_dependencies([embedding_gradient]):
clear_ops.append(
utils_embedding.embedding_update(gradient_store, node,
tf.zeros_like(embedding_gradient)))
losses.append(tf.reduce_sum(node_embedding * embedding_gradient))
store_loss = tf.add_n(losses)
with tf.control_dependencies(clear_ops):
return store_loss, self.store_optimizer.minimize(store_loss)
```
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reading the _optimize_store method in the scalablegcn code shown and trace how gradient_store and node_embeddings are produced and consumed. Done means providing a clear, evidence-based explanation of the loss expression and documenting it if the project’s conventions support that; no test or file path is identified in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- tensorflow
- Domain
- machine-learning
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100