It works that way too, I tried it with an XMI generated from the C++ annotator and it worked. So the command sytax is correct.
-Rahul On Sat, Feb 18, 2012 at 8:07 PM, Marshall Schor <[email protected]> wrote: > I'm no expert, but isn't the runAECpp command meant to take different > parameters, in perhaps different order? > > Try typing the runAECpp without any parameters. I did that and it said: > > Usage: runAECpp UimaCppDescriptor <-x> InputFileOrDir <OutputDir> > <-s Sofa> <-l LogLevel> > UimaCppDescriptor Analysis Engine descriptor for a CPP annotator > InputFileOrDir Input file or directory of files to process > OutputDir Existing directory for Xmi outputs (optional) > Options: > -x [-xmi] Input(s) must be in XCAS [XMI] format (default is raw text) > -lenient For -xmi, ignore unknown types & features > -s Sofa Name of a Sofa to process (input must be an XCAS or XMI) > -l logLevel Set to 0, 1, or 2 for Message, Warning, or Error > -n numInstances number of annotator instances each running in a separate > thread > -r numRuns number of iterations over the same input. > -rand randomize the selection on next input to process. > -rdelay Max add random delay between 0 and Max milliseconds between > calls to process. > > So it looks to me like you didn't get the parameters in the right way to > the command. > > -Marshall > > > On 2/17/2012 10:23 PM, Rahul Jha wrote: > >> Hi, >> >> I am writing a UIMA annotator in Perl which needs to be integrated with a >> pipeline of annotators primarily written in Java. To test my annotator, I >> write out the XMI from the Java annotator and then try to input it to the >> Perl annotator using: >> >> runAECpp -xmi PerlDescriptor.xml Input.xmi >> >> I made sure to import all the necessary types in PerlDescriptor.xml. >> However, I get the following error: >> ------------------------------**---------- >> runAECPP::Error 5041 XML parse fatal error in >> Exception : unspecified exception >> >> Error number : 5041 >> Recoverable : No >> Error : XML parse fatal error in edu.umich.fuse.fuse.Citation at >> line ??? character ???: ??? >> >> at line 0 character 0: ??? >> ------------------------------**---------- >> >> Any clue as to what might be causing this? >> >> Thanks, >> Rahul >> >> -- http://umich.edu/~rahuljha
