lmcinnes / lmcinnes/umap

How to look at the loss value?

Open
#100 9 comments 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
Python
Stars
8.3k
Forks
871
Avg merge
1d 13h
Merged PRs (30d)
5

Description

Is there a possibility to print the loss value during the optimization process? Or at least after the last epoch?

It would make sense to add this feature, as it would help to set an appropriate number of epochs when one tunes the algorithm for specific data.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No file, test, or entry point is named in the issue. Start by locating the optimization loop and its epoch handling, then determine how the loss value can be exposed or printed during optimization or after the final epoch. Done means users can inspect the loss while tuning the number of epochs.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
machine-learning
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.