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:53:00 UTC
[jira] [Updated] (UIMA-6017) uv3 make cascompare more useful by
eliminating duplicate reporting
[ https://issues.apache.org/jira/browse/UIMA-6017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marshall Schor updated UIMA-6017:
---------------------------------
Description:
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.
Also, remove code that was conditionally sorting some collections during compare - this broke other code and isn't needed - any sorting should be done before this routine is called.
was:
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.
> 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
> Priority: Minor
> 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.
> Also, remove code that was conditionally sorting some collections during compare - this broke other code and isn't needed - any sorting should be done before this routine is called.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)