@@ -31,12 +31,31 @@ Change Log
3131- [???] "asynch" multienv
3232- [???] properly model interconnecting powerlines
3333
34+
35+ - TODO A number of max buses per sub
36+ - TODO in the runner, save multiple times the same sceanrio
37+
38+
3439[1.10.3] - 2024-xx-yy
3540-------------------------
36- - TODO A number of max buses per sub
3741- TODO Automatic "experimental_read_from_local_dir"
3842- TODO Notebook for stable baselines
39- - TODO in the reset options: datetime start and max number of steps
43+
44+ - [BREAKING] `env.chronics_hander.set_max_iter(xxx) ` is now a private function. Use
45+ `env.set_max_iter(xxx) ` or even better `env.reset(options={"max step": xxx}) `.
46+ Indeed, `env.chronics_hander.set_max_iter() ` will likely have
47+ no effect at all on your environment.
48+ - [BREAKING] for all the `Handler ` (*eg * `CSVForecastHandler `) the method `set_max_iter ` is
49+ now private (for the same reason as the `env.chronics_handler `). We do not recommend to
50+ use it (will likely have no effect). Prefer using `env.set_max_iter ` instead.
51+ - [BREAKING] now the `runner.run() ` method only accept kwargs argument
52+ (because it should always have been like this)
53+ - [FIXED] a bug in the `MultiFolder ` and `MultifolderWithCache ` leading to the wrong
54+ computation of `max_iter ` on some corner cases
55+ - [ADDED] possibility to skip some step when calling `env.reset(..., options={"init ts": ...}) `
56+ - [ADDED] possibility to limit the duration of an episode with `env.reset(..., options={"max step": ...}) `
57+ - [ADDED] possibility to specify the "reset_options" used in `env.reset ` when
58+ using the runner with `runner.run(..., reset_options=xxx) `
4059
4160[1.10.2] - 2024-05-27
4261-------------------------
0 commit comments