Club Log · 7 April 2008 by Michael Wells
An brief introduction to Club Log
Club Log – ‘The ADIF Acrobat’
Club Log is a web site designed to produce reports and competitive league tables from participating members’ logs, which they can upload, much like Logbook of the World or eQSL. It’s being actively used by CDXC members, and you are invited to join in.
How did it start, and how does it work?
In 2007, I started designing a tool to provide a chart of DXCCs I’d worked, with a log search function for people who wanted to QSL or were curious if they had worked G7VJR.
I wanted this tool to be completely automated. The idea was to process my ADIF logs (exported from my logging software) and create the reports and search features, just by analysing the QSOs.
I hope you are not lost at this point – have a look in your logging software and see if you can find a menu that lets you “export to ADIF” – as you will find most do. It’s a common way of storing radio logs in computer format.
While I was doing some planning, I decided that it would be quite interesting to extend the idea, and create a service anyone could sign up and use, not just me. As well as being useful to other radio friends, I reasoned that if the database grew to have more participants, then it could mined to make league tables of DXCCs worked, including making league tables for specific modes or clubs (both rather intensive to do by hand).
The other thing I decided to do was take the manual labour out of creating most-wanted lists. It is quite a simple task for a computer to work out which DXCC entities are logged least often, and even to break this down by mode or by time periods. It just needs to be fed a lot of QSOs and the information can be readily processed. Ideally, millions of QSOs…
So, Club Log was born. It is a web-based application which uses a database to analyse amateur radio log files, which are uploaded in the common ADIF format. Using the logs, it builds band-mode league tables of amateurs’ QSOs, provides efficient log search tools and creates most wanted lists for DXCC entities (both over all time and in recent history, or by mode for example). Also, Club Log can give back to its users the ability to find “wanted” DX spots, and other analysis of their logs which might be hard to do with normal logging software.
How to sign up
I realise that using new web sites can be a little daunting. Please don’t be put off by all the jargon. Remember, to take part in Club Log you just need to sign in and upload your ADIF file from your logging software. If you do this, you will enrich the database and improve the quality of the most-wanted lists, so please be encouraged to join in. Obviously, it’s free.
To join Club Log, simply go to http://clublog.g7vjr.org (no ‘www’) and then click the button labelled “sign up” in the top menus. Signing up involves filling in your name and e-mail address, and typing in a single number from a sequence of about eight digits. You will be emailed a code to confirm your email address is valid. Unfortunately, I have to do these things, to stop the system being abused. Thanks for your understanding – just follow the instructions and you’ll be registered in a minute or two.
After you have signed in, you will find you can set up one or more callsigns. For example, you might have a ‘G’ and a ‘GM’ logbook, so they are both separate callsigns.
After you have added your callsigns, you can go onto upload your ADIF files. Simply export your entire log (yes, even if it’s really big!) and save it somewhere on your computer. Then, click on the button that says ‘Upload’ in the menu of the Club Log site, and follow the instructions to upload the file.
It takes a while for Club Log to process new logs, because it does an exhaustive analysis of each DX call you work to try and determine where the callsign is (for DXCC purposes).
While your log is being processed, you can access the following features:
•About
This is a page of information about Club Log, including a graph of how many people and callsigns are active, and analysis of the SSB/CW/data modes splits for the complete set of logs in the system.
•Upload
This is where you can upload new logs. You’ll find it is in several steps. Please follow the instructions carefully and you will have no problems.
•League
From here, you can access DXCC band-mode league tables. There are options to break the charts down by club (you can choose the clubs to which you belong on the ‘Settings’ page – see below). You can also access the ‘5 year league’, which is specifically aimed at newer ham radio operators who can’t hope to compete with the old timers!
•Search
This is a log search function, designed for Dxpedition users who want to offer a log search on their own homepage. If you perform a search, the results will show a breakdown of bands and modes, but of course the exact times will not be disclosed, to protect the integrity of QSLing.
•Most-Wanted
This tool builds a ranked list of DXCC entities which are ‘wanted’. It is based on the percentage of users who haven’t worked the entity, and can be filtered by mode or time.
•Charts
Club Log will generate a chart for any of your callsigns, which will show each entity against bands. At the top of the page, you can change the way the chart works to filter by mode and date. At the bottom of the chart, a graph of your QSOs per year, and your CW/SSB/Data split as a percentage are displayed.
•LF Challenge
This is a special report which shows 160/80/40 QSOs worked during the month of March. This in turn can be used to enter the LF Challenge, and perhaps win the CDXC Penallt Trophy. Competition is fierce – for further details see http://www.cdxc.org.uk/awards/lf-challenge.
•Spots
Using the information contained in your log, Club Log is able to easily work out which DXCC entities you haven’t worked. Using this list, it can filter the DX Cluster and give you a personalised cluster that only lists spots that are about the DXCCs you need. The list updates about once a minute. Of course, if you’ve worked them all then you will have to wait for a new entity like Kosova to be approved…!
•Settings
Use this page to manage your password, add callsigns, change the clubs of which you are a member, or (if you really need to) delete logs from Club Log. You might need to do that if you have made a mistake, like uploading a duff log or sending a log to the wrong callsign.
•Log Out
If you’re on a shared PC, don’t forget to log out to protect your account.
About ADIF and special callsigns
Skip this bit if you’re not interested in an autopsy of how ADIF works.
In an ideal world, all callsigns would resolve to one and only one DXCC entity. In practice, though, there are lots that don’t, like VP8, ZK and (increasingly) USA callsigns used on expeditions in the Pacific. In fact, there are lots of annoying exceptions and more appear every year.
Some logging tools are very advanced. When you enter your QSO, these tools generally have a specific DXCC entity number encoded against each callsign you work, and they include this in ADIF files they generate. If so, then Club Log will use this – by far the best solution provided you haven’t made any mistakes.
However, some logging software doesn’t encode a DXCC number (I can appreciate why – it’s not easy to get it right). In these cases, Club Log will try and work out the DXCC number for you. This is fairly accurate. It uses a combination of lists, Dxpedition records from the past, manual rules added by me and other Club Log users, and it also mines existing logs to see if other users have been consistently recording the callsign against a particular location. Between these sources, it can usually be sorted out. It just takes a lot longer.
If your log is being analysed by Club Log (ie. you don’t export DXCC entity numbers in your ADIF file), then, when you upload your log, especially if you’ve been active for a long time, you can help me and other Club Log users by identifying any mistakes Club Log has made, and emailing them to michael@g7vjr.org.
Acknowledgements
Club Log was inspired by a clever idea from Dominic M0BLF (called HamELog) which provided DXCC charts and log search for a single callsign. Dominic has a knack of inventing and implementing ideas like this. Thanks, Dom.
I would also like to acknowledge Marios 5B4WN, who was able to give me some good code and ideas on how to turn callsigns into DXCC entities reliably. Derivatives of this code are in use on the RSGB IOTA site, and also on DX Lite. It’s funny how acorns grow. Cheers Marios.
