https://fmt.dev/11.1/get-started/#debianubuntu
apt install libfmt-dev

/home/mateus/R/x86_64-pc-linux-gnu-library/4.1/irace/bin/irace > out

git rm -r /home/mateus/WSL/IC/SSP/input/raw/KTNS
git rm -r --cached /home/mateus/WSL/IC/SSP/input/raw/KTNS/SolList/Files/*
git lfs track "/input/raw/KTNS/*"

------------------------------------------------
DEBUG
------------------------------------------------

gdb src/out/mainCppDebug
run "./input/MyInstancesSameToolSets/n=75,p=0.24,r=0.5,t=650,v0.csv" "./input/Processed/ToolSetInt.csv" "./output/Exemplo/pt.csv" --PTL_TEMP_UPDATE_PROPORTION 3 --DIFERENT_TOOLSETS_MODE 0 --TEMP_INIT 0.1 --TEMP_FIM 5 --N_REPLICAS 11 --MCL 500 --PTL 100 --PASSO_GATILHO 10 --TEMP_DIST 3 --TYPE_UPDATE 1 --INIT_SOL_TYPE 0 --TEMP_UPDATE 3500 --PTL_TEMP_UPDATE_PROPORTION 3

------------------------------------------------
DADOS
------------------------------------------------

screen
Ctrl+A, then D
screen -ls
screen -r [session_id]
screen -X -S session_name_or_id quit

screen -r 1058641.pts-0.abstergo
screen -r 149791.pts-0.ecorp

tmux new -s pt
tmux attach -t pt
detach shortcut: Ctrl+B, then D

------------------------------------------------
DADOS
------------------------------------------------

lscpu
lsb_release -a

/home/mateus/R/x86_64-pc-linux-gnu-library/4.1/irace/bin/irace
/home/marco/R/x86_64-redhat-linux-gnu-library/3.6/irace/bin/irace

./src/out/mainCppDebug ./input/MyInstancesSameToolSets/n=75,p=0.24,r=0.5,t=650,v0.csv ./input/Processed/ToolSetInt.csv ./output/Exemplo/output1.txt --TEMP_INIT 0.2 --TEMP_FIM 1 --N_REPLICAS 16 --MCL 400 --PTL 100 --TEMP_DIST 1 --TYPE_UPDATE 2 --TEMP_UPDATE 35000 --CAPACITY 80 --MACHINES 2 --DAYS 2 --UNSUPERVISED_MINUTS 720 --RESULT_REPORT 1 --INSTANCE_REPORT 1
gprof ./src/out/mainCppDebug gmon.out > analysis.txt

ssh-copy-id username@server_address

------------------------------------------------
DADOS
------------------------------------------------

sshuttle -r mateus@200.239.132.108:4096 0.0.0.0/0
sshuttle -r marco@200.239.139.180:9229 0.0.0.0/0
sudo docker run --rm -it --network host --name=firefox -p 5800:5800 -v /docker/appdata/firefox:/config:rw jlesage/firefox
curl ifconfig.me

------------------------------------------------
RODAR
------------------------------------------------

python ./scripts/reportAnalises.py ./output/Exemplo/pt.csv 6
python ./scripts/reportAnalises.py ./output/Exemplo/pt.csv 7












Where can I find information about the different operations, i. e., which jobs are reentrant or not? For example, the first base case has 250 jobs and 376 operations. The data file has 250 rows, but I cannot figure out where to find the information about the 376 operations.
First we set a “setup_max” parameter {2M1: 0.5, 6M1: 0.6, 6M2:0.4}
Second we iterate over the jobs from 1 to 250 and generate jobs. If 1 setup 1 job, if 2 setups 2 jobs until we reach 376 jobs
The decision for 1 or 2 jobs is made with the following variable:
calculation = nr of jobs with 2nd setup / (nr of jobs – nr of jobs with 2nd setup + 1)
If calculation > setup_max è setups = 1, else è setups = 2
 

Where can I find information about job types, i. e., which jobs are priority and which are regular?
First we assign the priority level = 0.5
Same iteration as with nr setups per job. So from job 1 to job 250
calculation = Amount of priority jobs /  amount of priority jobs + amount of regular jobs + 1
If calculation < priority level è append job to priority jobs, else è append to regular jobs
 
 

Unsupervised shifts are considered to start at instant 24-t_U?
Yes exactly
 

Where can I find information about priority ratio, tool ratio and reentrant operations ratio, i. e., which jobs, tools and operations are selected when these ratios vary as indicated in the paper? Is it possible to reproduce the instances? 
Priority ratio and reentrant ratio (setup_max) is mentioned above. The assignment is as per method above.
The tool ratio is the list of unique tools. From job 1 to n we append the unique tools to the list. At the end we calculate the tool ratio
If tool ratio is too low è               1. we iterate over the existing jobs
2. we iterate over the tl references from id = 0 to id =n.
3. If a tool in that tl is not part of unique tools and nr of tools for that job fit in tool capacity, it is added to the TL of the current iterated job
3b. If other jobs also require the TL of that job, also the tool is added in that job
                If tool ratio is too high è              1. We iterate over existing jobs
                                                                                2. If the length of tool set > t_min è {2M1: 2, 6M1: 10, 6M2: 5}, we remove the tool for the TL                                                           
 
 
The magazine capacity is set as 80. However, some tool sets seem to have more than 80 tools, e. g., from instance 6M1401: TL51, TL52, and TL88. Particularly, TL51 seems to have 127 tools and is used by 4 different jobs. In this case a different magazine capacity is considered?
No tool capacity remains the same. If the tool set is too large, we assign a random TL to that job.