Skip to content

Conversation

AboudyKreidieh
Copy link
Member

they should work now for everyone that had isssue

::

source activate flow
source activate flow-rllab
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is not the case if you're not using rllab; you won't have this env.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

u create the environment during the rllab setup instructions

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this is in the Setting up section for rllab btw, which is totally optional and assumes u've installed rllab

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Mmm, I was confused by the git diff. Okay!

Copy link
Member

@eugenevinitsky eugenevinitsky left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@eugenevinitsky eugenevinitsky merged commit 0a3b7d3 into master Aug 22, 2018
@eugenevinitsky eugenevinitsky deleted the rllab_install branch August 22, 2018 23:15
nskh pushed a commit to nskh/flow that referenced this pull request Aug 25, 2018
kjang96 pushed a commit to kjang96/flow-1 that referenced this pull request Sep 1, 2018
standardizing SUMO file and Ray result names

Flow experiments can have their names specified in two places: `exp_tag` within `flow_params`, and the key in the dict passed to `ray.tune.run_experiments`. This PR ensures that the names are the same, by making sure the latter key is `flow_params["exp_tag"]` and not any other name.

This makes sure that, for a given experiment, the net/cfg files generated by SUMO and the Ray result directories have the same name.
crystalzyan pushed a commit to crystalzyan/flow that referenced this pull request Dec 1, 2018
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.

2 participants