Currently, SMO coding is broken because of the way that NLTK handles classpaths. Throws the following:
Exception in thread "main" java.lang.NoClassDefFoundError: org/slf4j/LoggerFactory
at edu.stanford.nlp.io.IOUtils.<clinit>(IOUtils.java:42)
at edu.stanford.nlp.ie.AbstractSequenceClassifier.loadClassifier(AbstractSequenceClassifier.java:1484)
at edu.stanford.nlp.ie.AbstractSequenceClassifier.loadClassifierNoExceptions(AbstractSequenceClassifier.java:1497)
at edu.stanford.nlp.ie.crf.CRFClassifier.main(CRFClassifier.java:3015)
This is a known issue with NLTK. In addition, StanfordNERTagger is going to be replaced by CoreNLPTagger in NLTK 3.2.5. We need to phase out its use and still have the ability to use a model trained on MPEDS training data.
Currently, SMO coding is broken because of the way that NLTK handles classpaths. Throws the following:
This is a known issue with NLTK. In addition, StanfordNERTagger is going to be replaced by CoreNLPTagger in NLTK 3.2.5. We need to phase out its use and still have the ability to use a model trained on MPEDS training data.