MaartenGr / MaartenGr/BERTopic
Modeling taking a long time after progress bar complete
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 7.8k
- Forks
- 920
- Avg merge
- 22h 24m
- Merged PRs (30d)
- 5
Description
I was surprised that my model was taking over 8 hours to run, so I set 'verbose = True' to monitor the progress. I was surprised to see that the progress bar completed within an hour, but the cell was left running for over several hours after (and still is). I've added a screenshot of my code and output for reference. I don't believe the problem to be from saving the model, because if I end the cell process and try to use the model it will say it does not exist.
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 with the code and output shown in the attached screenshot, reproducing the run with verbose=True. Compare the point where the progress bar completes with the remaining cell execution and determine which operation prevents the model from becoming available. Done means the post-progress delay is explained and the reported behavior is fixed or clearly documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- machine-learning
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100