Hi,
In general, Gecode has no support for working within a set amount of
memory. Any backtracking search (whether it is Gecode, some other
constraint programming system, or some other type of solver for
combinatorial problems) may need memory that is proportional within
some constant to the depth of the tree, and the representation of the
problem will naturally depend on the size of the problem. Neither of
these are knowable beforehand, so the simple answer is that it is not
possible.
There are some things that you can do though that might work well
enough depending on the problems that you solve:
* You can change the memory allocator that Gecode uses to one that
allocates from a pre-allocated slab of memory, and fails if Gecode
requests more memory than what is available.
* By changing the copying distance and the adaptive copying distance
to very large numbers, you can ensure that the search engine
essentially only keeps the root Space and the current Space used for
exploration. This will be a full recomputation search, which might
take more time, but might also be usable still.
See more about memory and search configuration in MPG.
Cheers,
Mikael
> --
> You received this message because you are subscribed to the Google Groups "Gecode" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to
gecode+un...@googlegroups.com.
> To view this discussion on the web visit
https://groups.google.com/d/msgid/gecode/0e9174a0-7d1e-420f-81dc-4a39a584ab6an%40googlegroups.com.
--
Mikael Zayenz Lagerkvist