From c0315161670e271c4a80eaab462af9a4f2efb0cb Mon Sep 17 00:00:00 2001 From: Loïc Guégan Date: Tue, 23 Sep 2025 14:00:45 +0200 Subject: Correct Readme --- README.md | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/README.md b/README.md index 830765c..5263ad7 100644 --- a/README.md +++ b/README.md @@ -8,15 +8,16 @@ - `simulation/` - Contains the simulator source code and script to run the experiments from the paper. - `slides_recap/` - - Just backup slides. Nothing interresting. + - Just backup slides. Nothing interesting. ## Experiments ### In-situ -Simulations are carried using previous CCGrid2022 date in the file `analysis/in-situ.R`. -The idea is to use a single policy each day (round-robin) until model performance reaches 89%. -For that, a day correspond to a single simulation from CCGrid2022 with a particular policy. +Simulations are carried using previous CCGrid2022 data. +These simulations are done in the file `analysis/in-situ.R`. +The idea is to use a single policy each day (round-robin) until the model performance reaches 80%. +For that, a day corresponds to a single simulation result from CCGrid2022 with a particular policy. Since we have 200 runs per policy from CCGrid2022, a single run result can be cherry-pick to simulate one day. ### Offline @@ -24,6 +25,6 @@ Since we have 200 runs per policy from CCGrid2022, a single run result can be ch First, models are trained and predictions are generated. This is done in `analysis/offline.R`. Predictions are stored in `analysis/inputs/input_*.csv`. -Then simulation are executed with those policies predictions as inputs. +Then, simulations are executed with those policy predictions as inputs. This is done in `simulations/results/paper.sh`. -- cgit v1.2.3