MaartenGr / MaartenGr/BERTopic
make verbose mode more verbose
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 7.8k
- Forks
- 920
- Avg merge
- 22h 24m
- Merged PRs (30d)
- 5
Description
Output during a long-running call to fit or transform could be more verbose. Currently we see a logger.info message after certain stages are complete. However, we are not seeing in which stage the process is currently spending time.
Happy to contribute a PR for this.
Contributor 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.
Research direction
Start at the Python entry points for fit and transform, then trace the existing logger.info calls that report completed stages. Define which in-progress stages should be reported and how that output should appear; done means long-running calls identify the stage currently taking time.
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
- Needs clarification
- Newbie friendliness
- 30/100