Optimizing 2020 SD-Rule Set - Baseline
I. Get the stats (yes|no) from current year data
shell> cd ${SUFFIXD_DIR}/bin
shell> GetSuffixD ${YEAR}
11
ALL
II. Establish the baseline: remove all Child SD-Rules and use it as the baseline
shell> cd ${SUFFIXD_DIR}/data/${YEAR}/dateR/SdRulesOptimum/00.baseline
shell> cp -p ../../../data/sdRules.stats.rpt.pipe sdRules.stats.in.${YEAR}
shell> cp -p sdRules.stats.in.${YEAR} sdRules.stats.in.${YEAR}.removeChild
shell> fgrep "|CHILD" sdRules.stats.in.${YEAR}.removeChild | wc -l
shell> ln -sf ./sdRules.stats.in.${YEAR}.removeChild sdRules.stats.in
III. Get the Optimal Set
shell> cd ${SUFFIXD_DIR}/bin
shell> GetSdRule ${YEAR}
1
others
00.baseline
0
IV. Results
The result of this baseline set of SD-Rules includes 130 unique parents/self SD-Rules (no child rules). They are sorted by a descending order of precision (= relevant, retrieved No./retrieved No.) and then retrieved No. rate. The top 92 SD-Rules are used as the optimized SD-Rule set to cover 95.05% system (accumulated) precision and 94.26% system (accumulated) recall rate with a system performance (F1) of 1.8931. The total valid instance (relevant, retrieved) number is 53,440 (from the last column in ./sdRules.stats.out).
-- Total line no: 156 -- Total comment no: 26 -- Total Sd-Rule no: 130 --------------------------------------- -- Optimum SD-Rules: 92|63.14%|331|209|122|0|$|noun|ist$|noun|2013|ORG_RULE|SELF|95.05%|94.26%|1.8931|50371|52993