# The MDVRP application can be executed by invoking the docker directly:
docker run --rm -v /ABSOLUTE_PATH_TO_MDVRP_APP:/MDVRP bapdock /MDVRP/src/run.jl /MDVRP/data/toy.vrp -u 229 -o /MDVRP/sol/toy.sol -t /MDVRP/tex/toy.tex

# Interactive mode:
docker run -it --rm -v /ABSOLUTE_PATH_TO_MDVRP_APP:/MDVRP bapdock

# Help with command line arguments
docker run --rm -v /ABSOLUTE_PATH_TO_MDVRP_APP:/MDVRP bapdock /MDVRP/src/run.jl --help

# It is possible to run a batch of instances:
docker run --rm -v /ABSOLUTE_PATH_TO_MDVRP_APP:/MDVRP bapdock /MDVRP/src/run.jl -b /MDVRP/A.batch

# The application directory (/ABSOLUTE_PATH_TO_MDVRP_APP) was mounted with -v as /MDVRP inside the container. Also, it is possible to mount a different directory to read/write solutions:
docker run --rm -v /ABSOLUTE_PATH_TO_MDVRP_APP:/MDVRP -v /ABSOLUTE_PATH_TO_OUTPUT:/OUT bapdock /MDVRP/src/run.jl /MDVRP/data/toy.vrp -u 229 -o /OUT/toy.sol

# If you are calling docker through a bash terminal (e.g. Linux, MacOS or Docker QuickStart Terminal), you can call the script named VRPSolver in the demo directory. For example:
./VRPSolver data/toy.vrp -u 229 -o sol/toy.sol -t tex/toy.tex 

# If you don't have permission to run VRPSolver script, call "chmod +x VRPSolver" before.
# This script must be called in the root directory of the application.

# Interactive mode:
./VRPSolver -it

# Help with command line arguments
./VRPSolver --help

# Running a batch of instances (see all.batch before for adjustments):
./VRPSolver -b all.batch

# Files with the extension .sh contain the call of VRPSolver for all instances individually.
