Changed outlier severity metric to exclusive runtime as using inclusive runtime will, for example, give a large severity to an anomaly in a small wrapper function around a long running child function

Disabled recoverable errors being logged when HBOS/COPOD come across a function with no unlabeled events in the data set; this can happen for legitimate reasons

Author: giltirn

include/chimbuko/ad/ExecData.hpp

@@ -489,7 +489,7 @@ class ExecData_t {
     /**
      * @brief Return the outlier severity, representing how important the outlier is
      */  
-    double get_outlier_severity() const{ return (double)get_runtime(); }   
+    double get_outlier_severity() const{ return (double)get_exclusive(); }
 
     /**
      * @brief Set the label

src/ad/ADOutlier.cpp

@@ -283,7 +283,7 @@ Anomalies ADOutlierHBOS::run(int step) {
       }
     }
     else { 
-	    recoverable_error(std::string("AD: Zero function runtimes "));
+      //recoverable_error(std::string("AD: Zero function runtimes "));
 	    continue;
     }
   }
@@ -568,7 +568,7 @@ Anomalies ADOutlierCOPOD::run(int step) {
       }
     }
     else { 
-	    recoverable_error(std::string("AD: Zero function runtimes "));
+      ///recoverable_error(std::string("AD: Zero function runtimes "));
 	    continue;
     }
     verboseStream << "Size of runtimes: " << runtimes.size() << ", func_id: " << func_id << std::endl;