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

Update mtsac_metaworld_mt50.py #1905

Merged
merged 1 commit into from Aug 20, 2020
Merged

Update mtsac_metaworld_mt50.py #1905

merged 1 commit into from Aug 20, 2020

Conversation

avnishn
Copy link
Member

@avnishn avnishn commented Aug 16, 2020

update the max_episode length of this example.

@avnishn avnishn requested a review from a team as a code owner August 16, 2020 00:53
@avnishn avnishn requested review from ryanjulian and removed request for a team August 16, 2020 00:53
@avnishn avnishn requested review from a team, gitanshu and ziyiwu9494 and removed request for a team August 16, 2020 00:53
@mergify mergify bot requested a review from a team August 16, 2020 00:53
@avnishn avnishn linked an issue Aug 16, 2020 that may be closed by this pull request
@ryanjulian ryanjulian added the backport-to-2020.06 Backport this PR to release-2020.06 label Aug 17, 2020
@mergify mergify bot requested a review from a team August 19, 2020 16:25
@ryanjulian
Copy link
Member

@Mergifyio rebase

@mergify
Copy link
Contributor

mergify bot commented Aug 19, 2020

Command rebase: success

Branch has been successfully rebased

@codecov
Copy link

codecov bot commented Aug 19, 2020

Codecov Report

Merging #1905 into master will increase coverage by 0.04%.
The diff coverage is n/a.

Impacted file tree graph

@@            Coverage Diff             @@
##           master    #1905      +/-   ##
==========================================
+ Coverage   93.42%   93.47%   +0.04%     
==========================================
  Files         192      192              
  Lines       10180    10180              
  Branches     1267     1267              
==========================================
+ Hits         9511     9516       +5     
+ Misses        441      437       -4     
+ Partials      228      227       -1     
Impacted Files Coverage Δ
src/garage/misc/tensor_utils.py 80.70% <0.00%> (+1.75%) ⬆️
src/garage/plotter/plotter.py 63.21% <0.00%> (+3.44%) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update ad4df26...55c664d. Read the comment docs.

@ahtsan ahtsan force-pushed the avnishn-patch-1 branch 2 times, most recently from 679afd0 to 5b8df31 Compare August 19, 2020 23:13
update the max_episode length of this example.
@mergify mergify bot merged commit edf2615 into master Aug 20, 2020
@mergify mergify bot deleted the avnishn-patch-1 branch August 20, 2020 04:31
@ryanjulian
Copy link
Member

@Mergifyio backport release-2020.06

@mergify
Copy link
Contributor

mergify bot commented Aug 20, 2020

Command backport release-2020.06: failure

No backport have been created

  • Backport to branch release-2020.06 failed

Cherry-pick of edf2615 has failed:

On branch mergify/bp/release-2020.06/pr-1905
Your branch is up to date with 'origin/release-2020.06'.

You are currently cherry-picking commit edf2615c.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Unmerged paths:
  (use "git add <file>..." to mark resolution)

	both modified:   examples/torch/mtsac_metaworld_mt50.py

no changes added to commit (use "git add" and/or "git commit -a")

avnishn pushed a commit that referenced this pull request Sep 3, 2020
Backport #1905, #1975, #1908 to fix problems
with max_eval_path_length being not used by
mtsac and sac, and add checking for incorrect
num_tasks being set in mtsac.
avnishn pushed a commit that referenced this pull request Sep 9, 2020
Backport #1905, #1975, #1908 to fix problems
with max_eval_path_length being not used by
mtsac and sac, and add checking for incorrect
num_tasks being set in mtsac.

Timelimit.truncated modified only when necessary

This issue occurs when there are multiple garage
envs that are nested or timelimit truncated = False
is included in the environment keys.
Previously, our timelimit
truncated logic was written with the idea in mind
that the key was only added when a time limit
truncation occured. If an environment already
has timelimit truncated = False in its keys
then the previous behavior was to set Done = True
which is the incorrect behavior.

That was causing performance degradation
in MTSAC and MTPPO/TRPO.

Now Done is only true in the normal/trivial case,
never if timelimit truncated is False.
avnishn pushed a commit that referenced this pull request Sep 11, 2020
Backport #1905, #1975, #1908 to fix problems
with max_eval_path_length being not used by
mtsac and sac, and add checking for incorrect
num_tasks being set in mtsac.

Timelimit.truncated modified only when necessary

This issue occurs when there are multiple garage
envs that are nested or timelimit truncated = False
is included in the environment keys.
Previously, our timelimit
truncated logic was written with the idea in mind
that the key was only added when a time limit
truncation occured. If an environment already
has timelimit truncated = False in its keys
then the previous behavior was to set Done = True
which is the incorrect behavior.

That was causing performance degradation
in MTSAC and MTPPO/TRPO.

Now Done is only true in the normal/trivial case,
never if timelimit truncated is False.
avnishn pushed a commit that referenced this pull request Sep 11, 2020
Backport #1905, #1975, #1908 to fix problems
with max_eval_path_length being not used by
mtsac and sac, and add checking for incorrect
num_tasks being set in mtsac.

Timelimit.truncated modified only when necessary

This issue occurs when there are multiple garage
envs that are nested or timelimit truncated = False
is included in the environment keys.
Previously, our timelimit
truncated logic was written with the idea in mind
that the key was only added when a time limit
truncation occured. If an environment already
has timelimit truncated = False in its keys
then the previous behavior was to set Done = True
which is the incorrect behavior.

That was causing performance degradation
in MTSAC and MTPPO/TRPO.

Now Done is only true in the normal/trivial case,
never if timelimit truncated is False.
mergify bot pushed a commit that referenced this pull request Sep 11, 2020
Backport #1905, #1975, #1908 to fix problems
with max_eval_path_length being not used by
mtsac and sac, and add checking for incorrect
num_tasks being set in mtsac.

Timelimit.truncated modified only when necessary

This issue occurs when there are multiple garage
envs that are nested or timelimit truncated = False
is included in the environment keys.
Previously, our timelimit
truncated logic was written with the idea in mind
that the key was only added when a time limit
truncation occured. If an environment already
has timelimit truncated = False in its keys
then the previous behavior was to set Done = True
which is the incorrect behavior.

That was causing performance degradation
in MTSAC and MTPPO/TRPO.

Now Done is only true in the normal/trivial case,
never if timelimit truncated is False.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport-to-2020.06 Backport this PR to release-2020.06 ready-to-merge
Projects
None yet
Development

Successfully merging this pull request may close these issues.

MTSAC Max Path Length Incorrect
3 participants