MaartenGr / MaartenGr/BERTopic
Potential Bug for vectorizer_model
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 7.8k
- Forks
- 920
- Avg merge
- 22h 24m
- Merged PRs (30d)
- 5
Description
Hi,
Again, thanks for your amazing work for Bertopic. I used Bertopic for many research projects.
I recently noticed that there may be a tricky bug for vectorizer_model. I checked the code, I found when I pass a cutomised vectorizer_model into BerTopic, the n_gram_range defined in BerTopic class will not be passed to it. Instead, we need to pass both arguments to the vectorizer_model when the vectorizer_model creats.
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 by tracing how BerTopic creates or accepts a custom vectorizer_model and where n_gram_range is handled. Reproduce the behavior with a custom vectorizer and compare it with the default path. Done means the configured n_gram_range is consistently honored for custom vectorizers, with coverage for that case.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- machine-learning
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100