10000 Getting misclassified instances from AnnotationStatistics · Issue #358 · ClearTK/cleartk · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Getting misclassified instances from AnnotationStatistics #358

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
bethard opened this issue Apr 15, 2015 · 4 comments
Open

Getting misclassified instances from AnnotationStatistics #358

bethard opened this issue Apr 15, 2015 · 4 comments
Labels
Component-eval ⭐️ Enhancement New feature or request Priority-Medium
Milestone
⭐️ Feature backlog

Comments

@bethard
Copy link
Contributor
bethard commented Apr 15, 2015

Original issue 360 created by ClearTK on 2013-04-15T14:04:34.000Z:

I believe that it could be useful to store actual misclassified cases in AnnotationStatistics as well as counts which are currently stored. This could be optional to reduce memory requirement when users don't want to see these cases. If it would be useful to anybody except me, I could provide a patch.
@bethard
Copy link
Contributor Author
bethard commented Apr 15, 2015

Comment #1 originally posted by ClearTK on 2013-04-16T15:44:27.000Z:

We can't store Annotation objects in AnnotationStatistics since Annotation objects will be invalidated when the CAS is reset on each CollectionReader.getNext call. So what exactly would we be storing? The coveredText? All the Annotation's features? My feeling is that each user is going to want to keep something different around.

But maybe we make it easier to subclass and store whatever information you want? Is there some change to AnnotationStatistics that would make this kind of subclass easier to write?

@bethard
Copy link
Contributor Author
bethard commented Apr 15, 2015

Comment #2 originally posted by ClearTK on 2013-04-16T18:21:00.000Z:

Yes, but I'll need to think a bit about how to do it, it isn't quite as simple as I originally thought.
8000

@bethard
Copy link
Contributor Author
bethard commented Apr 15, 2015

Comment #3 originally posted by ClearTK on 2013-05-03T08:44:33.000Z:

<empty>

@bethard
Copy link
Contributor Author
bethard commented Apr 15, 2015

Comment #4 originally posted by ClearTK on 2014-03-15T17:41:52.000Z:

<empty>

@bethard bethard modified the milestone: 2.2 Apr 16, 2015
@reckart reckart modified the milestones: 3.0.0, ⭐️ Feature backlog Nov 4, 2022
@reckart reckart added ⭐️ Enhancement New feature or request and removed Type-Enhancement labels Nov 4, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Component-eval ⭐️ Enhancement New feature or request Priority-Medium
3CB0
Projects
None yet
Milestone
⭐️ Feature backlog
Development

No branches or pull requests
2 participants
@bethard @reckart
0