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

20698Re: [ARRL-LOTW] Is this a wise move?

Expand Messages
  • dale cole
    Oct 4, 2013
    • 0 Attachment
      Thanks for the reply Dave.
      That may prove to the prudent thing to do.  Before I did it, I wanted to make sure that if I did, I would not cause my data to become corrupt.  You have now confirmed, that to do, would do more harm than good.  Although +/- 1000 q's would not tax the server, it could bugger up my log program.  Good Saturday afternoon project. (and get uploaded before the weekend contest logs start to pile in on Monday)
      Dale K8TS

      From: Dave AA6YQ <aa6yq@...>
      To: ARRL-LOTW@yahoogroups.com
      Sent: Friday, October 4, 2013 9:47 PM
      Subject: RE: [ARRL-LOTW] Is this a wise move?
      In an ideal world, each logged QSO should be submitted to LoTW exactly once. Anything more than that creates unnecessary load on the LoTW Server.
      Unfortunately, some ops routinely submit their entire log each time they work a few more QSOs, or after every contest. As a result, a large fraction of the load on the LotW Server is the unnecessary processing of what we loosely refer to as “duplicate QSOs” – QSOs whose information is unchanged from when they were previously submitted. Processing a duplicate QSO is not as expensive as processing a new QSO, as the LoTW database is not updated, but the aggregate load from duplicate QSOs is nonetheless significant. That’s why TQSL 1.14 keeps track of already-submitted QSOs and informs you when you attempt to submit a QSO that hasn’t changed since you last submitted it. That’s also why there is sensitivity here to submitting duplicate QSOs.
      There are good reasons to resubmit a previously submitted QSO. For example, you might receive email from a QSO partner asking that you add your grid square to your “Station Location” and re-submit your QSO  so that he or she can get VUCC credit. TQSL 1.14 won’t consider this a duplicate QSO, as some of its information has changed since when it was last submitted. The same thing might happen with your US State, or a QSO’s mode (if you submitted it with DATA rather than a specific mode designator like JT9 or JT65).
      In your situation, Dale, I recommend that you first delete any “made up calls for test purposes” from your log, if you can accurately identify them.  Submitting a few of these to LotW won’t hurt LotW, but may cause confusion for you later.
      Then direct your logging application to submit all QSOs not previously submitted to LotW; your QSO partners will appreciate it, but you won’t impose any unnecessary load on LotW.
                   Dave, AA6YQ
      From: ARRL-LOTW@yahoogroups.com [mailto:ARRL-LOTW@yahoogroups.com] On Behalf Of dale cole
      Sent: Friday, October 04, 2013 9:28 PM
      To: arrl-lotw@yahoogroups.com
      Subject: [ARRL-LOTW] Is this a wise move?
      Usually, after each contest, or snag of a new DX, I make sure that they are uploaded to LOTW.  I have never uploaded my entire log.  My log data goes only as far back as to when I changed calls, and includes a little over 1000 q's.  Is it a wise move to upload everything once now, knowing there are busted calls and a few made up calls for test purposes in different logger programs?  Will this screw up my WPX counts?  I would be loading from N3FJPs' ACLog.
      I don't know why, but each time I write to the group, it defaults to Dave but maybe some things are best left alone
      Dale K8TS
      No virus found in this message.
      Checked by AVG - http://www.avg.com/
      Version: 10.0.1432 / Virus Database: 3222/6224 - Release Date: 10/04/13
    • Show all 3 messages in this topic