Skip to content

mdeboute/VRPWD

Folders and files

NameName
Last commit message
Last commit date

Latest commit

Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 

Repository files navigation

Vehicle Routing Problem With Drones (VRPWD)

Here is the french subject of the La Poste VRP With Drones project. Here is the french report of the project. And finally, here is the french presentation of the project.

You'll need to have Python 3.8+ installed. Don't forget to do a pip install -r requirements.txt before running the code.

For the main program:

  • Type python3 src/vrpwdSolver.py -h for help.

For the benchmark (don't forget to do a chmod +x benchmark.sh):

  • Type ./benchmark.sh -h for help.

Coding Rules

To ensure consistency throughout the source code, keep these rules in mind as you are working:

  • All features or bug fixes must be tested by one or more specs (unit-tests).
  • All public API methods must be documented.
  • Don't push your work on the master branch.
  • Don't push code that are not working, that are not tested or that are in comments.

Commit Message Format

This specification is inspired by and supersedes the AngularJS commit message format.

We have very precise rules over how our Git commit messages must be formatted. This format leads to easier to read commit history.

Each commit message consists of a header.

The header must conform to the Commit Message Header format below.

Any line of the commit message cannot be longer than 100 characters.

Commit Message Header

<type>(<scope>): <short summary>
  β”‚       β”‚             β”‚
  β”‚       β”‚             └─⫸ Summary in present tense. Not capitalized. No period at the end.
  β”‚       β”‚
  β”‚       └─⫸ Commit Scope: db|algo||instances|tests|utils|...
  β”‚
  └─⫸ Commit Type: docs|feat|fix|perf|refactor|test|...

The <type> and <summary> fields are mandatory, the (<scope>) field is optional.