You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This should be something we can turn on/off, since I’m not sure how well it will work and whether we’ll get a lot of false positives.
To keep things comprehensible, we need to keep a map of "stemmed terms" → "actual terms" so that we can present them as the actual terms, even though we are matching by stem.
NLTK supports several different stemming implementations, so I need to do some reading and testing as to what makes the most sense. API docs: https://www.nltk.org/api/nltk.stem.html
The text was updated successfully, but these errors were encountered:
When we check whether any key terms have changed, we should try out using word stemming instead of exact matches:
web-monitoring-task-sheets/analyst_sheets/analyze.py
Lines 190 to 195 in 074cc01
This should be something we can turn on/off, since I’m not sure how well it will work and whether we’ll get a lot of false positives.
To keep things comprehensible, we need to keep a map of "stemmed terms" → "actual terms" so that we can present them as the actual terms, even though we are matching by stem.
NLTK supports several different stemming implementations, so I need to do some reading and testing as to what makes the most sense. API docs: https://www.nltk.org/api/nltk.stem.html
The text was updated successfully, but these errors were encountered: