Skip to content
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

[RLlib] Fix custom multi action distr #13681

Merged
merged 13 commits into from
Jan 28, 2021

Conversation

sven1977
Copy link
Contributor

@sven1977 sven1977 commented Jan 25, 2021

Fix custom multi action distr.

Re-vival of this closed PR by zseymour: #11868

When config["custom_action_dist"] is a subclass of MultiActionDistribution or TorchMultiActionDistribution, dst_class became a tuple of (partial, int), resulting in

AttributeError: 'tuple' object has no attribute 'required_model_output_shape'
This pull request instead causes ModelCatalog._get_multi_action_distribution to always return a tuple and returns directly from L148, bypassing the later return that threw the error.

Why are these changes needed?

Related issue number

Checks

  • I've run scripts/format.sh to lint the changes in this PR.
  • I've included any doc changes needed for https://docs.ray.io/en/master/.
  • I've made sure the tests are passing. Note that there might be a few flaky tests, see the recent failures at https://flakey-tests.ray.io/
  • Testing Strategy
    • Unit tests
    • Release tests
    • This PR is not tested :(

@sven1977 sven1977 merged commit 4bc257f into ray-project:master Jan 28, 2021
fishbone pushed a commit to fishbone/ray that referenced this pull request Feb 16, 2021
fishbone added a commit to fishbone/ray that referenced this pull request Feb 16, 2021
fishbone added a commit to fishbone/ray that referenced this pull request Feb 16, 2021
@sven1977 sven1977 deleted the fix_custom_multi_action_distr branch June 2, 2023 20:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants