Closed DE0CH closed 1 year ago
The problem is this option, I guess:
perturbation_constant "" r,log (0.00000001,0.0001)
It probably gets rounded to 0 due to digits.
This is a very weird parameter, it would be better to use an int and generate 10^-p.
Let me take a look this weekend.
If you want to get around the bug for now, just use digits=15 in scenario.txt. It probably doesn't make much of a difference for this scenario.
Hi Manuel,
I was working on the meta irace tuning project and I encountered this bug. Since I was not sure if my code in
iracepy
was buggy, I reproduced the bug with the development version of irace (devtools::install_github('MLopez-Ibanez/irace')
) and used the good old command line.The bug diappeared when I set
digits
to a large value, and in withirace
in CRAN, it detected that the lower bound forperturbation_constant is 0 when the scale is set to log, threw an error and stopped. So I suspect it rounded it to 0 but escaped a check to check if it's 0 and failed elsewhere.Below is the details of the things needed to reproduce the bug and a full traceback.
Folder structure:
parameters.txt
:scenario.txt
:target-runner
:Traceback: