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

fixed_env vs env #145

Open
ahmad-hl opened this issue Dec 23, 2021 · 1 comment
Open

fixed_env vs env #145

ahmad-hl opened this issue Dec 23, 2021 · 1 comment

Comments

@ahmad-hl
Copy link

What is the difference between env.py and fixed_env.py?
I feel they are doing the same job!

@hongzimao
Copy link
Owner

Doing a diff env.py fixed_env.py you will see something like

33c31
<         self.trace_idx = np.random.randint(len(self.all_cooked_time))
---
>         self.trace_idx = 0
36a35
>         self.mahimahi_start_ptr = 1
39c38
<         self.mahimahi_ptr = np.random.randint(1, len(self.cooked_bw))
---
>         self.mahimahi_ptr = 1

fixed_env.py is loading traces sequentially in order. It's just for easier testing and comparing results after training.

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

No branches or pull requests

2 participants