Add support for distributed Metrics Visualization
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
Research direction
Start with the README sample visualization for live loss metrics from a PyTorch worker on Ray. Clarify the interface needed for live loss and custom per-model metrics, including how it should work from the PyTorch API on Ray. Done means distributed ML workflows can publish and view those metrics in real time.
Written by the indexing model from the issue text.
Description
The README includes a sample visualization which showcases live loss metrics for a given pytorch worker on ray.
Implement a more general interface for the live publishing of pytorch metrics on raydar, which can help users understand the quality/progress of their distributed ML workflows on Ray in real time. A wishlist of supported features might include:
- Real time loss metrics as distributed training is happening
- Real time custom metrics per-model as distributed training is happening
- Support from within the pytorch api on ray
- Dominant language
- Python
- Stars
- 64
- Forks
- 8
- Avg merge
- 14h 24m
- Merged PRs (30d)
- 2
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Point72/raydar
-
part: dependencies type: bug
Difficulty 3/5 1-2 days Newbie friendliness 25/100
-
Add Better Support for `save_df`Possibly taken @gauglertodd claimed this 749 days ago. Opentype: enhancement
-
Add Support for Prometheus MetricsMay be free again @gauglertodd claimed this 919 days ago, and no pull request is open. Opentype: feature
Similar issues
-
[BUG] HTTP lifecycle dispatch treats a NO_PROXY-only environment as corporate egress and skips the resolve-and-pinned sessionPossibly taken @bodapatisaikrishna claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
external
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
langchain-ai/docs#7652 ·
Maintainers usually reply within 1 day
-
[oblt-aw][autodoc] Document new e2e-secret-leak-artifacts workflow and update e2e-all leaf listOpen
Difficulty 2/5 1-3 hours Newbie friendliness 79/100
elastic/oblt-aw#2513 · 1 comment ·
Maintainers usually reply within 1 day
-
bug p2
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
enhancement
Difficulty 1/5 Under an hour Newbie friendliness 75/100
NCAR/CLM-Tutorial#113 · 1 comment ·
Maintainers usually reply within 1 day