-
Notifications
You must be signed in to change notification settings - Fork 117
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
Version 1.10.2 #611
Merged
Merged
Version 1.10.2 #611
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…er to find suitable versions
…er to find suitable versions
…er to find suitable versions
… the default behaviour [skip ci]
…paring observation or action
… fix broken tests
…need testing [skip ci]
Add 90% of the "init state" feature
Upgrade to 1.10.2.dev3
Ready for version 1.10.2
Ready for version 1.10.2
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
runner.run_one_episode
now returns an extra first argument:chron_id, chron_name, cum_reward, timestep, max_ts = runner.run_one_episode()
whichis consistant with
runner.run(...)
(previously it returned onlychron_name, cum_reward, timestep, max_ts = runner.run_one_episode()
)chronics_handler
attribute (runner.chronics_handler
is not defined)
param.IGNORE_INITIAL_STATE_TIME_SERIE == True
(NOT the default) andno initial state is provided in
env.reset(..., options={"init state": ...})
change_reward
directly froman observation (no need to do it from the Observation Space)
is not needed anymore): you can use
obs.change_reward
experimental_read_from_local_dir
flags(with automatic class creation). For now it is disable by default, but you can
activate it transparently (see doc)
"time series" classes. The supported classes are
GridStateFromFile
- and all its derivative,FromOneEpisodeData
,FromMultiEpisodeData
,FromNPY
andFromHandlers
. The classesChangeNothing
and
FromChronix2grid
are not supported at the moment.JSONInitStateHandler
) that can set the grid to an initial state (so as to makecompatible the
FromHandlers
time series class with this new feature)GridObject
classPandaPowerBackend
(and add some basic tests)
param.IGNORE_INITIAL_STATE_TIME_SERIE
) which defaults toFalse
that tells the environment whether it should ignore theinitial state of the grid provided in the time series.
By default it is NOT ignored, it is taken into account
(for the environment that supports this feature)
"redispatching_unit_commitment_availble" flag set even if the redispatching
data was not loaded correctly
(instead of pandas series)
EpisodeData
): when there were no storage unitson the grid it did not set properly the "storage relevant" class attributes
grid layout was set
EpisodeData
.BaseMultiProcessEnvironment
: set_filter had no impactRunner
(self.chronics_handler
was sometimes used, sometimes notand most of the time incorrectly)
RemoteEnv
class (impact all multi process environment): the kwargs used to build then backendwhere not used which could lead to"wrong" backends being used in the sub processes.
different: it was not possible to set
names_chronics_to_grid
correctly when callingenv.make
obs.simulate
to make it clearer thedifference between env.step and obs.simulate on some cases
GridObjects
np.nonzero(arr)
calls witharr.nonzero()
which couldsave up a bit of computation time.
classes are initialized from the backend.
(creation of multiple environments, grid2op compatibility mode)
(improved test
AAATestBackendAPI.test_01load_grid
)