(Araucaria) Pergunta sobre o ClubLog.

Domingo Dezembro 14 11:14:20 BRST 2014

Olá Vince,

Eu tambem tinha esta duvida, veja os dois textos abaixo, extraidos do help
do clublog.

What does the blue 'V' mean?

Modified on: Thu, 16 Oct, 2014 at 5:50 pm
------------------------------

The blue 'V' means you have a QSO verified after presenting the QSL to ARRL
for an award.

When you upload an ADIF, it will generally include details of any QSLs you
have entered into your logging software. Club Log can use this information
to show you reports that help you focus your QSLing efforts.

There are three possible flags in the ADIF file that Club Log is able to
interpret:

*QSL_RCVD = N*
This means you haven't had a card, so the QSO is unconfirmed. This is
referred to as 'worked' and is signified by a yellow 'W'.

*QSL_RCVD = Y*
This means you have a card, so it's confirmed. This is signified by a green
'C'.

*QSL_RCVD = V*
This means you've presented the card to ARRL and received credit for the
QSO. This is signified by a blue 'V'.

Not all logging software supports this field, and it may also require
additional effort on your part to make sure you enter the verifications in
your log.

LoTW is also considered at the same time, using the LOTW_QSL_RCVD field.

Log matching

Modified on: Sat, 11 Oct, 2014 at 6:50 pm
------------------------------

*This feature is not currently available due to technical problems.*

Club Log pairs-up matching QSO entries in uploaded logs, recording new DXCC
band/mode slots in the order that it finds them in order to generate its *Log
matching* reports.  In order to match a specific QSO in your log:

   - Both you and the person you worked must have logged the QSO and
   uploaded the QSO data to Club Log;
   - Club Log must have had a chance to run the log matching function
   against both logs;
   - The callsign you logged must correspond exactly to the station
   callsign of the other person;
   - The band and mode of the QSO must correspond to those logged by the
   other person;
   - The time of the QSO must be close to that logged by the other person.

*The importance of time-keeping*

Club Log has a tolerance of ±15 minutes when matching QSOs, allowing for
small discrepancies in the times recorded in our logs.  A few of us
diligently log both the start and end times for our QSOs, but most of us
just record one time point - generally the moment we click the "Save this
QSO button" in our logging program (logged as the QSO end time).  Recording
the start time of QSOs is less reliable for those patient DXers who may
start logging a DX station before they finally make it through the pileup
and complete the QSO, although of course you can always edit the time in
your log provided you remember to do it.

*If you are logging the dates and times of your QSOs in local/clock time,
don't expect to get many matches.*  The global standard for almost
everything international in scope is 24-hour Universal Coordinated Time,
often denoted with a lowercase z *e.g.* "10:30z" means half past ten in the
morning, UTC, and "22:30z" means half past ten in the evening, UTC.  Unless
you live near the prime meridian that runs due North/South through the
Royal Observatory at Greenwich in East London, your actual morning and
evening may not coincide with the UTC morning and UTC evening: those of us
living on the Far Side in the Pacific have a topsy-turvy situation where
10:30z is time for bed, while 22:30z on a Monday is when we take our
morning teabreak on the Tuesday!  Provided we all use UTC, we avoid the
confusion caused by living in different time zones, and daylight savings
time.

*Known limitations of Club Log's log matching*

   - Club Log can't give you consolidated reports for all your linked calls
   yet, but it can show you the matches separately against each of your
   callsigns in turn.
   - Club Log can only show you up to 2,000 matches on the report, although
   all matches are dutifully recorded. Try filtering the report by DXCC to get
   around this limitation.
   - The log matching process is quite processor- and disk-intensive so it
   has a low priority and runs only when the system would otherwise be idle.
   Therefore you may have to wait a while after an upload to see the results.
   - Club Log is not accredited for awards programs.  QSOs that match in
   Club Log do not count as "confirmed" or "verified" for awards such as DXCC
   (use LoTW for that!).  As more and more DXers and DXpeditions upload
   their logs to Club Log, so more and more QSOs can be matched. Currently,
   around 10% of our QSOs can be matched in Club Log.  With ARRL's Logbook of
   the World, between 33% and 50% of recent QSOs are matched and confirmed,
   but LoTW doesn't provide such useful analysis as Club Log.

2014-12-11 18:05 GMT-02:00 <dxista em yahoo.ca>:
>
> Alguem poderia me dizer qual e a diference quando o ClubLog na pagina de
> QSls list um contato como Verified, Confirmed ou Matched?
>
> 73 de Vince, VA3VF
>
> _______________________________________________
> Araucaria mailing list
> Araucaria em araucariadx.com
> http://list.araucariadx.com/mailman/listinfo/araucaria
>

-- 
73 de
Roberto - PU4HAS

http://www.qrz.com/db/PU4HAS
-------------- Próxima Parte ----------
Um anexo em HTML foi limpo...
URL: <http://list.araucariadx.com/pipermail/araucaria/attachments/20141214/30d7cbed/attachment.html>