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.
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
New OM: ActionSelector #353
base: master
Are you sure you want to change the base?
New OM: ActionSelector #353
Changes from all commits
affcaa3
9a94e8d
9ee72fc
dc813cc
21c2c6d
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
Check warning on line 986 in unified_planning/engines/factory.py
Codecov / codecov/patch
unified_planning/engines/factory.py#L986
Check warning on line 33 in unified_planning/engines/mixins/action_selector.py
Codecov / codecov/patch
unified_planning/engines/mixins/action_selector.py#L31-L33
Check warning on line 40 in unified_planning/engines/mixins/action_selector.py
Codecov / codecov/patch
unified_planning/engines/mixins/action_selector.py#L36-L40
Check warning on line 42 in unified_planning/engines/mixins/action_selector.py
Codecov / codecov/patch
unified_planning/engines/mixins/action_selector.py#L42
Check warning on line 51 in unified_planning/engines/mixins/action_selector.py
Codecov / codecov/patch
unified_planning/engines/mixins/action_selector.py#L51
Check warning on line 59 in unified_planning/engines/mixins/action_selector.py
Codecov / codecov/patch
unified_planning/engines/mixins/action_selector.py#L59
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why two methods (
update
+get_action
) instead of a single oneget_next_action(observation)
?Check warning on line 67 in unified_planning/engines/mixins/action_selector.py
Codecov / codecov/patch
unified_planning/engines/mixins/action_selector.py#L67
Check warning on line 76 in unified_planning/engines/mixins/action_selector.py
Codecov / codecov/patch
unified_planning/engines/mixins/action_selector.py#L76
Check warning on line 85 in unified_planning/engines/mixins/action_selector.py
Codecov / codecov/patch
unified_planning/engines/mixins/action_selector.py#L85
Check warning on line 160 in unified_planning/model/contingent/contingent_problem.py
Codecov / codecov/patch
unified_planning/model/contingent/contingent_problem.py#L159-L160