It seems that there is a serious bug.
[opengm]/build/src/interfaces/commandline/double/opengm_min_sum -a ADSal --maxIt 1000 -m models/triplepoint4-plain-ring-inverse.h5:gm -o results/triplepoint4-plain-ring-inverse.h5 -p 100 -v --timeout 180 --gaplimit 0.01--threads 1
Results:
Warning: Argument "memlogging" not set. Using default value: 1
Warning: Argument "precision" not set. Using default value: 0
Warning: Argument "relative" not set. Using default value: 0
Warning: Argument "lazyLPPrimalBoundComputation" not set. Using default value: 0
Warning: Argument "lazyDerivativeComputation" not set. Using default value: 0
Warning: Argument "slowComputations" not set. Using default value: 0
Warning: Argument "noNormalization" not set. Using default value: 0
running ADSal caller
begin: value inf bound -inf mem 37.676 MB
oracleCalls 37
Segmentation fault
I tried running ADSal on the benchmark and observed that it was able to solve only a (very) few instances. I just picked up some concrete instances to check and came up with the bug.
Thanks.