Mailing-List: contact user-help@uima.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@uima.apache.org
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
Subject: Re: Wrong CAS being passed on in AAE
From: Martin Wunderlich <martin_wu@gmx.net>
In-Reply-To: <8AE27C2A-DDF2-4DAA-9D75-B3FEAA1A2BB6@apache.org>
Date: Thu, 27 Aug 2015 10:10:09 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <F509F06A-E9D8-4FCB-9028-AF96B6D11937@gmx.net>
References: <DE5C610F-06A1-4342-8870-C8795AD04282@gmx.net>
 <CAMjp+0cem192M+kwS1eVwB_dxoBm2xFpSq_i-xrntC1r4nhROQ@mail.gmail.com>
 <F5914B30-A1C9-4837-972F-B11D1F3BAB46@apache.org>
 <A7FE463C-CCE9-4E52-8A3C-F06BA905E55E@gmx.net>
 <7A778A0A-5E15-4191-A6DF-70ED77A14828@apache.org>
 <86F7FF37-EFFC-4483-97CA-DB26CE315914@gmx.net>
 <8AE27C2A-DDF2-4DAA-9D75-B3FEAA1A2BB6@apache.org>
To: user@uima.apache.org


> Am 26.08.2015 um 23:11 schrieb Richard Eckart de Castilho =
<rec@apache.org>:
>=20
>=20
> On 26.08.2015, at 22:58, Martin Wunderlich <martin_wu@gmx.net> wrote:
>=20
>> Kinda like this. It=92s bit more involved, because I was trying to =
spare you the details.=20
>>=20
>> First AAE: (FC AE AE AE AE AE AE)
>>=20
>> Second AAE: (AE AE AE AE AE)
>>=20
>> This does not work: AAE*[ CR AAE (FC AE AE AE AE AE AE) AAE (AE AE AE =
AE AE) ]
>>=20
>> This _does_ work: AAE*[ CR AAE (FC AE AE AE AE AE AE AE AE AE AE AE) =
]
>>=20
>> FC =3D FlowControlloer
>> RR =3D CollectionReader
>=20
> The CR is always outside the AAE - it is handled separately.
>=20
>> This does not work:CR AAE*[AAE (FC AE AE AE AE AE AE) AAE (AE AE AE =
AE AE) ]
>>=20
>> This _does_ work: CR AAE*[AAE (FC AE AE AE AE AE AE AE AE AE AE AE) ]
>=20
> Basically SimplePipeline.runPipeline does (with a few details left =
out):
>=20
> aae =3D createEngine(aed, aed, aed...)
> for (cas : createReader(crd) {
>  aae.process(cas);
> }
>=20
> I may have an idea why the first case does not work. Does the AAE
> define the flag "outputsNewCases" =
(org.apache.uima.resource.metadata.OperationalProperties)?
>=20
>  /**
>   * Sets whether this AnalysisEngine may output new CASes. If this =
property is set to true, an
>   * application can use the {@link =
AnalysisEngine#processAndOutputNewCASes(CAS)} to pass a CAS to
>   * this this AnalysisEngine and then step through all of the output =
CASes that it produces. For
>   * example, such an AnalysisEngine could segment a CAS into smaller =
pieces, emitting each as a
>   * separate CAS.
>   *=20
>   * @param aOutputsNewCASes
>   *          true if this component may output new CASes, false if it =
does not
>   */
>  public void setOutputsNewCASes(boolean aOutputsNewCASes);
>=20
> uimaFIT doesn't do that, you'd have to do that manually just as you =
also tweak the flow.

Correct: On the last step of the first AAE (a CAS merger) I have set =
this flag to true, so that the merged CAS gets output (and the CASes =
feeding into the Merger get dropped, as per the FC).=20

So, you mean that this setting is ignored by uimaFit when applying the =
SimplePipeline? That would explain why the correct output is missing.=20

Cheers,=20

Martin
=20


>=20
> Maybe there could be some way to infer this setting by detecting that =
a CAS multipler
> is inside an AAE... but then again, probably UIMA core should infer =
that, not uimaFIT.
>=20
> Cheers,
>=20
> -- Richard