There are several options that can be specified on the Java command line when launching YAAC to modify its operation, in addition to standard JVM options. The YAAC-specific options appear on the command line after the -jar YAAC.jar part of the command.
java [-JVM_options] -jar YAAC.jar [-YAAC_options]
The most obvious JVM options relevant to YAAC are the
options. The former specifies the maximum amount of heap memory Java
is allowed to use. For YAAC, this typically should be at least 256m
(256 megabytes), and at least 1024 megabytes when importing/compiling
the whole-planet OpenStreetMap file. Smaller amounts can be used for
tiny systems like the Raspberry Pi if the amount of incoming data
(and/or persistence time thereof) is limited.
There are a few YAAC-specific JVM system properties that can be
defined with the
-D option to override certain defaults (primarily in
the OpenStreetMap importer logic), using the
|property name||value meaning|
|sets the locale for language rendering and related changes in the YAAC user interface, overriding the operating system default. This can be used if there is a problem in the rendering being done in the default language locale, so you can switch to another. Note that display text strings are only provided in YAAC in English, German (Deutsch), and incompletely in Russian. All other locales default the text to English, but other aspects of the display (such as number formatting) will still be done in the current locale.|
||Specifies the path to a directory where scratch index files for OpenStreetMap data importing are stored. By default, such files are stored in the configured tile directory; this option should be used when another physical disk is available for the scratch files, so that importing will not be slowed by excessive disk head seeks. There is no benefit in specifying this if the system has only one physical disk drive, and potential additional performance impairment if specifying a different partition on the same disk.|
||Specify when using the File->OpenStreetMap->Download
PreImported Tiles command that a different subdirectory on the
YAAC author's website should be used to download tiles. By
default, the author makes pre-imported tile files available in the
||If the value is "true", don't delete the temporary files when the import is completed. By default, the several gigabytes (potentially) of scratch files are deleted when the import completes. These files are not of use to anyone who is not developing changes to the importer code.|
||If the value is "true", generate an additional debugging file during OSM XML import which logs all map bounding boxes at various geopolitical levels. Not functional for PBF imports.|
||If the value is "true", don't discard certain OpenStreetMap attributes that are helpful in analyzing the OSM data but are not actually used in rendering the map. This will cause generated tile files to be somewhat larger, due to preserving the additional attributes, and will therefore negatively impact OSM rendering times.|
||If the value is "true", go directly to the sorting of imported tiles, skipping the XML or PBF
parsing step. This is useful to preserve work if YAAC is shut down
after parsing is complete but before the generated tiles are
sorted and moved in place of previous versions of the operational
||If defined (regardless of what value is specified for the property) and your system has at least 4 CPU cores available to the Java runtime, YAAC will use an alternate version of the OpenStreetMap renderer that uses parallel threads to read the .ways and .nodes files from disk and compute the rendering. Note that this is only useful if you have a slow disk drive and slow multi-core processor, such that YAAC can render while it is reading, rather than alternately reading the map tile files and rendering them in a single rendering thread. This is experimental, and not guaranteed to improve map rendering performance relative to the single-thread renderer.|
The command-line options specific to YAAC are:
||Erase all of the YAAC configuration data for this profile; if for the nameless profile, erase everything. YAAC will behave as if it was newly installed on a clean system, offering the option of running the configuration wizard to initially configure YAAC.|
||Erase all persisted bulletin messages originated by this copy of YAAC in this profile.|
||Erase all persisted object definitions originated by this copy of YAAC in this profile.|
||Erase all of the interface port definitions (TNCs, GPSs, weather stations, APRS-IS connections, etc.) in this profile. YAAC will ask if you want to run the configuration wizard to define new ports.|
||Erase all of the memorized positions and sizes of different window types in YAAC in this profile, and let the operating system window manager and YAAC use default placements and sizes.|
||Turn on extra tracing messages in the YAAC error log. May impair YAAC's performance due to the extra logging.|
||Turn on selected extra tracing messages in the YAAC error log, rather than enabling all debug
messages. Categories are specified as a comma-separated list of category names.
May impair YAAC's performance due to the extra logging. Some debug categories include:
||Force YAAC to try to use a GUI display. By default, YAAC will attempt to open the graphical windows if a graphical environment is available (on Microsoft Windows and Macintosh OS X, or on Linux and Unix systems where an X server is available).|
||Force YAAC to try to use a GUI display (as with the plain
||Force YAAC to run without a GUI. Not all functionality will be
available. Useful when using YAAC as a stand-alone digipeater or
I-gate where a screen is not available or needed, but YAAC must be configured in
||Run YAAC with the named alternate named configuration profile. By default, YAAC will use the configuration stored in the nameless profile. The name is arbitrary, and can consist of letters, numbers, underscores, hyphens, and a few other punctuation characters; if spaces are used in the name, the name may need to be quoted to prevent the shell from ignoring the part of the name after the first space.|
||Specify the password for opening the keystore. Necessary when
running in -nogui mode when using the SSL APRS-IS port driver,
where the authentication credentials must be extracted from the keystore. Note that this can be
a security risk, as the password can displayed by system utilities that report the command lines
of currently executing commands. If possible, use the
||Specify that YAAC should prompt for the keystore password at
the console used to invoke YAAC. Necessary when
||Specify a non-configured path to the directory tree where pre-imported OpenStreetMap tile files and USGS SRTM terrain files are stored. Typically used only on DVD-ROM or USB memory stick distributions of YAAC, so that sample map data can be provided on the distribution medium.|
||Print out the version of the YAAC program (not counting for any installed plugins) and terminate YAAC.|
||Print out the versions of YAAC and every installed and activated plugin, and terminate YAAC. The output is printed as multiple lines; each line is the name of the plugin (first being the core YAAC program), followed by a TAB character ('\\t' or 0x09) and the version string for that plugin.|
||Specify the default callsign-SSID for YAAC, in case there wasn't an already-configured
port specifying a callsign-SSID. Primarily useful when using the |
||check the current configuration, and, if it does not contain a port definition matching
the specified port_description string, it will create one, taking the port-specific
defaults for any description that is not complete.
The port description string consists of multiple expressions without embedded whitespace (unless mentioned specifically below) separated by semicolon ";" characters. All the semicolons are required even if a particular expression is empty. The first expression (required) will have the following format:
where portType is the case-sensitive name of the port driver, such as
The second expression is a APRS-IS filter expression. This expression can (and must) have spaces between multiple filters; note that such port_descriptions must be quoted to prevent the operating system shell from breaking the port_description at the space.
The third expression is "true" or "false" for whether this port is enabled for operation.
The fourth expression is "true" or "false" for whether flow control (or something overloading the meaning of this field) should be enabled or not.
The fifth expression is a decimal number of the value of the acceptableProtocolsMask bitmask. The interpretation is port-type-specific, and should be left at zero for port types that don't use it.
The sixth expression is two decimal numbers separated by a slash "/" character representing the timeslot offset (relative to the top of the cycle) in seconds and the length of the timeslot cycle in seconds. Negative cycle length indicates that timeslotting is not used, but the values are preserved in case the user wants to turn timeslotting back on.
The seventh expression is a decimal number of the value of the flags bitmask. Bit meanings are port-type-specific.
The eighth expression is a pipe "|" separated list of names of beacon definitions that should be transmitted through this port. Only meaningful for ports capable of transmitting APRS or OpenTRAC packets.
For further details of the exact syntax of the port expression, consult the YAAC source code
Note that the
Overrides any default or explicit specification of the |