DOC-753 | Graph ML UI #709
Conversation
|
Deploy Preview Available Via |
This comment was marked as duplicate.
This comment was marked as duplicate.
| title: ArangoGraphML Web Interface | ||
| menuTitle: ArangoGraphML Web Interface |
There was a problem hiding this comment.
Title to be discussed (we might rename it to just GraphML)
There was a problem hiding this comment.
Yes, I’ve updated the title and menuTitle to "GraphML" as suggested.
| aliases: | ||
| - getting-started-with-arangographml | ||
| --- | ||
| Solve high-computational graph problems with Graph Machine Learning. Apply ML on a selected graph to predict connections, get better product recommendations, classify nodes, and perform node embeddings. Configure and run the whole machine learning flow entirely in the web interface. |
There was a problem hiding this comment.
We only have node classification and embeddings available as immediate options. If we mention something like link predictions, we should at least outline how to achieve that.
Would also be good to have a more technical explanation here about how GraphML works (GraphSage, using depth 2 neighborhood, as mentioned in Slack team channel).
Please also add an overview over the process instead of immediately starting with project creation etc., users should first get an understanding of the hierarchy and steps involved.
There was a problem hiding this comment.
I’ve addressed the points as suggested:
Mentioned only node classification and embeddings as the currently available options.
Added a brief technical explanation of how GraphML works, referencing GraphSAGE with depth 2 neighborhood, based on our Slack discussion and information from the official GraphSAGE site.
Included an overview section at the beginning to explain the overall process, hierarchy, and steps before diving into project creation.
|
|
||
| ## Prediction Phase | ||
|
|
||
| Once the best-performing model has been selected, the final step of the GraphML pipeline is to generate predictions for new or unlabeled data |
There was a problem hiding this comment.
As I explained, we don't have the capability to only process new/unlabeled data
There was a problem hiding this comment.
Updated – Rewrote the section to remove the inaccurate reference to “new or unlabeled data” as suggested.
Replaced it with:
After selecting a model, you can create a Prediction Job. The Prediction Job generates predictions and persists them to the source graph, either in a new collection or within the source documents.
Let me know if any further adjustments are needed.
This comment was marked as duplicate.
This comment was marked as duplicate.
This comment was marked as duplicate.
This comment was marked as duplicate.
This comment was marked as duplicate.
This comment was marked as duplicate.
This comment was marked as duplicate.
This comment was marked as duplicate.
This comment was marked as duplicate.
This comment was marked as duplicate.
This comment was marked as duplicate.
This comment was marked as duplicate.
Description
TODO: Update screenshots due to name change Data Science (Suite) -> GenAI Suite
Upstream PRs