Fixed rare bug when -0.0 and 0.0 attribute values appeared in a dataset.

Author: agudys

Diff for: adaa.analytics.rules/build.gradle

@@ -27,7 +27,7 @@ codeQuality {
 }
 
 sourceCompatibility = 1.8
-version = '1.6.1'
+version = '1.6.2'
 
 
 jar {

Diff for: adaa.analytics.rules/src/main/java/adaa/analytics/rules/logic/induction/ClassificationFinder.java

@@ -460,10 +460,6 @@ protected ElementaryCondition induceCondition(
 		Set<Attribute> allowedAttributes,
 		Object... extraParams) {
 
-		if (rule.getPremise().getSubconditions().size() == 3) {
-		//	return null;
-		}
-
 		if (allowedAttributes.size() == 0) {
 			return null;
 		}
@@ -483,10 +479,6 @@ protected ElementaryCondition induceCondition(
 		// iterate over all allowed decision attributes
 		for (Attribute attr : allowedAttributes) {
 
-			if ((rule.getPremise().getSubconditions().size() == 2) && (!attr.getName().equals("input16"))) {
-			//	continue;
-			}
-
 			// consider attributes in parallel
 			Future<ConditionEvaluation> future = (Future<ConditionEvaluation>) pool.submit(() -> {
 
@@ -515,7 +507,7 @@ class TotalPosNeg {
 					// get all distinctive values of attribute
 					for (int id : coveredByRule) {
 						DataRow dr = trainSet.getExample(id).getDataRow();
-						double val = dr.get(attr);
+						double val = dr.get(attr) + 0.0; // to eliminate -0.0
 
 						// exclude missing values from keypoints
 						if (Double.isNaN(val)) {