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

Re: WSJT-X v1.0 r3323: Ambiguous entries in ADIF log file when QSO crosses 00:00 UTC

Expand Messages
  • g4wjs
    ... Sorry Joe, I can t agree with you there. Separating date and time into two fields is exactly why were are where we are with this issue. A stand-alone date
    Message 1 of 6 , Jun 5, 2013
    • 0 Attachment
      --- In wsjtgroup@yahoogroups.com, "Joe Subich, W4TV" <lists@...> wrote:
      >
      >
      > > Separating time and date into two fields is not acceptable since it
      > > appears one refers to the start time and the other the end date!
      >
      > It's not a matter of separating time and date into two fields, it is a
      > matter of capturing them at the same time. Currently time is captured
      > when the report is sent (message 2 or message 3 is generated) whilst
      > date is captured when the QSO is completed (the "Log QSO" button is
      > clicked). Since the two events differ by *at least* 2 or 3 minutes,
      > any QSO that crosses "midnight" will record the wrong date in
      > wsjtx_log.adi.

      Sorry Joe, I can't agree with you there. Separating date and time into two fields is exactly why were are where we are with this issue.

      A stand-alone date field belongs in a train or bus timetable, not as an absolute time-stamp in a log record. I don't know if the issue lies with an ambiguous ADIF specification or with a defect in the WSJT-X code, but either way if some way of combining the date and time in a single field had been used we probably wouldn't be having this discussion.

      >
      > 73,
      >
      > ... Joe, W4TV
      >
    • g4wjs
      ... ... I meant to say stand-alone time field there, of course a stand-alone date field is fine if a one day resolution is sufficient. 73 Bill.
      Message 2 of 6 , Jun 5, 2013
      • 0 Attachment
        --- In wsjtgroup@yahoogroups.com, "g4wjs" <bill.8@...> wrote:

        <snip>

        > Sorry Joe, I can't agree with you there. Separating date and time into two fields is exactly why were are where we are with this issue.
        >
        > A stand-alone date field belongs in a train or bus timetable, not as an absolute time-stamp in a log record.

        I meant to say "stand-alone time field" there, of course a stand-alone date field is fine if a one day resolution is sufficient.

        73
        Bill.
      • Carol & Fred Darrah
        When I start a QSO in JT9 mode the date is entered first. The next figure is the time I respond to the call, or give a report. If the date or time is not what
        Message 3 of 6 , Jun 6, 2013
        • 0 Attachment
          When I start a QSO in JT9 mode the date is entered first. The next figure is the time I respond to the call, or give a report. If the date or time is not what you think is right you have the ability to change the items before you log the contact. Where is the the problem for some operators and not others?
          Fred  N9GUE

          --- On Wed, 6/5/13, g4wjs <bill.8@...> wrote:

          From: g4wjs <bill.8@...>
          Subject: [wsjtgroup] Re: WSJT-X v1.0 r3323: Ambiguous entries in ADIF log file when QSO crosses 00:00 UTC
          To: "Joe Subich, W4TV" <lists@...>, wsjtgroup@yahoogroups.com
          Date: Wednesday, June 5, 2013, 8:51 PM

           



          --- In wsjtgroup@yahoogroups.com, "Joe Subich, W4TV" <lists@...> wrote:
          >
          >
          > > Separating time and date into two fields is not acceptable since it
          > > appears one refers to the start time and the other the end date!
          >
          > It's not a matter of separating time and date into two fields, it is a
          > matter of capturing them at the same time. Currently time is captured
          > when the report is sent (message 2 or message 3 is generated) whilst
          > date is captured when the QSO is completed (the "Log QSO" button is
          > clicked). Since the two events differ by *at least* 2 or 3 minutes,
          > any QSO that crosses "midnight" will record the wrong date in
          > wsjtx_log.adi.

          Sorry Joe, I can't agree with you there. Separating date and time into two fields is exactly why were are where we are with this issue.

          A stand-alone date field belongs in a train or bus timetable, not as an absolute time-stamp in a log record. I don't know if the issue lies with an ambiguous ADIF specification or with a defect in the WSJT-X code, but either way if some way of combining the date and time in a single field had been used we probably wouldn't be having this discussion.

          >
          > 73,
          >
          > ... Joe, W4TV
          >

        • g4wjs
          ... Hi Fred, ... Sorry, I probably wasn t too clear in my original post. The date and time fields are the automatically generated ones that get inserted into
          Message 4 of 6 , Jun 6, 2013
          • 0 Attachment
            --- In wsjtgroup@yahoogroups.com, Carol & Fred Darrah <cfdarrah@...> wrote:

            Hi Fred,

            >
            > When I start a QSO in JT9 mode the date is entered first. The next figure is the time I respond to the call, or give a report. If the date or time is not what you think is right you have the ability to change the items before you log the contact. Where is the the problem for some operators and not others?

            Sorry, I probably wasn't too clear in my original post. The date and time fields are the automatically generated ones that get inserted into the log ADIF file. I understand that the values may be changed manually in the log form, but normally they need no adjustment except for this special case when the QSO spans 00:00 UTC. I don't believe this is an operator problem as I expect auto generated values to be correct and unambiguous.

            > Fred  N9GUE

            73
            Bill.
          Your message has been successfully submitted and would be delivered to recipients shortly.