Optimizing 2016 SD-Rule Set - Optimum Log

I. Criteria:

• Total valid SD-Pairs from baseline (parent only rules) is 50,814
• Candidate child rules are:
  • Decompose occurrence rate >= 40% (default)
  • Candidate child rules: occurrence rate >= 25% (default)
  • Candidate child rules: precision is decided by the methodology of optimization
  • Find the one with max. precision and recallIf the child rule has lower precision and recall than parents, it is not a good candidate even its recall is over 25%!

    Such as in Cases 15 and 16, the system performance is worse because both precision and recall are lower than parents. No need to run the program for these two cases.

    If the performance of a child rule is worse, then the next generation child rules will be worse. No need to run through the following generations (even we still run through them to keep the log completed)!

• Find the best set by comparing parent vs. child rules:
  • Only apply when child rules precision is better than parent rule
  • Higher system performance
  • If System Performance is the same,
    • Use Precision
    • Use Recall
    • Use Linguistic knowledge

    • Use parent rule to replace child rules.
    • If no parent-child rules involved, use more rules

II. Iterative Optimization Log:

Source:

• Dir: ${SUFFIX_DIR}/data/${YEAR}/dataR/SdRulesOptimum/*/
• File: sdRules.stats.out.html