On 9/1/2012 11:44 AM, [email protected] wrote:
This was when an update got generated when the last weekly set appeared to
below the ham threshold. So I removed the check on the weekly set.
That weekly set (20120623) still says 119126 hams (below threshold of
150000), if you click "source details" (you'll need to ctrl-f search
the page for that).
...
Requiring both the current daily and latest weekly to be above the
threshold makes sense to me, and as I said, it's what I previously believed
was required. I just can't explain why it worked in this case, if that's
required.
Digging into why it worked over a month ago with the number of changes
that have been made in the meantime is just too hard. These scripts are
complex and intertwined plus require distributed submissions so I'm
doing my best to keep a slow and steady progress forward
Any ideas? Should I re-enable the latest weekly check in my script?
Personally, I'm a fan of your scripts and I think that more transparency
on these processes is good. Send them to ruleqa perhaps?
I thin kwe had two issues though. One a lack of corpora for the weekend
set that bombed things for a week and then the eval code the blew up
things since.
Regards,
KAM
