Chris Roeder | 11 Jan 2011 01:49
Favicon

Identifying failed AE from StatusCallbackListener

Hi,

I'm looking to identify documents whose processing failed for later 
re-processing. I'd also like to identify the failing AE. I'm looking
at StatusCallbackListener.getFailedComponentNames() and getting
"[Process]" back. Could someone more familiar with that part of the
code help enlighten me?

Is this intended to be the AE name? Or is it a more
general concept? Is there some data missing from my
configuration that might be used to fill that field in
with something more useful?

thanks
-Chris

Marshall Schor | 11 Jan 2011 14:50

Re: basic question on sharing results from ./documentAnalyzer.sh demo


On 12/30/2010 12:24 PM, Ted Pedersen wrote:
> PS Just a few details on a second experiment, as there was an
> interesting little twist that initially confused me. This time I just
> used
>
> Analysis Engine : PersonTitleAnnotator.xml
>
> and ran as described below. What was nice about this was that all the
> possible titles as defined in the xml file were shown to me in the CPE
> Gui, so I could review those and remove or add as needed....
>
> But, initially I did not get any titles identified! Instead I got the
> following error....
>
> No output is being produced by the PersonTitleAnnotator because the
> Result Specification did not contain a request for the type
> example.PersonTitle with the language 'x-unspecified'
>   (Note: this message will only be shown once.)

We put in that error message in the 2.3.1 version of the PersonTitleAnnotator -
because others have been hit with this same issue - the annotator previously
just produced nothing, with no message.  You can find out more about results
specification, in the documentation:
http://uima.apache.org/d/uimaj-2.3.1/tutorials_and_users_guides.html#ugr.tug.aae.result_specification_setting

Many annotators ignore the result specification, and produce their output
regardless.  But the PersonTitleAnnotator was written to be more of a tutorial,
teaching example, and has code in it that makes use of it.  You can see this
code here:
(Continue reading)

Eric Riebling | 18 Jan 2011 17:02
Picon
Favicon

Performance Report bug, and best-practices for 'import by name' in CDE

PERFORMANCE REPORT BUG

There appears to be a bug when generating the information after
a CPE completes, that depicts the total processing time.  If there
are more than 1 thread in the CPE, the processing times per thread
are added together, so a 10 threaded setup will report a total time
that is actually 10 times longer than elapsed.

IMPORT BY NAME ISSUES WITH COMPONENT DESCRIPTOR EDITOR

A suggestion to improve by example, relating to "import by name"
- in order for "import by name" to work properly in the Component
Descriptor Editor, imported projects
have to list their descriptors as "Source folders on build path"
such that they get copied (automatically) to the Default output
folder (usually project-name/bin).  This is not the case in the
uimaj-examples project, so anyone using that as a template is
possibly going to be confused in two ways:

  * 'import by name' not working
  * cognitive dissonance: XML descriptors aren't binaries, yet
	they get copied there as such whenprojects are set up
	such that they are listed as Source on build path
	(in order to make 'import by name' work properly)
--

-- 
Eric Riebling  GHC 6713,  LTI,   SCS,  CMU
412.268.9872   http://www.cs.cmu.edu/~er1k

Marshall Schor | 18 Jan 2011 22:32

Re: Performance Report bug, and best-practices for 'import by name' in CDE


On 1/18/2011 11:02 AM, Eric Riebling wrote:
> PERFORMANCE REPORT BUG
>
> There appears to be a bug when generating the information after
> a CPE completes, that depicts the total processing time.  If there
> are more than 1 thread in the CPE, the processing times per thread
> are added together, so a 10 threaded setup will report a total time
> that is actually 10 times longer than elapsed.
>
> IMPORT BY NAME ISSUES WITH COMPONENT DESCRIPTOR EDITOR
>
> A suggestion to improve by example, relating to "import by name"
> - in order for "import by name" to work properly in the Component
> Descriptor Editor, imported projects
> have to list their descriptors as "Source folders on build path"
> such that they get copied (automatically) to the Default output
> folder (usually project-name/bin).  This is not the case in the
> uimaj-examples project, so anyone using that as a template is
> possibly going to be confused in two ways:
>
>  * 'import by name' not working
>  * cognitive dissonance: XML descriptors aren't binaries, yet
>     they get copied there as such whenprojects are set up
>     such that they are listed as Source on build path
>     (in order to make 'import by name' work properly)

Re: the confusion around import-by-name in the uimaj-examples project: You are
right.  This was all set up a long time ago, before we even had import-by-name,
as I recall.
(Continue reading)

Ajnabee Parinda | 19 Jan 2011 04:27
Picon

Issues building and running pythonnator under Windows

I'm having some issues building and running pythonnator. I've followed the
instructions and am able to build the pythonnator successfully with the
instructions specified in the python.html file. I then copied over the
_pythonnator.dll, pythonnator.py and sample.py files to %UIMACPP_HOME%\bin,
which is on PYTHONPATH. However, when I run the runAEcpp command with the
PythonSample.xml as the descriptor and a sample input file, I get the
following errors:

Pythonnator: Initialize - debug=101
Pythonnator:sample: failed to import pythonnator module, PYTHONPATH problem?
Pythonnator: destroy
Exception exceptions.ImportError: 'No module named _pythonnator' in 'garbage
collection' ignored
Fatal Python error: unexpected exception during garbage collection

This happens with both Python 2.4 and 2.5. I'm at my wit's end trying to
resolve this issue. Can anybody please help me with this?

Regards.
Eddie Epstein | 20 Jan 2011 00:14
Picon

Re: Issues building and running pythonnator under Windows

