CGI/Perl Guide | Learning Center | Forums | Advertise | Login
Site Search: in

  Main Index MAIN
Search Posts SEARCH
Who's Online WHO'S
Log in LOG

Home: Perl Programming Help: Intermediate: Re: [stuckinarut] HASH-O-RAMA Data Processing Problem: Edit Log


Apr 13, 2015, 8:00 PM

Views: 19158
Re: [stuckinarut] HASH-O-RAMA Data Processing Problem


Thanks for posting the comparison, its looking better than a few comparisons ago.

I couldn't locate the lqpck5 subdirectory, could you post the full link.

In my 2014 RESULTS, I showed N8XX at 13,000 points - his log had 13 QSOs (x 1000 = 13,000) "Claimed", which *should* have been the MAXimum possible score before any Errors in the scores.txt file list. Not sure why only 12,000 shows as the MAX, unless it has to do with him using the name 'IGOR' for the 1st QSO. IMHO, that should not make any difference in determining MAXimum possible.

You should have increased the wtf in the weights log for igor to above the wtf threshold. Ok lets simply this, lets remove one of the more extreme checks (which this issue tripped up on) and assume all the log side of things as oppose to call are somewhat valid and not ignore logs below the wtf threshold. Inevitably you can still control the validity on a per error basis via the adjustmenets log.

Delete or comment out line 522, which should be:

next if $log_wtf < $wtf_threshold;

This may fix numerous issues where previously you hadn't used the weights log to its full potential. Note igor will now appear in the list of names in the unsubmitted and scores logs (this can be changed if need be), but any calls to this name will continue to CNQ error because its < wtf threshold.


(This post was edited by Zhris on Apr 13, 2015, 8:22 PM)

Edit Log:
Post edited by Zhris (Enthusiast) on Apr 13, 2015, 8:21 PM
Post edited by Zhris (Enthusiast) on Apr 13, 2015, 8:22 PM

Search for (options) Powered by Gossamer Forum v.1.2.0

Web Applications & Managed Hosting Powered by Gossamer Threads
Visit our Mailing List Archives