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

Adding contaminated data to randomly produce conflicts #21

Open
igrangel opened this issue May 26, 2017 · 7 comments
Open

Adding contaminated data to randomly produce conflicts #21

igrangel opened this issue May 26, 2017 · 7 comments
Assignees

Comments

@igrangel
Copy link
Contributor

Following this idea would be good if we could add a method that introduces some contaminated data by pairs, e.g., two attributes with same refSemantic and different names, etc.

@igrangel igrangel assigned igrangel and omarrana and unassigned igrangel May 26, 2017
@omarrana
Copy link
Contributor

I have added this method for RoleClass attribute. It will change RoleClassAttribute Names in one of the seeds which give us the above scenario.
However, I am not sure about the GoldStandard here.

Please add this in config.ttl if you want to test.
aml:ContaminateRoleClassAttribute "1";

@igrangel
Copy link
Contributor Author

Would be good if we can add the contaminated data to Attributes and Internal Elements since they are the most common AML elements.

@igrangel
Copy link
Contributor Author

Would be possible to have the percents of the injected contaminated data we have?
For example, that we can inject 20% and 40%, etc, with respect to the total number of elements?

@omarrana
Copy link
Contributor

Hi adding to other elements is not problem.
Currently it contaminates only generated data. So for role class I generated 2 attributes . then 2 are contaminated. We know the count of contamination through config

@igrangel
Copy link
Contributor Author

Can we know the total number of elements?

@omarrana
Copy link
Contributor

if we count the elements of seed.aml , then we know out of say 10 elements 2 were contaminated then we can . But i will have to run the results again since its overwritten now.

@omarrana
Copy link
Contributor

close it please

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