Skip to content
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.

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

Classifing commits #166

Open
niloofartrg opened this issue Sep 13, 2019 · 7 comments
Open

Classifing commits #166

niloofartrg opened this issue Sep 13, 2019 · 7 comments

Comments

@niloofartrg
Copy link
Collaborator

Hello,
For classifying commits I need a good amount of labeled commits, and as I understand there are no labels for the DRR commits (except for the tool in the name), so how should I go about it? Thanks. @monperrus

@monperrus
Copy link
Contributor

monperrus commented Sep 15, 2019 via email

@niloofartrg
Copy link
Collaborator Author

but what about the other possibilities? So I just know one of the possible labels.

@monperrus
Copy link
Contributor

monperrus commented Sep 16, 2019 via email

@niloofartrg
Copy link
Collaborator Author

should I predict whether a commit can be generated by a specific repair tool or not, or can it be generated by any repair tool or not? @monperrus

@niloofartrg
Copy link
Collaborator Author

In more details, now I have generated features for all the commits in the DRR correct folder.
So, now I have to fill in a binary table (0,1) with rows corresponding to the commits and the columns corresponding to the repair tools in order to do the ML phase.

My question is that How I should fill in this table?
I can fill the spots where the name of the repair tool is in the file and the identical files, but what about the rest of the table ? should I use the results from the coming project? @monperrus

@monperrus
Copy link
Contributor

monperrus commented Sep 16, 2019 via email

@monperrus
Copy link
Contributor

monperrus commented Sep 16, 2019 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants