Skip to content

Changes

Page history
revert back authored by Matthew Chambers's avatar Matthew Chambers
Show whitespace changes
Inline Side-by-side
Making-GridTracker-Work-For-You/GridTracker-Statistics.md
View page @ 704c14c9
!["Statistics Button"](../img/GT_Stats.png) !["Statistics Button"](/img/GT_Stats.png)
Clicking on the "Statistics" button in the control panel will open a new window - the **Statistics** window - with every metric the developers could think of that's related to your QSO data. Clicking on the "Statistics" button in the control panel will open a new window - the **Statistics** window - with every metric the developers could think of that's related to your QSO data.
...@@ -10,7 +10,7 @@ Clicking on the "Statistics" button in the control panel will open a new window ...@@ -10,7 +10,7 @@ Clicking on the "Statistics" button in the control panel will open a new window
### **Logbook Data** ### **Logbook Data**
!["Logbook tab of the Stats window](../img/GT_Stats_Logbook.png) !["Logbook tab of the Stats window](/img/GT_Stats_Logbook.png)
The first tab in the **Statistics** window is Logbook data. It's self explanatory: the columns reflect the data collected by WSJT-X plus any other external logs you've chosen to import into your current working session. The first tab in the **Statistics** window is Logbook data. It's self explanatory: the columns reflect the data collected by WSJT-X plus any other external logs you've chosen to import into your current working session.
...@@ -20,7 +20,7 @@ Again, GridTracker always retrieves your current wsjtx_log.adi file when GridTra ...@@ -20,7 +20,7 @@ Again, GridTracker always retrieves your current wsjtx_log.adi file when GridTra
##### **_Sorting_** ##### **_Sorting_**
!["Logbook with several column headers identified"](../img/GT_Stats_LogbookSort.png) !["Logbook with several column headers identified"](/img/GT_Stats_LogbookSort.png)
Click on a column header (i.e., Station, Mode, DXCC) to sort the table by that column. The initial sort will be alphabetically from A to A. Click on the column header again and the table will reverse sort from Z to A. Click on a column header (i.e., Station, Mode, DXCC) to sort the table by that column. The initial sort will be alphabetically from A to A. Click on the column header again and the table will reverse sort from Z to A.
...@@ -36,32 +36,32 @@ Type at least one character into the yellow oval above **Station** to get all en ...@@ -36,32 +36,32 @@ Type at least one character into the yellow oval above **Station** to get all en
* The number of QSOs that meet your criteria appears at the top of the page. * The number of QSOs that meet your criteria appears at the top of the page.
!["Logbook with callsign filter containing A and 272 log entires matching"](../img/GT_Stats_LogbookFilter1.png) !["Logbook with callsign filter containing A and 272 log entires matching"](/img/GT_Stats_LogbookFilter1.png)
!["Logbook with callsign filter containing AA and 27 log entries matching"](../img/GT_Stats_LogbookFilter2.png) !["Logbook with callsign filter containing AA and 27 log entries matching"](/img/GT_Stats_LogbookFilter2.png)
* The initial search results return sorted in reverse chron order: newest date to earliest. You can then click on the column headings to do any further sorts you wish. * The initial search results return sorted in reverse chron order: newest date to earliest. You can then click on the column headings to do any further sorts you wish.
* The filter is not case sensitive. If you input an "a" it will automatically be converted to an "A". * The filter is not case sensitive. If you input an "a" it will automatically be converted to an "A".
* The order you type characters into the search box matters. The search function does a character string search so will get a different set of results doing a filter search for "JY" than one done for "YJ" * The order you type characters into the search box matters. The search function does a character string search so will get a different set of results doing a filter search for "JY" than one done for "YJ"
!["Logbook with callsign filter containing YJ"](../img/GT_Stats_LogbookFilter_YJ.png)!["Logbook with callsign filter containing JY"](../img/GT_Stats_LogbookFilter_JY.png) !["Logbook with callsign filter containing YJ"](/img/GT_Stats_LogbookFilter_YJ.png)!["Logbook with callsign filter containing JY"](/img/GT_Stats_LogbookFilter_JY.png)
###### **_Grid Filtering_** ###### **_Grid Filtering_**
You can filter grid data the same way you filter callsigns: by typing one or more characters into the yellow box above the **Grid** column label. However the filter results are entirely dependent on the _order of the search string characters._ Some examples from an actual data set will make this clearer. You can filter grid data the same way you filter callsigns: by typing one or more characters into the yellow box above the **Grid** column label. However the filter results are entirely dependent on the _order of the search string characters._ Some examples from an actual data set will make this clearer.
!["Logbook with grid filter containing L"](../img/GT_Stats_LogbookGrids_L.png) !["Logbook with grid filter containing L"](/img/GT_Stats_LogbookGrids_L.png)
* Filtering the data for Grids with **"L"** returns the following: four QSOs where **"L"** is the _first letter_ of the two letter grid identification. * Filtering the data for Grids with **"L"** returns the following: four QSOs where **"L"** is the _first letter_ of the two letter grid identification.
* But it omits data where **"L"** is _the second letter_ in the initial two letter grid I.D. such as grids beginning DL, EL, FL, etc. * But it omits data where **"L"** is _the second letter_ in the initial two letter grid I.D. such as grids beginning DL, EL, FL, etc.
!["Logbook with grid filter containing DL"](../img/GT_Stats_LogbookGrids_DL.png)!["Logbook with grid filter containing EL"](../img/GT_Stats_LogbookGrids_EL.png)!["Logbook with grid filter containing FL"](../img/GT_Stats_LogbookGrids_FL.png) !["Logbook with grid filter containing DL"](/img/GT_Stats_LogbookGrids_DL.png)!["Logbook with grid filter containing EL"](/img/GT_Stats_LogbookGrids_EL.png)!["Logbook with grid filter containing FL"](/img/GT_Stats_LogbookGrids_FL.png)
!["Logbook with grid fitler containing 9"](../img/GT_Stats_LogbookGrids_9.png) !["Logbook with grid fitler containing 9"](/img/GT_Stats_LogbookGrids_9.png)
You cannot filter for a number character alone in a grid I.D. alone: You cannot filter for a number character alone in a grid I.D. alone:
!["Logbook with grid filter contianing DM9"](../img/GT_Stats_LogbookGrids_DM9.png) !["Logbook with grid filter contianing DM9"](/img/GT_Stats_LogbookGrids_DM9.png)
But you can filter for grids that contain a number that follows two alphabetic characters like, "\✱\✱#" (where ✱ is a letter and # is a number). Filtering for **DM9** returns these results: But you can filter for grids that contain a number that follows two alphabetic characters like, "\✱\✱#" (where ✱ is a letter and # is a number). Filtering for **DM9** returns these results:
...@@ -75,11 +75,11 @@ But it won't return QSOs with grid IDs like: ...@@ -75,11 +75,11 @@ But it won't return QSOs with grid IDs like:
You can filter for an exact string of four characters such the the following example which filtered data for grids **"EL96"**: You can filter for an exact string of four characters such the the following example which filtered data for grids **"EL96"**:
!["Logbook with grid filter containing EL96"](../img/GT_Stats_LogbookGrids_EL96.png) !["Logbook with grid filter containing EL96"](/img/GT_Stats_LogbookGrids_EL96.png)
###### **_Filtering for Band, Mode, QSL, and DXCC_** ###### **_Filtering for Band, Mode, QSL, and DXCC_**
!["Logbook header row with drop down options identified"](../img/GT_Stats_LogbookFilterDropDowns.png) !["Logbook header row with drop down options identified"](/img/GT_Stats_LogbookFilterDropDowns.png)
Clicking on any of these green boxes gives you a drop-down menu from which you can make your section. Clicking on any of these green boxes gives you a drop-down menu from which you can make your section.
...@@ -87,10 +87,10 @@ The options in the dropdown menus will reflect the data you currently have impor ...@@ -87,10 +87,10 @@ The options in the dropdown menus will reflect the data you currently have impor
| **Band** | **Mode** | **QSL** | **DXCC** | | **Band** | **Mode** | **QSL** | **DXCC** |
| --- | --- | --- | --- | | --- | --- | --- | --- |
| !["Band dropdown from logbook header"](../img/GT_Stats_Logbook_Band.png) | !["Mode dropdown from logbook header"](../img/GT_Stats_Logbook_Mode.png) | !["QSL dropdown from logbook header"](../img/GT_Stats_Logbook_QSL.png) | !["DXCC dropdown from logbook header"](../img/GT_Stats_Logbook_DXCC.png) | | !["Band dropdown from logbook header"](/img/GT_Stats_Logbook_Band.png) | !["Mode dropdown from logbook header"](/img/GT_Stats_Logbook_Mode.png) | !["QSL dropdown from logbook header"](/img/GT_Stats_Logbook_QSL.png) | !["DXCC dropdown from logbook header"](/img/GT_Stats_Logbook_DXCC.png) |
### **Scores and Awards** ### **Scores and Awards**
!["Example of shading styles in GridTracker"](../img/GT_Shading.png) !["Example of shading styles in GridTracker"](/img/GT_Shading.png)
Before discussing the Scores and Awards tabs on the **Statistics** page an explanation of "shading" versus "highlighting" is in order because shading and highlighting are used on most of the awards pages. Before discussing the Scores and Awards tabs on the **Statistics** page an explanation of "shading" versus "highlighting" is in order because shading and highlighting are used on most of the awards pages.
...@@ -117,16 +117,16 @@ The following screenshots illustrate how your award statistics will vary dependi ...@@ -117,16 +117,16 @@ The following screenshots illustrate how your award statistics will vary dependi
This user has worked four continents and 27 U.S. states via the specific mode of FT-4 on the 20 meter band. This user has worked four continents and 27 U.S. states via the specific mode of FT-4 on the 20 meter band.
!["Example of WAC/WAS award tab viewing 20m/FT4"](../img/GT_Stats_WACWAS_20mFT4.png) !["Example of WAC/WAS award tab viewing 20m/FT4"](/img/GT_Stats_WACWAS_20mFT4.png)
The user has worked 5 continents and 46 states in _some_ digital band on 40 meters. The user has worked 5 continents and 46 states in _some_ digital band on 40 meters.
!["Example of WAC/WAS award tab viewing 40m/Digital"](../img/GT_Stats_WACWAS_40mDigital.png) !["Example of WAC/WAS award tab viewing 40m/Digital"](/img/GT_Stats_WACWAS_40mDigital.png)
No contacts in any digital mode on the 160 meter band. No contacts in any digital mode on the 160 meter band.
!["Example of WAC/WAS award tab viewing 160m/Digital"](../img/GT_Stats_WACWAS_160mDigital.png) !["Example of WAC/WAS award tab viewing 160m/Digital"](/img/GT_Stats_WACWAS_160mDigital.png)
No contacts using CW on the 20 meter band. No contacts using CW on the 20 meter band.
!["Example of WAC/WAS award tab viewing 20m/CW"](../img/GT_Stats_WACWAS_20mCW.png) !["Example of WAC/WAS award tab viewing 20m/CW"](/img/GT_Stats_WACWAS_20mCW.png)
\ No newline at end of file \ No newline at end of file