Skip to content
This repository has been archived by the owner on Jun 7, 2023. It is now read-only.

C-BERT: Run on single Libtiff commit for manual analysis #38

Closed
lucaburatti7 opened this issue Jan 26, 2022 · 5 comments
Closed

C-BERT: Run on single Libtiff commit for manual analysis #38

lucaburatti7 opened this issue Jan 26, 2022 · 5 comments
Assignees
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.

Comments

@lucaburatti7
Copy link

  1. get ranked list from ML models
  2. get list ranked list from C-BERT
  3. compare and report results here.
@sesheta
Copy link

sesheta commented Apr 27, 2022

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@sesheta sesheta added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 27, 2022
@lucaburatti7
Copy link
Author

lucaburatti7 commented Apr 27, 2022

1 and 2 completed.
3: from manual analysis on libtiff commit
Label: 0 ? 1 s 1+s
------------------

cbert2 8 1 1 0 1
cbert2sec 7 2 1 0 1
cbert1 3 3 0 4 4
cbert1sec 5 1 0 4 4

where s = TP but safe (typically integer overflow).
so we can conclude that it's hard to choose a "best" model. Cbert2 finds 1 real TP but at the cost of more 0, while Cbert1 is better overall but finds only "safe" TP

@sesheta
Copy link

sesheta commented May 27, 2022

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

/lifecycle rotten

@sesheta sesheta added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels May 27, 2022
@sesheta
Copy link

sesheta commented Jun 27, 2022

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close

@sesheta
Copy link

sesheta commented Jun 27, 2022

@sesheta: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@sesheta sesheta closed this as completed Jun 27, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.
Projects
None yet
Development

No branches or pull requests

3 participants