V1 Release Notes 2020
V1.4.0 November 2020
- Add attribute
Algorithm
to optionally use V2 algorithm. - Add V1 to V2 pass through.
V1.3.0 October 2020
- Add attribute 'PriorRequestID' to make use of matrices caching.
- Add boolean 'CacheMatrices' attribute to enable matrices caching, only useful when its combined with 'PriorRequestID'.
V1.2.8 September 2020
- Fix BD-243 related to not respecting the TotalRuntime constraint for specific problems.
V1.2.7 August 2020
- Fix BD-220 related to the use of too many vehicles.
V1.2.6 July 2020
- Update Map Data (BIN file) and fix v1 tests after map update.
- Fix for OPT-627 related to unplanned jobs.
- Fix BD-108 related to map data.
- Fix BD-198 related to sub-optimal job sequence.
V1.2.5 March 2020
- Fix BD-161 related to multi-day scheduling issues.
V1.2.4 January 2020
- Add Not-Implemented error in V1 when AdditionalTag is used to allocate Vehicle to a specific request.
V1 Release Notes 2019
V1.2.3 November 2019
- Added more validation to
TotalRunTime
andContinueWithoutImprovementTime
, values should be greater than zero. - Fixed the bug BD-133 which is related to invalid driver start time in a bespoke algorithm.
- Fixed the bug BD-135 which is related to not fully correct load sharing between drivers in a bespoke algorithm.
V1.2.2 November 2019
What's Fixed
- The bug BD-126 which is related to location snapping to the map.
- The bug BD-136 which is related to not correct sequence of untagged requests (jobs).
V1.2.1 October 2019
What's Fixed
- The bug BD-134 it is related to problematic lat/lng with too much precision.
V1.2.0 October 2019
What's New
- The
LocationPrecisionMetre
attribute is added which defines the maximum geographic precision that Vortex can recognise.
What's Fixed
- The bug OPT-502 it is related to a non working depot reload feature.
V1.1.1 May 2019
What's New
- Statistical distance model is added which provides better estimations for distances & times.
What's Fixed
- The bug BD-78 validation to invalid times such as
12:-8:25
is added - The bug VOR-7 validation of the optional list of locations if passed.
- The bug VOR-8 validation of the empty list of requests, drivers, depots and vehicles is added.
V1.1.0 March 2019
What's New
- In RESTFul mode, when polling for a result using GET request, HTTP status Accepted (code 202) is returned. HTTP status OK (code 200) is returned only when it is the final result.
- Intermediate results are supported, this can be activated when populating the attribute
EnableIntermediateResults
withtrue
value. Service would response with HTTP code 202 and the latest up-to-date JSON schedule is returned. - Better performance for large problems
- In RESTFul mode, when polling for a result using GET request, both routs /YOUR_REQUEST_ID and /v1/YOUR_REQUEST_ID work fine.
What's Fixed
- Typos in JSON input has been fixed, old misspelled attributes are still working for backward compatibility.
- The bug VOR-3 cleanup unused JSON attributes from documentation such as:
NumberOfBays
- The bug VOR-1 in algorithm is fixed, so it is focusing on optimizing overall cost mainly. The bug is about two far away depots and two available vehicles. The scheduler now is using more resources if it is efficient to do so.
- The bug VOR-2 in multi-day problems is fixed, originally it was leaving jobs unplanned.
- A bug in output JSON, when number of reported unplanned jobs is different from the actual number. Now they are identical.