-
Notifications
You must be signed in to change notification settings - Fork 1
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
Comments
I have added this method for RoleClass attribute. It will change RoleClassAttribute Names in one of the seeds which give us the above scenario. Please add this in config.ttl if you want to test. |
Would be good if we can add the contaminated data to Attributes and Internal Elements since they are the most common AML elements. |
Would be possible to have the percents of the injected contaminated data we have? |
Hi adding to other elements is not problem. |
Can we know the total number of elements? |
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. |
close it please |
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.
The text was updated successfully, but these errors were encountered: