Keyboard Shortcuts
ctrl + shift + ? :
Show all keyboard shortcuts
ctrl + g :
Navigate to a group
ctrl + shift + f :
Find
ctrl + / :
Quick actions
esc to dismiss
Likes
Search
inconsistent map behavior
|
I have the current YAAC version running on different machines. On one ( a RPi 4) NWS raster overlay maps are displayed and refreshed every few minutes. On the other, (an x86 machine), the maps do not refresh. If I delete a previously loaded NWS map, and manually load a new one, the map displays. Subsequent maps are not displayed. If I look at the "raster maps" window, I always find the enable box unchecked. This happens even though "enable" is checked after loading the first map. Have I mis-configured the second machine somehow?
73, NX2I
? |
开云体育This sounds like there's some kind of networking issue on your second computer. This can happen when the radar image refresh is attempted and fails. An error message should appear in the YAAC.out file in your log files directory (also viewable
in the Help->About dialog on the Error Log tab, and in the terminal window where you started YAAC if you used one). Whenever you successfully download a radar image, the log should report the refresh time (when NWS says the image will be out-of-date), so you
should be able to predict when YAAC will try to download the image again.
What build of YAAC are you using?
Andrew, KA2DDO
author of YAAC
From: [email protected] <[email protected]> on behalf of John Spoonhower via groups.io <jpspoonhower@...>
Sent: Wednesday, February 19, 2025 7:51:03 AM To: [email protected] <[email protected]> Subject: [yaac-users] inconsistent map behavior I have the current YAAC version running on different machines. On one ( a RPi 4) NWS raster overlay maps are displayed and refreshed every few minutes. On the other, (an x86 machine), the maps do not refresh. If I delete a previously loaded NWS map, and
manually load a new one, the map displays. Subsequent maps are not displayed. If I look at the "raster maps" window, I always find the enable box unchecked. This happens even though "enable" is checked after loading the first map. Have I mis-configured the
second machine somehow?
73, NX2I
?
|
|
Hi Andrew, thanks for the reply. Both machines are running 1.0beta208. On the first (working) system, the error log shows repeated downloads of the NWS map file, e.g.: Wed Feb 19 10:59:42 EST 2025: downloading CONUS_L2_CREF_QCD_20250219_155839.tif.gz took 675d+6223r+9680e msec at Wed Feb 19 10:59:42 EST 2025, update time of NWS radar image is Wed Feb 19 10:59:13 EST 2025, expire=Wed Feb 19 10:59:56 EST 2025 On the other (non-working) machine: I only see the first download and then the listed error: Wed Feb 19 11:16:32 EST 2025: downloading CONUS_L2_CREF_QCD_20250219_161441.tif.gz took 613d+7230r+8184e msec at Wed Feb 19 11:16:32 EST 2025, update time of NWS radar image is Wed Feb 19 11:15:08 EST 2025, expire=Wed Feb 19 11:16:46 EST 2025 renderCurrentRaster: 1 files in 247msec @ zoom=1202457.5 1739981792875 renderCurrentMap[#1]: 60997(631215)/2419790 ways(0ur), 18/222335 nodes, 1 signs, 26 files(0 new,4 missing) in 10107msec @ zoom=1202457.5 [28.947521,-82.23135] java.lang.OutOfMemoryError: Java heap space Wed Feb 19 11:36:34 EST 2025: try#0: connection to localhost/ lost: Socket closed John, NX2I . ....... John On Wed, Feb 19, 2025 at 9:39?AM Andrew P. via <andrewemt=[email protected]> wrote:
|
开云体育Looks like an obvious failure due to not enough memory allocated to the Java runtime on the second machine.?
How much RAM memory does that computer have, and what operating system are you using? Also, what version of the Java runtime are you using? Open a terminal or command window on the system, and at the prompt, type the command
java -version
(Note the space between the "java" command and the "-version" option.)
Assuming the computer has enough memory available, you may need to raise the Java heap limit with a command-line option to the "java" command used to launch YAAC. If the computer doesn't have enough RAM, it may need an upgrade. :-(
Andrew, KA2DDO
author of YAAC
From: [email protected] <[email protected]> on behalf of John Spoonhower via groups.io <jpspoonhower@...>
Sent: Wednesday, February 19, 2025 11:41:57 AM To: [email protected] <[email protected]> Subject: Re: [yaac-users] inconsistent map behavior Hi Andrew,
thanks for the reply. Both machines are running 1.0beta208.
On the first (working) system, the error log shows repeated downloads of the NWS map file, e.g.:
Wed Feb 19 10:59:42 EST 2025: downloading CONUS_L2_CREF_QCD_20250219_155839.tif.gz took 675d+6223r+9680e msec
at Wed Feb 19 10:59:42 EST 2025, update time of NWS radar image is Wed Feb 19 10:59:13 EST 2025, expire=Wed Feb 19 10:59:56 EST 2025 On the other (non-working) machine: I only see the first download and then the listed error:
Wed Feb 19 11:16:32 EST 2025: downloading CONUS_L2_CREF_QCD_20250219_161441.tif.gz took 613d+7230r+8184e msec
at Wed Feb 19 11:16:32 EST 2025, update time of NWS radar image is Wed Feb 19 11:15:08 EST 2025, expire=Wed Feb 19 11:16:46 EST 2025 renderCurrentRaster: 1 files in 247msec @ zoom=1202457.5 1739981792875 renderCurrentMap[#1]: 60997(631215)/2419790 ways(0ur), 18/222335 nodes, 1 signs, 26 files(0 new,4 missing) in 10107msec @ zoom=1202457.5 [28.947521,-82.23135] java.lang.OutOfMemoryError: Java heap space Wed Feb 19 11:36:34 EST 2025: try#0: connection to localhost/ lost: Socket closed John, NX2I
.
.......
John
On Wed, Feb 19, 2025 at 9:39?AM Andrew P. via <andrewemt=[email protected]> wrote:
|
|
Andrew, please see responses below. John On Wed, Feb 19, 2025 at 12:10?PM Andrew P. via <andrewemt=[email protected]> wrote:
|
开云体育When you start YAAC from a command line (either directly, in a script, or in a graphical desktop shortcut), you will want to tweak the launching command line a little to look like this:
java -Xmx512m -jar C:\Users\john\YAAC\YAAC.jar
(I'm assuming your Windows username is "john" and you installed YAAC in the YAAC directory in your home directory.)
Note the -Xmx option; that specifies the maximum amount of memory the Java virtual machine is allowed to claim. In this example, it is authorizing 512 megabytes of RAM (hence the "m" after the 512).
Hopefully,? your system isn't so clogged with other applications that there is that much RAM available for YAAC to use.
Let me know if you still have any issues.
Andrew, KA2DDO
author of YAAC
From: [email protected] <[email protected]> on behalf of John Spoonhower via groups.io <jpspoonhower@...>
Sent: Wednesday, February 19, 2025 12:28:05 PM To: [email protected] <[email protected]> Subject: Re: [yaac-users] inconsistent map behavior Andrew,
please see responses below.
John
On Wed, Feb 19, 2025 at 12:10?PM Andrew P. via <andrewemt=[email protected]> wrote:
|
|
Thanks!. All is working well now. On Wed, Feb 19, 2025 at 1:26?PM Andrew P. via <andrewemt=[email protected]> wrote:
|
|
To see how much heap you really need to have for your particular usage of YAAC, you can open the expert-mode Configuration dialog and enable displaying the memory utilization bar on the Preferences tab. The bar itself will appear on the map window's toolbar. you should have at least a 10% reserve. Note that specifying the -Xmx command-line option only sets the upper limit for Java heap size; if the demand is less, the actual amount of allocated heap (still more than the used heap) may be less than the maximum.
Andrew, KA2DDO author of YAAC ________________________________________ From: [email protected] <[email protected]> on behalf of John Spoonhower via groups.io <jpspoonhower@...> Sent: Wednesday, February 19, 2025 3:50 PM To: [email protected] Subject: Re: [yaac-users] inconsistent map behavior Thanks!. All is working well now. On Wed, Feb 19, 2025 at 1:26?PM Andrew P. via groups.io<> <andrewemt@...<mailto:[email protected]>> wrote: When you start YAAC from a command line (either directly, in a script, or in a graphical desktop shortcut), you will want to tweak the launching command line a little to look like this: java -Xmx512m -jar C:\Users\john\YAAC\YAAC.jar (I'm assuming your Windows username is "john" and you installed YAAC in the YAAC directory in your home directory.) Note the -Xmx option; that specifies the maximum amount of memory the Java virtual machine is allowed to claim. In this example, it is authorizing 512 megabytes of RAM (hence the "m" after the 512). Hopefully, your system isn't so clogged with other applications that there is that much RAM available for YAAC to use. Let me know if you still have any issues. Andrew, KA2DDO author of YAAC ________________________________ From: [email protected]<mailto:[email protected]> <[email protected]<mailto:[email protected]>> on behalf of John Spoonhower via groups.io<> <jpspoonhower@...<mailto:[email protected]>> Sent: Wednesday, February 19, 2025 12:28:05 PM To: [email protected]<mailto:[email protected]> <[email protected]<mailto:[email protected]>> Subject: Re: [yaac-users] inconsistent map behavior Andrew, please see responses below. John On Wed, Feb 19, 2025 at 12:10?PM Andrew P. via groups.io<> <andrewemt@...<mailto:[email protected]>> wrote: Looks like an obvious failure due to not enough memory allocated to the Java runtime on the second machine. How much RAM memory does that computer have, and what operating system are you using? Also, what version of the Java runtime are you using? Open a terminal or command window on the system, and at the prompt, type the command 8 GB; windows 10 home 64 bit.java -version java version "1.8.0_441"Java(TM) SE Runtime Environment (build 1.8.0_441-b07) Java HotSpot(TM) Client VM (build 25.441-b07, mixed mode, sharing) Assuming the computer has enough memory available, you may need to raise the Java heap limit with a command-line option to the "java" command used to launch YAAC. If the computer doesn't have enough RAM, it may need an upgrade. :-( PSE tel me how.Andrew, KA2DDO author of YAAC ________________________________ From: [email protected]<mailto:[email protected]> <[email protected]<mailto:[email protected]>> on behalf of John Spoonhower via groups.io<> <jpspoonhower@...<mailto:[email protected]>> Sent: Wednesday, February 19, 2025 11:41:57 AM To: [email protected]<mailto:[email protected]> <[email protected]<mailto:[email protected]>> Subject: Re: [yaac-users] inconsistent map behavior Hi Andrew, thanks for the reply. Both machines are running 1.0beta208. On the first (working) system, the error log shows repeated downloads of the NWS map file, e.g.: Wed Feb 19 10:59:42 EST 2025: downloading CONUS_L2_CREF_QCD_20250219_155839.tif.gz took 675d+6223r+9680e msec at Wed Feb 19 10:59:42 EST 2025, update time of NWS radar image is Wed Feb 19 10:59:13 EST 2025, expire=Wed Feb 19 10:59:56 EST 2025 On the other (non-working) machine: I only see the first download and then the listed error: Wed Feb 19 11:16:32 EST 2025: downloading CONUS_L2_CREF_QCD_20250219_161441.tif.gz took 613d+7230r+8184e msec at Wed Feb 19 11:16:32 EST 2025, update time of NWS radar image is Wed Feb 19 11:15:08 EST 2025, expire=Wed Feb 19 11:16:46 EST 2025 renderCurrentRaster: 1 files in 247msec @ zoom=1202457.5 1739981792875 renderCurrentMap[#1]: 60997(631215)/2419790 ways(0ur), 18/222335 nodes, 1 signs, 26 files(0 new,4 missing) in 10107msec @ zoom=1202457.5 [28.947521,-82.23135] java.lang.OutOfMemoryError: Java heap space Wed Feb 19 11:36:34 EST 2025: try#0: connection to localhost/127.0.0.1:8000<> lost: Socket closed John, NX2I . ....... John On Wed, Feb 19, 2025 at 9:39?AM Andrew P. via groups.io<> <andrewemt@...<mailto:[email protected]>> wrote: This sounds like there's some kind of networking issue on your second computer. This can happen when the radar image refresh is attempted and fails. An error message should appear in the YAAC.out file in your log files directory (also viewable in the Help->About dialog on the Error Log tab, and in the terminal window where you started YAAC if you used one). Whenever you successfully download a radar image, the log should report the refresh time (when NWS says the image will be out-of-date), so you should be able to predict when YAAC will try to download the image again. What build of YAAC are you using? Andrew, KA2DDO author of YAAC ________________________________ From: [email protected]<mailto:[email protected]> <[email protected]<mailto:[email protected]>> on behalf of John Spoonhower via groups.io<> <jpspoonhower@...<mailto:[email protected]>> Sent: Wednesday, February 19, 2025 7:51:03 AM To: [email protected]<mailto:[email protected]> <[email protected]<mailto:[email protected]>> Subject: [yaac-users] inconsistent map behavior I have the current YAAC version running on different machines. On one ( a RPi 4) NWS raster overlay maps are displayed and refreshed every few minutes. On the other, (an x86 machine), the maps do not refresh. If I delete a previously loaded NWS map, and manually load a new one, the map displays. Subsequent maps are not displayed. If I look at the "raster maps" window, I always find the enable box unchecked. This happens even though "enable" is checked after loading the first map. Have I mis-configured the second machine somehow? 73, NX2I |
to navigate to use esc to dismiss