Loading ...
Sorry, an error occurred while loading the content.

Re: [N1MM] Contest Robot Application

Expand Messages
  • Gunarso
    Thank you to all who have responded to my email, I can understand the differences in the application, but what I mean here is. robot applications just taken
    Message 1 of 5 , Jul 19, 2013
      Thank you to all who have responded to my email, I can understand the differences in the application, but what I mean here is.
      robot applications just taken delivery of logs and check sumary data categories.
      application cross check, to check the results of the log, how do I check the log sheet sent by the participants, to examine fraud and errors. If done manually, this is very difficult and takes a long time, certainly there apalikasi or software to examine or cross check log sheet contestant.
      thank you all for enlightenment

      73 de Gun

      Send from My MacBook

      From: radio_ng2d <bills_eyepiece@...>
      To: N1MMLogger@yahoogroups.com
      Sent: Friday, July 19, 2013 7:01 PM
      Subject: Re: [N1MM] Contest Robot Application

      The contest robot can do little more than check the vlidity of the incoming log as previously described.

      The contest can not be scored until all the logs are in, so two different programs are by far the best solution.

      --- In N1MMLogger@yahoogroups.com, Anthony Willard <awillard69@...> wrote:
      > Contest robots and log checking are two different animals.  Since every contest is different, every robot and scoring application is different.
      > Normally, the contest robot receives the submitted log and checks that it contains all the information for a submission, like format, type of contest, category of submission, and QSO's, etc.  A simple one would stop there and notify the sender of acceptance.  A more thorough version would check QSO's are valid, such as mode, time of contact, band, etc.  The more extensive the robot is, the higher the log quality used in QSO checking and scoring.
      > Log checking for points scoring against other logs is another application, and is usually very contest specific.  There are rules for the contest, such as who can contact whom, available bands, band change limits, operating times, modes, multipliers, etc.  All of these are then cross checked against all other logs to verify the contacts that it can and handle ones that are not in any other log.  Are there busted calls, unique calls, incorrect bands, etc?  The more complicated the rules and scoring, the more extensive this application must be.  And that's just checking the basic QSO.  If you go further and process the exchange and ensure it was recorded properly, you have yet another layer of complexity to the scoring.  What about penalties?  Are the points deductions for unmatched or incorrect QSO data?
      > Many contest sponsors have extensive applications and check every item in the robot.  They want the log to be the absolute best before scoring and notify the sender accordingly.  Scoring a contest takes a lot of time and usually these applications were developed over many iterations (think years) and contests.  The more you think about it, the easier it is to understand why it takes so long to see any results from the contest - this is not a trivial task.
      > Good luck.
      > Anthony
      > AB9YC

      [Non-text portions of this message have been removed]
    Your message has been successfully submitted and would be delivered to recipients shortly.