You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
--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.
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
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?
The text was updated successfully, but these errors were encountered: