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
I'm getting case sensitive mapping results even though I'm using an index built with --lowercase.
To reproduce.
index with UMLS 2018AA and -L (lowercase)
test code:
from quickumls import *
matcher = QuickUMLS('/quickumls-data-2018AA')
text ='Name.'
for p in matcher.match(text, best_match=True, ignore_syntax=False):
for q in p:
print(q)
Turns out SpaCy folks got a bit to aggressive with the definition of stopwords, as "name" is now included in their list. Switched to NLTK in QuickUMLS 1.2.4 to fix this issue. Sorry it took me a while to get to this!
I'm getting case sensitive mapping results even though I'm using an index built with
--lowercase
.To reproduce.
-L
(lowercase)Result is:
But if
text = 'Name.'
is changed totext = 'name.'
result is empty.Similarly, if
text = 'Patient Name.'
then result is:And if `text = 'Patient name.', the result is:
(Note the
name
part is ignored.)The text was updated successfully, but these errors were encountered: