On 8/7/2012 11:58 AM, Axb wrote:
-1 but - it spit out even more high scores.
> Or I tweak the days Ham is good for to include more ham?
+1 This would probably cause less havoc.
Upped from 72 to 84 with very little change
> Jari, are you seeing your corpus?
>
> Anyone else seeing missing corpora?
> Is this possibly a problem where corpora are not being included?
OK, so here's the issue:
The script running RIGHT now is checking to see if the uploaded mass
check log contains:
# SVN revision: 1369288
It uses this command:
REVISION=`head corpus/usable-corpus-set${SCORESET}/* | grep "SVN
revision" | cut -d" " -f4 | sort -rn | head -1`
Short circuiting the script and looking at the corpus set manually, we have:
head corpus/usable-corpus-set1/* | grep "SVN revision" | cut -d" " -f4
| sort -nr | uniq
1369288
1366614
1364050
1348336
1342864
1307740
1301890
1296586
1243018
1240465
1197902
1183598
1128571
1098073
1064983
1059274
1042117
831520
814117
unknown
Jari, checking your logs, we have:
ham-net-jarif.log:# SVN revision: 1364050
spam-net-jarif.log:# SVN revision: 1364050
So your logs are being ignored because they are not being run with the
"right" version of code.
I'm working to find out why you have the wrong version of the code...
Regards,
KAM
