Adam Lally wrote:
On 3/2/07, Michael Baessler <[EMAIL PROTECTED]> wrote:
Adam Lally wrote:
> You can specify both a custom FlowController AND a <fixedFlow> (or
> <capabilityLanguageFlow>) element in your descriptor.  Your
> FlowController will be called but it can access all of the
> AnalysisEngineMetdata from the aggregate descriptor, including the
> fixedFlow and capabilityLanguageFlow sections.

But how can I specify a order for my custom flow? Is this also possible
or do I have to use configuration parameter settings?



Like this:

<analysisEngineDescription xmlns="http://uima.apache.org/resourceSpecifier";>
<frameworkImplementation>org.apache.uima.java</frameworkImplementation>
<primitive>false</primitive>

<delegateAnalysisEngineSpecifiers>
 <delegateAnalysisEngine key="a1">
   <import location="Annotator1.xml"/>
 </delegateAnalysisEngine>
 <delegateAnalysisEngine key="a2">
   <import location="Annotator2.xml"/>
 </delegateAnalysisEngine>
</delegateAnalysisEngineSpecifiers>
<flowController key="MyFlowController">
 <import location="MyFlowController.xml"/>
</flowController>

<analysisEngineMetaData>
<name>Aggregate with custom flow controller</name>
<version>1.0</version>
<vendor>The Apache Software Foundation</vendor>

<flowConstraints>
 <fixedFlow>
   <node>a1</node>
   <node>a2</node>
 </fixedFlow>
</flowConstraints>

</analysisEngineMetaData>
</analysisEngineDescription>


Your custom flow controller in its intialization can query the
<flowContraints> and find out that the sequence is supposed to be a1,
a2; and it can act accordingly.

-Adam

Let me make sure I'm following this. MyFlowController can not know what order analysis engines were specified in in the delegateAnalysisEngineSpecifiers tag, as those are order independent, right? You can then specify a fixedFlow constraint that the flow controller is free to follow or not, also correct?

If that is right, it seems really weird. All we want is to pass a suggestion to the custom flow controller, in the absence of other information, choose this order. Calling that fixedFlow is more than just confusing, it's misleading. You should not be able to specify a fixedFlow with a custom flow controller, for why would you need one when you have a fixed flow?

On the other hand, I'm not even sure what this whole discussion is about, so maybe this is all besides the point ;-)

--Thilo

Reply via email to