Error using with PAX using NPE
Hi,
I am getting the following error in GATE:
extracting np PAS!
java.lang.ClassCastException: gate.corpora.DocumentContentImpl cannot be cast to java.lang.String
at info.semanticsoftware.multiPaX.NpParserPaX.getPAS(NpParserPaX.java:48)
at info.semanticsoftware.multiPaX.MultiPaX.execute(MultiPaX.java:195)
at gate.util.Benchmark.executeWithBenchmarking(Benchmark.java:299)
at gate.creole.SerialController.runComponent(SerialController.java:221)
at gate.creole.SerialController.executeImpl(SerialController.java:153)
at gate.creole.SerialAnalyserController.executeImpl(SerialAnalyserController.java:115)
at gate.creole.AbstractController.execute(AbstractController.java:62)
at gate.util.Benchmark.executeWithBenchmarking(Benchmark.java:299)
at gate.gui.SerialControllerEditor$RunAction$1.run(SerialControllerEditor.java:1526)
at java.lang.Thread.run(Thread.java:619)
I have PAX using the "np" NPE Ann Set with both its input and output Ann Sets blank. PAX works fine with "stanford". Any clue as to what the problem is?
- Q
- Login to post comments



Try patching MuNPEx
The version of MuNPEx used in the PAX release is newer than the one on this website. I'll update it sometime this summer, but for a quick fix patch the following lines in the MuNPEx release by adding "toString()" as shown below:
de-lemma.jape:String npLemma = (String)npAnn.getFeatures().get( "HEAD" ).toString();en-lemma.jape:String npLemma = (String)npAnn.getFeatures().get( "HEAD" ).toString();np.jape: features.put( "HEAD", doc.getContent().getContent( headAnn.getStartNode().getOffset(), headAnn.getEndNode().getOffset() ).toString());np.jape: features.put( "MOD", doc.getContent().getContent( modStart, modEnd ).toString() );np.jape: features.put( "DET", doc.getContent().getContent( detAnn.getStartNode().getOffset(), detAnn.getEndNode().getOffset() ).toString());np.jape: features.put( "MOD2", doc.getContent().getContent( mod2Ann.getStartNode().getOffset(), mod2Ann.getEndNode().getOffset() ).toString());Fixed by new MuNPEx release
With any newer MuNPEx version (1.0 and up) this problem should not appear anymore.