You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by "Marshall Schor (JIRA)" <de...@uima.apache.org> on 2019/03/29 17:51:00 UTC
[jira] [Created] (UIMA-6017) uv3 make cascompare more useful by
eliminating duplicate reporting
Marshall Schor created UIMA-6017:
------------------------------------
Summary: uv3 make cascompare more useful by eliminating duplicate reporting
Key: UIMA-6017
URL: https://issues.apache.org/jira/browse/UIMA-6017
Project: UIMA
Issue Type: Improvement
Components: Core Java Framework, Tools
Affects Versions: 3.0.1SDK
Reporter: Marshall Schor
Fix For: 3.0.2SDK
When using the cas compare to discover the root cause of two CASs miscomparing, it is helpful to exclude showing miscompares that are caused by already reported miscompares.
For example, if you have some collection of Feature Structures, and one of them miscompares and you report that, it is helpful to not also report the two collections are miscomparing.
If you don't exclude these "upper level" miscompares from reporting, there are typically so many reported miscompares, that it's hard to focus on the root cause.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)