SCIP custom settings not loaded
I have defined configurable options in scip.set file and placed it in myscipdir / settings.
Settings contain
limits/time = 86400
limit/memory = 61440
lp/threads = 6
However SCIP doesn't seem to load the configured parameters, instead
- the default settings are used (see attached image) and
- the options file was not found in the / check / results directory.
May I know how to do this correctly? I can set the time and memory limits from the test command line, but I also need to set more threads.
Note that in the figure SCIP said "scip.set user options file not found - using default options", this is misleading because on the next line it said "loaded options file ...". If scip.set is really not in / settings, SCIP throws an error message indicating that the file was not found and is not aborted.
source to share
This is more than that. I remember that you ran automated tests using make test
SCIP functionality (by the way, you should always mention in your question). The options you provide are read, but then overwritten again (as usual, the magic happens in "check / configuration_tmpfile_setup_scip.sh", see also your related question ).
Instead, you must pass these specific configuration parameters as parameters make
like this:
make test TIME=86400 THREADS=6 MEM=61440 [optional: SETTINGS=scip]
If you don't pass these flags, they are (currently) default
- TIME = 3600
- MEM = 6144
- THREADS = 1
You will find the definitions under "make / make.project". Some of the more readily available (in your case, perhaps readable) options are found in the Advanced Options section on How to Run Automated Tests .
This is a way to prevent the accidental use of settings with unwanted time constraints (possibly even infinite limits) during automated tests. I admit that this might sound a little tricky. While this approach has saved us an almost infinite amount of CPU processing time, we have on our agenda to make both the test system and its availability easier.
Your bonus question about SCIP reading behavior in settings files: the confusion comes from the fact that you named your settings "scip.set". Each time you open an interactive shell, SCIP will look for custom settings in the current working directory of that name, but use the default settings if no such file exists. If, however, you specify a settings file using the SETTINGS
-flag, but if the test script cannot find that file in the settings directory, the script aborts saving the computation time with non-existent settings.
EDIT1: By the way: since you are using SoPlex as your LP solver, you don't need to worry about the LP thread number; SoPlex is single threaded.
source to share