Checking the "Show advanced settings" box in the Settings module allows you to access the following information and capabilities:
(o) The “System information” part of the panel lists useful metrics of disk usage:
- “Free”: available disk space in the AccessMod Virtual Machine (VM), in GB and percentage of total available
- “Free”: currently used disk space in the VM, in GB and percentage of total available
- “Total”: Total disk space in the VM, in GB. The default disk space allocated to the AccessMod VM when importing it in VirtualBox is 40 GB.
(1) The “AccessMod version” part of the panel lists some information linked to the version of AccessMod and the Github code repository. This is mostly useful for AccessMod developers to check that there are no issues with the versions:
- Branch: Identify the name of the code branch on Github from which the current version of AccessMod you have installed on your computer is coming from. The “devel” or "master" branch (depending on the version) is the main branch for AccessMod.
- Revision local: The unique identifier attached to the revision currently installed on your computer, "658d2c7" in the example here above.
- Revision fetched: The unique identifier for the latest revision accessible from the online repository. A different identifier compared to the one reported under "Current revision" means that an update is available. The presence of the same identifier between the two fields means that the latest update is already installed on your computer
- Node name: an internal code name for the Github node under which AccessMod is located.
(2) The “Install update” button installs the latest revision when one is available. When you click on it, the update will take place and will inform you when the update is finished.
(3) The “Restart AccessMod” button restarts AccessMod. Clicking on it will restart AccessMod in the virtual machine, and will therefore reload AccessMod in your browser. This can be useful in some rare instances when AccessMod becomes unstable (i.e., crashes easily).
(4) The “Clear cache and restart” button clears the cache and restarts AccessMod. Compared to the previous button, this one will delete the cached (stored) images that were previously generated by the "Raster Preview" module. This will free some disk space and can resolve issues where the displayed images in the "Raster Preview" do not correspond to the latest results (for example, when you have performed the same analysis, with the same associated tags, twice). In some rare instances, clearing the cache can also allow erratic behavior of the data module.
(5) The “Show expert options” check box allows for the opening of the expert options of AccessMod. These options complement the advanced ones and are dedicated to users who have a good level of understanding of AccessMod.
(6) The “Temporary limit for data importing (Megabytes)” field allows for the expansion of the data importing limit. By default, this limit is set to 300 Megabytes (per individual imported layer), but it can be extended to a larger number (up to 1’000 Megabytes) if you need to import a larger file. It is nevertheless important to note that increasing this limit and importing a very large file may result in making AccessMod slow or unstable (depending on the hardware characteristics of your machine, and especially if you have a limited amount of RAM).
(7) The “Apply the temporary data importing limit” button applies the temporary data importing limit set under point 6.
(8) The “Reload spatial settings” button to reload the spatial data settings. Clicking on this button will allow resetting the projection, resolution, and extent of GRASS based on the DEM. This can be useful in the unlikely event when GRASS will crash in the middle of a function that changes resolution. In such case, GRASS can temporarily have the wrong resolution, and reloading the spatial data settings will correct for that.