Planner bug: Memouts even with specific memory limit #34

New Issue

patrick · 2017-11-29T21:46:26+01:00

patrick commented

2017-11-29 21:46:26 +01:00

Even though I specified a memory limit of 8192 MB to the planner with the option -m 8192, we got multiple memouts (which have an extra tolerance margin of 1024 MB, making for a total, hard limit of 9216 MB).

Multiple examples for reconstructing this issue occurred in the logistics-round-1-strips domain: example 1, example 2, example 3.

Even though I specified a memory limit of 8192 MB to the planner with the option `-m 8192`, we got multiple memouts (which have an extra tolerance margin of 1024 MB, making for a total, hard limit of 9216 MB). Multiple examples for reconstructing this issue occurred in the `logistics-round-1-strips` domain: [example 1](https://git.luehne.de/patrick/tplp-planning-benchmark/commit/6b3f1290dbc2c1c4d530aa1b9513a77c4dd50521), [example 2](https://git.luehne.de/patrick/tplp-planning-benchmark/commit/1cc74043fb19f52ef0e07d3889b738539038c932), [example 3](https://git.luehne.de/patrick/tplp-planning-benchmark/commit/107b16c0f55147f0ec5896941844bcb0fb786437).

patrick added this to the Extended Paper for TPLP Journal milestone 2017-11-29 21:46:26 +01:00

patrick self-assigned this 2017-11-29 21:46:26 +01:00

patrick added the

bug

benchmarks

labels 2017-11-29 21:46:26 +01:00

patrick commented

2017-12-02 03:18:58 +01:00

It seems that this won’t be resolved before the deadline. As the memouts aren’t in favor of the presented planner, we’ll leave it at this for now.

patrick closed this issue

2017-12-02 03:18:58 +01:00

This repo is archived. You cannot comment on issues.