As a sanity check, keep all the files in %uimacpp_home%\scriptators\python
and try runaecpp pythonsample.xml ..\..\examples\data
This should run a few documents and find annotations in some.

I get the same error as you if pythonnator.py is moved to another directory.
However, all works again for me if PYTHONPATH points to that directory.

Here's all the python in my environment:

C:\temp\apache-uima\uimacpp\scriptators\python>set | grep PYTH
PYTHONPATH=C:\temp\apache-uima\uimacpp\scriptators\python\SAVE
PYTHON_INCLUDE=\Python24\include
PYTHON_LIB=\Python24\lib
PYTHON_LIBDIR=\Python24\libs

Eddie

On Tue, Jan 18, 2011 at 10:27 PM, Ajnabee Parinda
<ajnabee.parinda@...> wrote:
> I'm having some issues building and running pythonnator. I've followed the
> instructions and am able to build the pythonnator successfully with the
> instructions specified in the python.html file. I then copied over the
> _pythonnator.dll, pythonnator.py and sample.py files to %UIMACPP_HOME%\bin,
> which is on PYTHONPATH. However, when I run the runAEcpp command with the
> PythonSample.xml as the descriptor and a sample input file, I get the
> following errors:
>
> Pythonnator: Initialize - debug=101
> Pythonnator:sample: failed to import pythonnator module, PYTHONPATH problem?
> Pythonnator: destroy
(Continue reading)

Peter Klügl | 20 Jan 2011 13:40
Picon
Favicon

CAS Editor type system questions

  Hello,

when using the CAS Editor I have two problems and I want to ask if I'm 
doing something wrong:

I can't open a xmi if it contains annotations of types that are not 
defined in the specified type system.

If I specify a type system in a CAS Editor project that imports other 
types system (by location), then the editor does not open correctly, 
especially if the xmi contains types of the imported type systems.

Thanks,

Peter

--

-- 
---------------------------------------------------------------------
Dipl.-Inf. Peter Klügl
Universität Würzburg        Tel.: +49-(0)931-31-86741
Am Hubland                  Fax.: +49-(0)931-31-86732
97074 Würzburg              mail: pkluegl@...
      http://www.is.informatik.uni-wuerzburg.de/en/staff/kluegl_peter/
---------------------------------------------------------------------

Jörn Kottmann | 20 Jan 2011 13:49
Picon

Re: CAS Editor type system questions

On 1/20/11 1:40 PM, Peter Klügl wrote:
>  Hello,
>
> when using the CAS Editor I have two problems and I want to ask if I'm 
> doing something wrong:
>
> I can't open a xmi if it contains annotations of types that are not 
> defined in the specified type system.
>
Yes, that is a limitation which is there. Maybe it is possible to open a 
CAS even when types it contains
are not in the type system. Not sure about that. Would it be important 
for you to change that ?

> If I specify a type system in a CAS Editor project that imports other 
> types system (by location), then the editor does not open correctly, 
> especially if the xmi contains types of the imported type systems.
That sounds like a bug to me. Did you use the Cas Editor project ? There 
is also support now to open CAS files which
are not in a Cas Editor project, in this case the type system is either 
located in a default location, or it ask for a type system
to use.

Jörn

Thilo Götz | 20 Jan 2011 13:58
Picon
Picon

Re: CAS Editor type system questions

On 1/20/2011 13:49, Jörn Kottmann wrote:
> On 1/20/11 1:40 PM, Peter Klügl wrote:
>>  Hello,
>>
>> when using the CAS Editor I have two problems and I want to ask if I'm doing
>> something wrong:
>>
>> I can't open a xmi if it contains annotations of types that are not defined in
>> the specified type system.
>>
> Yes, that is a limitation which is there. Maybe it is possible to open a CAS
> even when types it contains
> are not in the type system. Not sure about that. Would it be important for you
> to change that ?

I think (not sure though) that you can somehow open an XMI
file with data that's not in the type system, and populate
the CAS only with the known data without throwing an error.

--Thilo

> 
>> If I specify a type system in a CAS Editor project that imports other types
>> system (by location), then the editor does not open correctly, especially if
>> the xmi contains types of the imported type systems.
> That sounds like a bug to me. Did you use the Cas Editor project ? There is also
> support now to open CAS files which
> are not in a Cas Editor project, in this case the type system is either located
> in a default location, or it ask for a type system
> to use.
(Continue reading)

Peter Klügl | 20 Jan 2011 14:00
Picon
Favicon

Re: CAS Editor type system questions

  Hello Jörn,

Am 20.01.2011 13:49, schrieb Jörn Kottmann:
> On 1/20/11 1:40 PM, Peter Klügl wrote:
>>  Hello,
>>
>> when using the CAS Editor I have two problems and I want to ask if 
>> I'm doing something wrong:
>>
>> I can't open a xmi if it contains annotations of types that are not 
>> defined in the specified type system.
>>
> Yes, that is a limitation which is there. Maybe it is possible to open 
> a CAS even when types it contains
> are not in the type system. Not sure about that. Would it be important 
> for you to change that ?
>

The importance is relative. We will probably use the CAS Editor to 
annotate stuff and in my use cases there are always annotations of 
unknown types present. On the other hand, I can also do some workaround 
for that problem.

>> If I specify a type system in a CAS Editor project that imports other 
>> types system (by location), then the editor does not open correctly, 
>> especially if the xmi contains types of the imported type systems.
> That sounds like a bug to me. Did you use the Cas Editor project ? 
> There is also support now to open CAS files which
> are not in a Cas Editor project, in this case the type system is 
> either located in a default location, or it ask for a type system
(Continue reading)


Gmane