AccessMod Replay

Changes were done in AMRemote to make the process for the user and the code management much easier.

Major change:

• The user modifies manually a JSON file (few parameters, only two mandatory), and then, they always run the same bash script, regardless the machine and the analysis . Overall, this script will check the parameters and the machine on which the script is being executed and will launch Docker or Singularity accordingly and submit regular jobs or job arrays (multiple nodes) when applicable.

New features:

• When required, a ZonalStat analysis can be run right after the accessibility analysis.
• A parameter allows the user to run an analysis on a regular server on the background. They can then close the terminal without killing the process.
• Provided path in the inputs.json file can be relative or absolute.
• In the cluster jobs are automatically sent to different nodes when splitting by region and/or when having multiple maximum travel times.
• A json file is editable for advanced user to modify the sbatch parameters when using the cluster (non-advanced users can leave the default values).
• Docker is now run as a non-root user. Therefore, the outputs created in the server are now owned by the user who has full rights to them.
• All parameters used for the replay are saved within the output folder, as well as a file with all the standard outputs and errors (when running in background).