Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ablation() error  #67

Open
ThomasF59 opened this issue Mar 6, 2024 · 8 comments
Open

Ablation() error  #67

ThomasF59 opened this issue Mar 6, 2024 · 8 comments
Labels
waiting for info The reporter must provide additional information

Comments

@ThomasF59
Copy link

ThomasF59 commented Mar 6, 2024

Hello, 
I'm using the ablation function, but I have an issue ( I'm using version 3.6 not the last because on a cluster used by others). When I run the command, I use a logFile generated by the same version. Then it executes runs (none of them crash), as soon as all first runs have finished, irace returns that I don't understand:

After I get that : 

 ablog <- ablation(iraceResults, seed=1,ablationLogFile="tmp.RDa")
# 2024-03-06 20:19:44 CET: Starting ablation from 1 to 1331
# Seed: 1
batchmode 
sge,pbs,torque,slurm,htcondor 
# Source configuration (row number is ID):
  TimeMove RoomMove RoomsStabilityMove MwMove LMove HeuristicPerLoop Sep1
1        1        1                  1      1     1                3    _
  Accept_Criter_1 End_Criter_1 Sep4 MaxIdle UpperBoundRate CoolRateBound
1               1            0    _       5             NA          <NA>
  LowerBoundRate InitTemp CoolRateTemp CoolScheduleTemp ReheatRate TL_Rate Sep2
1             NA       NA           NA               NA         NA      NA    _
  Accept_Criter_2 End_Criter_2 Sep3 Accept_Criter_3 End_Criter_3 MaxIdle_2
1               2            2    _               3            3        NA
  UpperBoundRate_2 CoolRateBound_2 LowerBoundRate_2 InitTemp_2 CoolRateTemp_2
1             1.15   0.99999985714              0.9         NA             NA
  CoolScheduleTemp_2 ReheatRate_2 TL_Rate_2 MaxIdle_3 UpperBoundRate_3
1                 NA           NA        NA        NA               NA
  CoolRateBound_3 LowerBoundRate_3 InitTemp_3 CoolRateTemp_3 CoolScheduleTemp_3
1            <NA>               NA          3           0.82                  7
  ReheatRate_3 TL_Rate_3
1           10        49
# Target configuration (row number is ID):
     TimeMove RoomMove RoomsStabilityMove MwMove LMove HeuristicPerLoop Sep1
1331        1        0                  1      0     1                3    _
     Accept_Criter_1 End_Criter_1 Sep4 MaxIdle UpperBoundRate CoolRateBound
1331               2            2    _      NA           1.86 0.99999985714
     LowerBoundRate InitTemp CoolRateTemp CoolScheduleTemp ReheatRate TL_Rate
1331           0.79       NA           NA               NA         NA      NA
     Sep2 Accept_Criter_2 End_Criter_2 Sep3 Accept_Criter_3 End_Criter_3
1331    _               2            2    _               0            0
     MaxIdle_2 UpperBoundRate_2 CoolRateBound_2 LowerBoundRate_2 InitTemp_2
1331        NA              3.3   0.99999985714             0.86         NA
     CoolRateTemp_2 CoolScheduleTemp_2 ReheatRate_2 TL_Rate_2 MaxIdle_3
1331             NA                 NA           NA        NA        12
     UpperBoundRate_3 CoolRateBound_3 LowerBoundRate_3 InitTemp_3
1331               NA            <NA>               NA         NA
     CoolRateTemp_3 CoolScheduleTemp_3 ReheatRate_3 TL_Rate_3
1331             NA                 NA           NA        NA
# 2024-03-06 20:19:44 CET: Executing source and target configurations on the given instances (31)...
Erreur : == irace == isTRUE(all.equal(configurations.id, sapply(experiments, getElement,  is not TRUE

    "id.configuration"))) is not TRUE
5: capture.output(traceback(6))
4: irace.internal.error(msg)
3: irace.assert(isTRUE(all.equal(configurations.id, sapply(experiments, 
       getElement, "id.configuration"))))
2: execute.evaluator(experiments, scenario, target.output, src.configuration)
1: ablation(iraceResults, seed = 1, ablationLogFile = "tmp.RDa")
@MLopez-Ibanez
Copy link
Owner

Hi Thomas,

I would need the 'irace.Rdata' file. If you have a 'tmp.RDa' or a "iracedump.rda" file that would be useful as well.

@MLopez-Ibanez
Copy link
Owner

You say you are using version 3.6, but the latest version in CRAN is 3.5. Are you installing from CRAN or from git?

@ThomasF59
Copy link
Author

Here is the zip of my Rda file

ezyzip.zip

@ThomasF59
Copy link
Author

It was already installed but when I do packageVersion("irace"), it is written 3.5 so CRAN I think , common installed

@MLopez-Ibanez
Copy link
Owner

Would it possible for you to test with the version in git? I have fixed lots of bugs and made a lot of improvements. To install open the R console and type:

    install.packages("devtools")
    devtools::install_github("MLopez-Ibanez/irace")

Pay attention to where it is installed. There you can find the folder bin where the ablation executable is. To make sure you are running the git version, you can do ~/R/x86_64-pc-linux-gnu-library/4.1/irace/bin/ablation --version (the path will be different for you). The git version will be something like 3.5.1.9000.XXXX.

@ThomasF59
Copy link
Author

I tried but unfortunately the ubuntu cluster version is so old that R can't be updated and therefore no devtools.
But it doesn't matter, I'll do it manually, using the github code. Generating the configurations to be tested will greatly speed up the work.

@MLopez-Ibanez
Copy link
Owner

Please let me know how it goes. If there is a bug, I am very interested in fixing it. But if the bug is already fixed in git, there are so many changes that I am unlikely to backport it to 3.5. I would like to release the next irace version soon.

@MLopez-Ibanez
Copy link
Owner

MLopez-Ibanez commented Mar 8, 2024

By the way, if the R version in your cluster is at least 3.6, you download the files from git to a folder irace/ and then install the package with

R CMD build --no-build-vignettes irace/
R CMD INSTALL irace_3.5.1.9000.tar.gz

@MLopez-Ibanez MLopez-Ibanez added the waiting for info The reporter must provide additional information label Mar 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
waiting for info The reporter must provide additional information
Projects
None yet
Development

No branches or pull requests

2 participants