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

Why do we need '--metric period =200' for evaluation? #32

Open
HaoZhouGT opened this issue May 25, 2021 · 3 comments
Open

Why do we need '--metric period =200' for evaluation? #32

HaoZhouGT opened this issue May 25, 2021 · 3 comments

Comments

@HaoZhouGT
Copy link

Hi can you guys explain the setting of --metric_period 200 for evaluation? Does it mean we don't care the delay or throughput of the network after 2000s? Why not using --metric_period 359 for the whole period?

@Kanstarry9T
Copy link
Contributor

--metric_period=200 means that we currently evaluate your solution every 200 seconds for scoring. You can set this parameter for your own needs.

@HaoZhouGT
Copy link
Author

--metric_period=200 means that we currently evaluate your solution every 200 seconds for scoring. You can set this parameter for your own needs.

Hi Kan, do you imply we can change this setting? I assume this is not modifiable. Also I found only by adding --metric_period=200 we can get the same result as the server does.

@Kanstarry9T
Copy link
Contributor

Yes, you can modify --metric_period, for example, --metric_period=100 means that evaluate your solution locally every 100 second, but please be notified currently, the scoring system evaluate your solution every 200 seconds. Also if you have any further questions, please join our Q&A session 06/02/2021 9:00PM (Beijing time) or 9:00 AM (Atlanta, EDT) https://bluejeans.com/895107273/0765

@Kanstarry9T Kanstarry9T reopened this Jun 2, 2021
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