Mailing-List: contact user-help@uima.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@uima.apache.org
From: Mario Juric <mj@unsilo.ai>
Content-Type: multipart/alternative;
 boundary="Apple-Mail=_626305E2-1C9D-4761-B98A-30B4E2044A5F"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: uimaFit JCasUtil.selectAt meaning
Message-Id: <A6633AB2-ABBF-438C-BFCF-5A9C4C9A08E0@unsilo.ai>
Date: Wed, 1 Nov 2017 17:02:33 +0100
To: user@uima.apache.org
archived-at: Wed, 01 Nov 2017 16:02:58 -0000

--Apple-Mail=_626305E2-1C9D-4761-B98A-30B4E2044A5F
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Hi,

I was wondering what exactly the semantics of JCasUtil.selectAt is =
supposed to be after looking into the implementation, since the JavaDoc =
isn=E2=80=99t very precise. I initially thought that it would select =
annotations of the given type with the exact begin and end, but this is =
not the case when inspecting the implementation. The problem is in =
CasUtil.selectAt with the following while loop:

while (it.isValid()) {
  AnnotationFS a =3D it.get();
  // If the offsets do not match the specified offets, we're done
  if (a.getBegin() !=3D aBegin && a.getEnd() !=3D aEnd) {
    break;
  }
  it.moveToNext();
  list.add(a);
}

I would have expected that either begin or end must be different to drop =
the item, i.e. "if (a.getBegin() !=3D aBegin || a.getEnd() !=3D aEnd)" =
instead. This is obviously not the case, and it does not have the same =
behaviour like selectCovered either, so what is the intend if it=E2=80=99s=
 not a bug?

Best,
Mario


--Apple-Mail=_626305E2-1C9D-4761-B98A-30B4E2044A5F--