|
Re: WD config errors
Rob Robinett
I am away from home. I’ll check it later today when I get home
On Thu, Jan 7, 2021 at 12:20 PM Glenn Elmore <n6gn@...> wrote:
--
|
|
|
|
Re: WD config errors
Glenn Elmore
On 1/7/21 12:40 PM, John via groups.io wrote:
Here is with a comma added. I get the same errors..The comma was no doubt a problem but there's another thing, perhaps formatting was changed in posting. I don't know about the line wrap, but your entry for schedule 00:00 looks suspect declare WSPR_SCHEDULE_simple=(I see it as two lines and I can't tell if that's what you actually have. I think it needs to be a single line. WD is a bit fussy about white space and delimiters. Check your .conf very carefully. Glenn
|
|
|
|
Re: WD config errors
John
And also the same errors when KIWI_0,KIWI_1 is coded.
J
|
|
|
|
Re: WD config errors
John
Here is with a comma added. I get the same errors..
# To enable these options, remove the leading '#' and modify SIGNAL_LEVEL_UPLOAD_ID from "AI6VN" to your call sign:
#SIGNAL_LEVEL_UPLOAD="noise" ### If this variable is defined and not "no", AND SIGNAL_LEVEL_UPLOAD_ID is defined, then upload signal levels to the wsprdaemon cloud database
### SIGNAL_LEVEL_UPLOAD_MODE="no" => (Default) Upload spots directly to wsprnet.org
### SIGNAL_LEVEL_UPLOAD_MODE="noise" => Upload extended spots and noise data. Upload spots directly to wsprnet.org
### SIGNAL_LEVEL_UPLOAD_MODE="proxy" => In addition to "noise", don't upload to wsprnet.org from this server. Regenerate and upload spots to wsprnet.org on the wsprdaemon.org server
SIGNAL_LEVEL_UPLOAD="yes" ### If this variable is defined as "yes" AND SIGNAL_LEVEL_UPLOAD_ID is defined, then upload extended spots and noise levels to the logs.wsprdaemon.org database and graphics file server.
SIGNAL_LEVEL_UPLOAD_ID="TI4JWC" ### The name put in upload log records, the the title bar of the graph, and the name used to view spots and noise at that server.
SIGNAL_LEVEL_UPLOAD_GRAPHS="yes" ### If this variable is defined as "yes" AND SIGNAL_LEVEL_UPLOAD_ID is defined, then FTP graphs of the last 24 hours to http://wsprdaemon.org/graphs/SIGNAL_LEVEL_UPLOAD_ID
#SIGNAL_LEVEL_LOCAL_GRAPHS="no" ### If this variable is defined as "yes" AND SIGNAL_LEVEL_UPLOAD_ID is defined, then make graphs visible at http://localhost/
##############################################################
### The RECEIVER_LIST() array defines the physical (KIWI_xxx,AUDIO_xxx,SDR_xxx) and logical (MERG...) receive devices available on this server
### Each element of RECEIVER_LIST is a string with 5 space-seperated fields:
### " ID(no spaces) IP:PORT or RTL:n MyCall MyGrid KiwPassword Optional SIGNAL_LEVEL_ADJUSTMENTS
### [[DEFAULT:ADJUST,]BAND_0:ADJUST[,BAND_N:ADJUST_N]...]
### A comma-separated list of BAND:ADJUST pairs
### BAND is one of 2200..10, while ADJUST is in dBs TO BE ADDED to the raw data
### So If you have a +10 dB LNA, ADJUST '-10' will LOWER the reported level so that your reports reflect the level at the input of the LNA
### DEFAULT defaults to zero and is applied to all bands not specified with a BAND:ADJUST
declare RECEIVER_LIST=(
"KIWI_0 192.168.2.160:8073 TI4JWC EK70wb 6105
KIWI_1 192.168.2.161:8073 TI4JWC EK70wb 6105
MERGED_0_1 KIWI_0, KIWI_1 TI4JWC EK70wb " )
### This table defines a schedule of configurations which will be applied by '-j a,all' and thus by the watchdog daemon when it runs '-j a,all' ev ery odd two minutes
### The first field of each entry in the start time for the configuration defined in the following fields
### Start time is in the format HH:MM (e.g 13:15) and by default is in the time zone of the host server unless ',UDT' is appended, e.g '01:30,UDT'
### Following the time are one or more fields of the format 'RECEIVER,BAND'
### If the time of the first entry is not 00:00, then the latest (not necessarily the last) entry will be applied at time 00:00
### So the form of each line is "START_HH:MM[,UDT] RECEIVER,BAND... ". Here are some examples:
declare WSPR_SCHEDULE_simple=(
"00:00 KIWI_0,80 KIWI_0,40 KIWI_0,30
MERGED_0_1,20 MERGED_0_1,17 MERGED_0_1,15 MERGED_0_1,12 MERGED_0_1,10 " )
###declare WSPR_SCHEDULE_complex=(
### "06:00 KIWI_0,80 KIWI_0,40 KIWI_0,30 MERGED_0_1,20 MERGED_0_1,17 MERGED_0_1,15 MERGED_0_1,12 MERGED_0_1,10" ### KIWI_0 => 7 rx channels (80/40/30/20/17/15/../10), KIWI_1 => 7 rx channels (../40/30/20/17/15/12/10)
### "18:00 MERGED_0_1,80 MERGED_0_1,40 MERGED_0_1,30 MERGED_0_1,20 MERGED_0_1,17 MERGED_0_1,15 KIWI_0,12 KIWI_1,10" ### KIWI_0 => 7 rx channels (80/40/30/20/17/15/12/..), KIWI_1 => 7 rx channels (80/40/30/20/17/15/../10)
###)
### This array WSPR_SCHEDULE defines the running configuration. Here we make the simple configuration defined above the active one:
declare WSPR_SCHEDULE=( "${WSPR_SCHEDULE_simple[@]}" )
|
|
|
|
Re: WD config errors
Gwyn Griffiths
John
toggle quoted messageShow quoted text
I think you need a comma in the line below between KIWI_0 and KIWI_1 regards Gwyn G3ZIL
On Thu, Jan 7, 2021 at 06:02 PM, John wrote: MERGED_0_1 KIWI_0 KIWI_1 TI4JWC EK70wb " )
|
|
|
|
WD config errors
John
I am still seeing ERRORS when I start WD. What is my config error?
John TI4JWC ===================== pi@raspberrypi:~/wsprdaemon $ wd -a -V
wsprdaemon.sh Copyright (C) 2020 Robert S. Robinett
This program comes with ABSOLUTELY NO WARRANTY; for details type './wsprdaemon.sh -h'
This is free software, and you are welcome to redistribute it under certain conditions. execute'./wsprdaemon.sh -h' for details.
wsprdaemon depends heavily upon the 'wsprd' program and other technologies developed by Joe Taylor K1JT and others, to whom we are grateful.
Goto https://physics.princeton.edu/pulsar/K1JT/wsjtx.html to learn more about WSJT-x
ERROR: in WSPR_SCHEDULE line '00:00 KIWI_0,80 KIWI_0,40 KIWI_0,30 MERGED_0_1,20 MERGED_0_1,17 MERGED_0_1,15 MERGED_0_1,12 MERGED_0_1,10', job 'MERGED_0_1,20' specifies receiver 'MERGED_0_1' not found in RECEIVER_LIST
ERROR: in WSPR_SCHEDULE line '00:00 KIWI_0,80 KIWI_0,40 KIWI_0,30 MERGED_0_1,20 MERGED_0_1,17 MERGED_0_1,15 MERGED_0_1,12 MERGED_0_1,10', job 'MERGED_0_1,17' specifies receiver 'MERGED_0_1' not found in RECEIVER_LIST
ERROR: in WSPR_SCHEDULE line '00:00 KIWI_0,80 KIWI_0,40 KIWI_0,30 MERGED_0_1,20 MERGED_0_1,17 MERGED_0_1,15 MERGED_0_1,12 MERGED_0_1,10', job 'MERGED_0_1,15' specifies receiver 'MERGED_0_1' not found in RECEIVER_LIST
ERROR: in WSPR_SCHEDULE line '00:00 KIWI_0,80 KIWI_0,40 KIWI_0,30 MERGED_0_1,20 MERGED_0_1,17 MERGED_0_1,15 MERGED_0_1,12 MERGED_0_1,10', job 'MERGED_0_1,12' specifies receiver 'MERGED_0_1' not found in RECEIVER_LIST
ERROR: in WSPR_SCHEDULE line '00:00 KIWI_0,80 KIWI_0,40 KIWI_0,30 MERGED_0_1,20 MERGED_0_1,17 MERGED_0_1,15 MERGED_0_1,12 MERGED_0_1,10', job 'MERGED_0_1,10' specifies receiver 'MERGED_0_1' not found in RECEIVER_LIST
++++++++++++++++++++++++++++++++++ # To enable these options, remove the leading '#' and modify SIGNAL_LEVEL_UPLOAD_ID from "AI6VN" to your call sign:
#SIGNAL_LEVEL_UPLOAD="noise" ### If this variable is defined and not "no", AND SIGNAL_LEVEL_UPLOAD_ID is defined, then upload signal levels to the wsprdaemon cloud database
### SIGNAL_LEVEL_UPLOAD_MODE="no" => (Default) Upload spots directly to wsprnet.org
### SIGNAL_LEVEL_UPLOAD_MODE="noise" => Upload extended spots and noise data. Upload spots directly to wsprnet.org
### SIGNAL_LEVEL_UPLOAD_MODE="proxy" => In addition to "noise", don't upload to wsprnet.org from this server. Regenerate and upload spots to wsprnet.org on the wsprdaemon.org server
SIGNAL_LEVEL_UPLOAD="yes" ### If this variable is defined as "yes" AND SIGNAL_LEVEL_UPLOAD_ID is defined, then upload extended spots and noise levels to the logs.wsprdaemon.org database and graphics file server.
SIGNAL_LEVEL_UPLOAD_ID="TI4JWC" ### The name put in upload log records, the the title bar of the graph, and the name used to view spots and noise at that server.
SIGNAL_LEVEL_UPLOAD_GRAPHS="yes" ### If this variable is defined as "yes" AND SIGNAL_LEVEL_UPLOAD_ID is defined, then FTP graphs of the last 24 hours to http://wsprdaemon.org/graphs/SIGNAL_LEVEL_UPLOAD_ID
#SIGNAL_LEVEL_LOCAL_GRAPHS="no" ### If this variable is defined as "yes" AND SIGNAL_LEVEL_UPLOAD_ID is defined, then make graphs visible at http://localhost/
##############################################################
### The RECEIVER_LIST() array defines the physical (KIWI_xxx,AUDIO_xxx,SDR_xxx) and logical (MERG...) receive devices available on this server
### Each element of RECEIVER_LIST is a string with 5 space-seperated fields:
### " ID(no spaces) IP:PORT or RTL:n MyCall MyGrid KiwPassword Optional SIGNAL_LEVEL_ADJUSTMENTS
### [[DEFAULT:ADJUST,]BAND_0:ADJUST[,BAND_N:ADJUST_N]...]
### A comma-separated list of BAND:ADJUST pairs
### BAND is one of 2200..10, while ADJUST is in dBs TO BE ADDED to the raw data
### So If you have a +10 dB LNA, ADJUST '-10' will LOWER the reported level so that your reports reflect the level at the input of the LNA
### DEFAULT defaults to zero and is applied to all bands not specified with a BAND:ADJUST
declare RECEIVER_LIST=(
"KIWI_0 192.168.2.160:8073 TI4JWC EK70wb 6105
KIWI_1 192.168.2.161:8073 TI4JWC EK70wb 6105
MERGED_0_1 KIWI_0 KIWI_1 TI4JWC EK70wb " )
### This table defines a schedule of configurations which will be applied by '-j a,all' and thus by the watchdog daemon when it runs '-j a,all' ev ery odd two minutes
### The first field of each entry in the start time for the configuration defined in the following fields
### Start time is in the format HH:MM (e.g 13:15) and by default is in the time zone of the host server unless ',UDT' is appended, e.g '01:30,UDT'
### Following the time are one or more fields of the format 'RECEIVER,BAND'
### If the time of the first entry is not 00:00, then the latest (not necessarily the last) entry will be applied at time 00:00
### So the form of each line is "START_HH:MM[,UDT] RECEIVER,BAND... ". Here are some examples:
declare WSPR_SCHEDULE_simple=(
"00:00 KIWI_0,80 KIWI_0,40 KIWI_0,30
MERGED_0_1,20 MERGED_0_1,17 MERGED_0_1,15 MERGED_0_1,12 MERGED_0_1,10 " )
###declare WSPR_SCHEDULE_complex=(
### "06:00 KIWI_0,80 KIWI_0,40 KIWI_0,30 MERGED_0_1,20 MERGED_0_1,17 MERGED_0_1,15 MERGED_0_1,12 MERGED_0_1,10" ### KIWI_0 => 7 rx channels (80/40/30/20/17/15/../10), KIWI_1 => 7 rx channels (../40/30/20/17/15/12/10)
### "18:00 MERGED_0_1,80 MERGED_0_1,40 MERGED_0_1,30 MERGED_0_1,20 MERGED_0_1,17 MERGED_0_1,15 KIWI_0,12 KIWI_1,10" ### KIWI_0 => 7 rx channels (80/40/30/20/17/15/12/..), KIWI_1 => 7 rx channels (80/40/30/20/17/15/../10)
###)
### This array WSPR_SCHEDULE defines the running configuration. Here we make the simple configuration defined above the active one:
declare WSPR_SCHEDULE=( "${WSPR_SCHEDULE_simple[@]}" )
|
|
|
|
Re: Local Monitoring
Rob Robinett
Do this:
pi@Maui-Pi85:~/wsprdaemon/uploads.d/wsprnet.d/spots.d $ cd ~/wsprdaemon/uploads.d/wsprnet.d/spots.d
pi@Maui-Pi85:~/wsprdaemon/wsprdaemon.sh -d pi@Maui-Pi85:~/wsprdaemon/uploads.d/wsprnet.d/spots.d $ tail -f uploads.log
210107 0432 0.36 -22 0.28 7.0401518 WA4DT EM94 30 0 7 0
210107 0432 0.63 -7 0.19 7.0401760 KJ6WSM CM98 33 0 1 0
210107 0432 0.17 -27 0.19 7.0401882 KN8DMK EM89 33 0 1 -32
210107 0432 0.55 -8 -0.19 14.0970398 K6MTU CM97 23 0 1 0
210107 0432 0.25 -26 1.09 14.0970972 K7CKW DM42 37 0 4 0
210107 0432 0.46 -16 0.28 14.0971219 W6TOM CM87 23 0 1 0
210107 0432 0.27 -24 0.19 14.0971600 W0YSE DN41 40 -2 4 0
210107 0432 0.19 -28 0.41 18.1060830 KC7OGJ DM33 37 0 1 0
210107 0432 0.24 -24 0.37 21.0960361 N6RQW DM14 23 -1 385 0
Thu 07 Jan 2021 04:36:37 AM UTC: upload_to_wsprnet_daemon() uploading AI6VN/KH6_BL10rx spots file /tmp/wsprdaemon/uploads.d/wsprnet.d/wspr_spots.txt with 14 spots in it.
Thu 07 Jan 2021 04:36:40 AM UTC: upload_to_wsprnet_daemon() successful curl upload has completed. 14 of these offered 14 spots were accepted by wsprnet.org:
210107 0434 0.23 -26 0.71 3.5701796 N6RY DM33 37 0 3 0
210107 0434 0.31 -26 0.11 7.0399906 KM4TLA EM84 0 0 1 0
210107 0434 0.47 -17 0.07 7.0400303 W6LVP DM04 37 0 1 0
210107 0434 0.28 -22 -0.87 7.0400498 DP0POL IG06 37 0 1 0
210107 0434 0.56 -14 0.28 7.0400792 W6SCQ CM98 37 0 1 0
210107 0434 0.24 -21 0.19 7.0401020 9Z4FV FK90 43 0 2 0
210107 0434 0.44 -19 0.66 7.0401065 AE7YQ DM41 37 0 5 0
210107 0434 0.33 -20 -0.32 7.0401381 N8VIM FN42 37 0 1 0
210107 0434 0.18 -30 0.37 7.0401611 W5QJ EM30 23 0 1 0
210107 0434 0.42 -20 0.15 7.0401958 VA7TZ DN09 30 0 1 0
210107 0434 0.14 -22 0.37 10.1402037 N6WKZ CM87 23 0 1 0
210107 0434 0.50 -12 -0.32 14.0970932 AB1K CM98 23 0 1 0
210107 0434 0.17 -26 1.47 14.0970972 K7CKW DM42 37 0 1 -24
210107 0434 0.11 -27 0.37 28.1261781 N6RQW DM14 23 0 1 -8
^C
pi@Maui-Pi85:~/wsprdaemon/uploads.d/wsprnet.d/spots.d $
|
|
|
|
Re: Second KIWI setup?
Edward Hammond
Well, I guess I'm out of touch. I've been running WD for
months. :-) (W3ENR) EH
On 1/5/21 10:12 PM, Rob Robinett wrote:
|
|
|
|
Re: New to WSPR Daemon
Gwyn Griffiths
Hello Greg and welcome to WsprDaemon
I'm pleased that you have found this resource and look forward to future updates on what you have been able to do with the analysis tools you've outlined. I have to say, I was completely unaware of the packages and utilities you list. In part, that's my limited horizon, but I guess it's also an indication of just how many different approaches and tools there are available. Are you happy for me to add the links above, with a short introduction, to the Annex in my Timescale documentation that covers data access options? 73 Gwyn G3ZIL
|
|
|
|
Re: Second KIWI setup?
Gwyn Griffiths
Edward,
Your interests in antenna experiments are very much catered for through Rob's WD script and the Grafana dashboards I've created. To add to Rob's answer with my own example. Having looked at Rob's template, you can see the context for these key lines, where I've substituted *** for the passwords. First the receiver list. The receiver name on the left is included in each spot data row sent to the wsprdaemon database whereas it is the third column that is used as the identifier to wsprnet. In this example I want to identify between the two receivers on wsprnet on some bands, hence the G3ZIL and G3ZIL/S. I'm also creating a merged receiver, where the best SNR between G3ZIL_1 and G3ZIL_2 is reported to wsprnet as G3ZIL; as Rob says, this avoids double reporting to wsprnet. However, the original individual receiver data is available in the wsprdaemon database. declare RECEIVER_LIST=(
"G3ZIL_1 10.0.1.44:8073 G3ZIL IO90hw ****"
"G3ZIL_2 10.0.1.78:8074 G3ZIL IO90hw ****"
"G3ZIL_4 10.0.1.44:8073 G3ZIL/S IO90hw ****"
"MERGED_RX G3ZIL_1,G3ZIL_2 G3ZIL IO90hw ****"
)
And so, we can look at the data from Callsign G3ZIL and receivers G3ZIL_1 and G3ZIL_2 on the Grafana dashboard at http://logs2.wsprdaemon.org:3000/d/MBseDfvMz/merged-receiver-comparisons-from-wsprdaemon-tables?orgId=1&from=now-2d&to=now-1m&var-Callsign=G3ZIL&var-receiver_A=G3ZIL_1&var-receiver_B=G3ZIL_2&var-band_m=20 These dashboards are taking quite some time for initial load and then some panels take a fair time - but I hope that via this comprehensive example dashboard you can see that wsprdaemon really does provide a great starting point for antenna experimentation. Check out more information on our Grafana dashboards at: http://wsprdaemon.org/ewExternalFiles/Setting_up_Timescale_Grafana_dashboards_V2-2.pdf I have dropped you an email to your address on QRZ.com with the password. 73 Gwyn
|
|
|
|
Re: Second KIWI setup?
Rob Robinett
WD fully supports getting spots for 2 or more Kiwis, selecting one set of the best received spots and uploading only one copy of each spot under the single receiver call sign to wsprnet.org.
In addition, WD creates a log file where all spots are listed and a comparison of the SNR of the spots is listed.
Further, all spots from all receives can be recorded in the wsprdaemon.org SQL database for further analysis and text and graphs using SQL and Grafana.
Download WD and you will find in the config file a template for MERGE receivers.
Rob
|
|
|
|
Re: Second KIWI setup?
Edward Hammond
On 1/5/21 5:59 PM, John via groups.io wrote:
I am not clear how to use the "Merge" assignments. I want to avoid double listing the same spots.I'm interested in similar antenna experiments, and have the same question about avoiding duplicate submissions. Of course I could put a suffix on the callsign of one of the Kiwis, but it would be preferable to report both under the same call. I fear, though, that there's no easy answer. EH
|
|
|
|
Re: Second KIWI setup?
Rob Robinett
It appears that all of your rx channels are the same all day, so your config file can be much simpler. mail your config file and I'll fix it up.
My first KIWI is using 8 bands of vertical 10M -80M. Mu wsprdaemon.conf lists: --
|
|
|
|
Second KIWI setup?
John
My first KIWI is using 8 bands of vertical 10M -80M. Mu wsprdaemon.conf lists:
"KIWI_0 192.168.2.160:8073 TI4JWC EK70wb and declare WSPR_SCHEDULE_complex=(
"06:00 KIWI_0,80 KIWI_0,40 KIWI_0,30 KIWI_0,20 KIWI_0,17 KIWI_0,15 KIWI_0,12 KIWI_0,10"
"07:00 KIWI_0,80 KIWI_0,40 KIWI_0,30 KIWI_0,20 KIWI_0,17 KIWI_0,15 KIWI_0,12 KIWI_0,10"
"08:00 KIWI_0,80 KIWI_0,40 KIWI_0,30 KIWI_0,20 KIWI_0,17 KIWI_0,15 KIWI_0,12 KIWI_0,10"
"09:00 KIWI_0,80 KIWI_0,40 KIWI_0,30 KIWI_0,20 KIWI_0,17 KIWI_0,15 KIWI_0,12 KIWI_0,10"
"10:00 KIWI_0,80 KIWI_0,40 KIWI_0,30 KIWI_0,20 KIWI_0,17 KIWI_0,15 KIWI_0,12 KIWI_0,10"
"11:00 KIWI_0,80 KIWI_0,40 KIWI_0,30 KIWI_0,20 KIWI_0,17 KIWI_0,15 KIWI_0,12 KIWI_0,10"
"12:00 KIWI_0,80 KIWI_0,40 KIWI_0,30 KIWI_0,20 KIWI_0,17 KIWI_0,15 KIWI_0,12 KIWI_0,10"
"13:00 KIWI_0,80 KIWI_0,40 KIWI_0,30 KIWI_0,20 KIWI_0,17 KIWI_0,15 KIWI_0,12 KIWI_0,10"
"14:00 KIWI_0,80 KIWI_0,40 KIWI_0,30 KIWI_0,20 KIWI_0,17 KIWI_0,15 KIWI_0,12 KIWI_0,10"
"15:00 KIWI_0,80 KIWI_0,40 KIWI_0,30 KIWI_0,20 KIWI_0,17 KIWI_0,15 KIWI_0,12 KIWI_0,10"...................................
For the schedule. For the second KIWI on the Hex beam I think this will be the new arangement. declare RECEIVER_LIST=(
"KIWI_0 192.168.2.160:8073 TI4JWC EK70wb
KIWI_1 192.168.2.161:8073 TI4JWC EK70WB
and declare WSPR_SCHEDULE_complex=(
"06:00 KIWI_0,80 KIWI_0,40 KIWI_0,30 KIWI_0,20 KIWI_0,17 KIWI_0,15 KIWI_0,12 KIWI_0,10
KIWI_1,20 KIWI_1,17 KIWI_1,15 KIWI_1,12 KIWI_1,10 "
"07:00 KIWI_0,80 KIWI_0,40 KIWI_0,30 KIWI_0,20 KIWI_0,17 KIWI_0,15 KIWI_0,12 KIWI_0,10
KIWI_1,20 KIWI_1,17 KIWI_1,15 KIWI_1,12 KIWI_1,10 "
"08:00 KIWI_0,80 KIWI_0,40 KIWI_0,30 KIWI_0,20 KIWI_0,17 KIWI_0,15 KIWI_0,12 KIWI_0,10
KIWI_1,20 KIWI_1,17 KIWI_1,15 KIWI_1,12 KIWI_1,10 "
"09:00 KIWI_0,80 KIWI_0,40 KIWI_0,30 KIWI_0,20 KIWI_0,17 KIWI_0,15 KIWI_0,12 KIWI_0,10
KIWI_1,20 KIWI_1,17 KIWI_1,15 KIWI_1,12 KIWI_1,10 "
"10:00 KIWI_0,80 KIWI_0,40 KIWI_0,30 KIWI_0,20 KIWI_0,17 KIWI_0,15 KIWI_0,12 KIWI_0,10
KIWI_1,20 KIWI_1,17 KIWI_1,15 KIWI_1,12 KIWI_1,10 "
"11:00 KIWI_0,80 KIWI_0,40 KIWI_0,30 KIWI_0,20 KIWI_0,17 KIWI_0,15 KIWI_0,12 KIWI_0,10
KIWI_1,20 KIWI_1,17 KIWI_1,15 KIWI_1,12 KIWI_1,10 "
"12:00 KIWI_0,80 KIWI_0,40 KIWI_0,30 KIWI_0,20 KIWI_0,17 KIWI_0,15 KIWI_0,12 KIWI_0,10
for the combined schedule. I am not clear how to use the "Merge" assignments. I want to avoid double listing the same spots. John TI4JWC
|
|
|
|
New to WSPR Daemon
Greg Beam <ki7mt01@...>
Hello All,
I just recently found WSPR Daemon ( Very Cool !! ), and I'm very interested in how this will progress over the next SS cycle. I had started a similar project (on a much, much smaller scale) for WSPRnet data. I am (was) mainly focused on using Spark (Scala), PySpark, Apache Arrow, and various utilities to convert those monster CSV files to Parquet / Avro formats; not so much on the visualization ( but that may change now :-) ) I have truck-load of content to add, but, I did start working on a db-init-script for a local PostgreSQL DB (wsprnet, tutorial) and put up a few Scala apps / Py Sample Scripts for CSV conversion testing. I've not added the tutorial tables to the init script yet, but will do soon. The Docs site is far from complete, but, here are few links so folks can see the direction I'm heading (In time there will be visualization plots). I've added a WSPR-Daemon section where things related to this project will go. The concepts are the same for both WSPRnet and WSPR-Daemon in terms of processing data in volume. Some examples:
As I said earlier, there's a ton to be added, including a full tools-installation section for those interested in either project using Spark related tooling. I was planning on doing some Vagrant testing of the Daemon script before the holidays ended, but, I did not get to it. There's just to many fun things to do, and not enough time to do them. Anyway, I look forward to seeing how things progress here with WSPR Daemon ! 73's Greg, KI7MT
|
|
|
|
Re: Example query and analysis using R
Andi Fugard M0INF <almost@...>
Hi Gwyn,
I haven't used Grafana, so I'm not sure. R has a huge number of packages for pretty much every visualisation and statistical analysis in existence, so there's likely to be something. It's also fairly easy to get from a local analysis to a web app, e.g., here is a simple visualisation grabbing the last hour's worth of sent/receives to/from IO91: https://andif.shinyapps.io/wspr_app/ (It also happens to be software I can use!) Anyway, shall have a think :) 73, Andi M0INF
|
|
|
|
Re: HELP - every day from 14h utc it is the time, when uploads are not accepted any more...
ON5KQ
Thanks Rob, for explanation...
I will keep the system running. It was however strange, that wsprnet.org stopped accepting the uploads the last 3 days just after reconfig of the antenna directions (according to wsprdaemon.conf scheduled rearrangement of kiwis) I will check it the next days, if that keeps making problems at 14h utc... I checked, but wsprnet.org never accepted spots from 14h to 15h utc at least on 20m... most likely on all bands, but I didn't check the last... The stored files from that period on 20m disappeared from my PC unfortunately... Ulli, ON5KQ
|
|
|
|
Re: Example query and analysis using R
Gwyn Griffiths
Hello Andi
I'm glad you have found this group and the WsprDaemon database. Thank you for sharing your R example, on how to access, and on how to generate plots. I will include a link to your web page in our documentation. It would be nice to have your views on what visualisations one could program in R that would be useful but are not possible using our Grafana site. 73 Gwyn G3ZIL
|
|
|
|
Re: HELP - every day from 14h utc it is the time, when uploads are not accepted any more...
Rob Robinett
Sometimes wsprnet.org will report that it accepts only some of the uploaded spots and those spots cannot be uploaded by retrying.
It doesn't tell WD why it rejects spots or what those rejected spot are, so there is nothing more WD can do and I then delete the spot files. In contrast, uploads to wsprdaeon.org are completely under our control. To address these problems, I have suggested to Phil that he offer the option to search the extended_spots database rather than the wsprnet scrape.
|
|
|
|
Example query and analysis using R
Andi Fugard M0INF <almost@...>
Greetings,
I just found this database and group - really wonderful. Thanks all for work making it possible. Here's an example showing how to query the db using R: https://inductivestep.github.io/WSPR-analysis/ 73s, Andi M0INF
|
|
|