"maybe someone with some N1MM experience can issue some guidelines on how to
correctly set the time macro?"
The setup in N1MM+ is very simple. The user should be using the {TIME2} macro .
When a contest that uses time is loaded the time gets set when the callsign is
filled in and the callsign window loses focus. It can be either a mouse click
or a spacebar press or clicking on an exchange in the RX window but once focus
is lost the time is locked for that contact until either the user wipes the
call from the entry window or the contact is logged. When using the {TIME2}
macro the time is saved in a certain field in the database. Because users were
not using the {TIME2} macro during the contest it was causing error's upon
saving the qso. Because of this the decision was made to log the real time if
that field in the database was empty. The {TIME2} macro is nothing new. The
BARTG contests were one of the first contests that I coded in N1MM classic back
in 2001 or 2002 and that macro and its working have not changed except when the
errors started occurring and the logging of the real time was added in.
73 Rick N2AMG
-----Original Message-----
From: RTTY [mailto:rtty-bounces@contesting.com] On Behalf Of Phil Cooper
Sent: Thursday, April 09, 2015 1:13 PM
To: 'SIMONE WILSON'; 'Michael Therrien'
Cc: rtty@contesting.com
Subject: Re: [RTTY] BARTG HF Contest 2015 Preliminary Results
Hello Simone and the group,
As you said, as contest manager, you have the choice, which is as it should be.
However, there is another point of view….
If you are a contester, casual or serious, and you don’t know how to set up
your logging software correctly, then I believe you should be penalised.
If you think I have copied a time wrongly, then it’s reasonable for me to be
penalised.
However, if I copied it correctly, but the sender logged it incorrectly, I
should not be penalised.
I know Writelog includes the program name in the Cabrillo header, and I assume
that N1MM does the same, but maybe you can clarify this?
I know that if I entered the wrong category, I would be penalised, and I don’t
really see this as different.
Looking at my original RBN, I see that I have a few where the time is off by
one or two minutes, so I assume these will now be corrected.
However, I have a few where the time is so far off as to be questionable.
One is with G3TTJ, where I copied 1242, but the RBN says he sent 1016. I simply
don’t believe that is correct.
Another is with GI4SNA, where I clearly received 14:24 which was sent twice,
but the RBN shows I should have logged 1509.
I also have a couple of NIL’s, including WW4LL, whose exchange was clear to me,
as was my call. Also, there were SQ9DDA and YO7CVL, both of whom called ME, so
I am not sure why the NIL.
This is NOT a complaint, but simply to point out some potential adjudication
issues.
Simone, I have the text dump from MMTTY to back this up, should you wish to see
it.
Obviously, there needs to be a rethink on how the rules are interpreted, and
maybe someone with some N1MM experience can issue some guidelines on how to
correctly set the time macro?
73
Phil GU0SUP
---
This email has been checked for viruses by Avast antivirus software.
http://www.avast.com
_______________________________________________
RTTY mailing list
RTTY@contesting.com
http://lists.contesting.com/mailman/listinfo/rtty
_______________________________________________
RTTY mailing list
RTTY@contesting.com
http://lists.contesting.com/mailman/listinfo/rtty
|