You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm seeing very different explanations from bin/streaming.sh compared to bin/batch.sh and bin/frontent.sh. In addition to this, the values of ratio, records, and support are incorrect for streaming mode explanations.
For any explanation in the report, the following relationship should hold true:
ratio = (outliers_with_attr / outliers) / (inliers_with_attr / inliers)
Support is the proportion of records marked as outliers that contained this attribute combination. Theoretical minimum is 0 (no outliers had this pattern), maximum is 1 (all outlier records matched).
Ratio Out/In is the proportion of outlier records containing this attribute combination compared to the proportion of inlier records containing this attribute combination (i.e., support in outliers divided by support in inliers). A ratio of 1 means that this pattern appeared equally frequently in inlier and outliers. A ratio of infinity means this pattern was not present in the inliers.
Records is the actual number of outlier records matching this pattern (i.e., support * number of outliers).
The values of support, ratio and records make sense (UPDATE: risk ratio shouldn't be INFINITY. There exist inlier records with this attribute value combination! I'm going through the source code and learning about the FPGrowth algorithm to figure out the mistake).
I'm seeing very different explanations from
bin/streaming.sh
compared tobin/batch.sh
andbin/frontent.sh
. In addition to this, the values ofratio
,records
, andsupport
are incorrect for streaming mode explanations.For any explanation in the report, the following relationship should hold true:
ratio = (outliers_with_attr / outliers) / (inliers_with_attr / inliers)
Data
sensor_data_demo_db_version.txt
Here is a result from bin/batch.sh:
The values of support, ratio and
recordsmake sense (UPDATE: risk ratio shouldn't be INFINITY. There exist inlier records with this attribute value combination! I'm going through the source code and learning about the FPGrowth algorithm to figure out the mistake).Here is the result from bin/streaming:
The values of support, records and ratio are in disagreement with each other.
support = records / outliers
does not hold true.ratio
andrecords
does not make sense.Cause of issue
I believe that this issue is due to a bug in the code for streaming explanations.
The text was updated successfully, but these errors were encountered: