Hello all,
I am working on vrpRouting:
- Reading the inner queries on the C++ code. Thus avoiding some 3X memory usage.
- Before
- X storing on C structure
- X copying into a C++ container
- X copying into the final location of the information
- Before
- Intention of this work:
- X storing into a C++ container
- X copying into the final location of the information
Because of this work many things were noticed.
About Google Summer of Code work
Being the first one that the work done for v0.4.0 which includes the work of Manas from Google Summer of code using or-tools was not tagged after the job was finished.
We need to create the tag because it involves the Google Summer of Code students code and @krashish8 just created the tag as is.
About the tags
- v0.3.0 was coded for VROOM 1.11.0, and works for that version
- v0.4.0 was coded for VROOM 1.12.0, and for or-tools for a version that I could not figure out, unfortunately was not documented, and with the latest version 9.10.4067 it does not work.
Therefore currently v0.4.0 or-tool functions are not usable with or-tools 9.10.4067.
It does not work for the newest versions of VROOM
Failing functions
- or-tools functions
- vrp_knapsack
- vrp_bin_packing
- vrp_multiple_knapsack
- ported from pgrouting:
- vrp_onedepot
Build
- vrpRouting do not use boost
CI
- Do not use appveyor anymore
- The actions need update like
checkout@v2→checkout@v4 - Separate the update of locale from building the documentation on the website
- No boost test is needed, as it does not use boost.
Testing data
Some data are stored locally on the pgtap directory
- Move it to the testers directory
- Fix some of the data
New way of reading the inner queries
- The original intention of the work that is ongoing
The process of fixing all the issues found will be done directly on the main branch
Where the first things to tackle is:
- Make the failing functions work
- Update/Rename the actions
- Update the testing data.
Once it is working again, a tag 0.4.1 will be created and the work where the inner queries are read on the C++ will be done for 0.4.2
Probably it will be done on a series of PR to make it easier for the reviewers. It a big change and almost all the files are modified.
What this work will not cover
The work will not cover to make it work for VROOM v1.13.0 or v.14.0 or any new VROOM versions.
Regards
Vicky