Round 2

[kidzik]

The reward in the second round:

• objective is to walk forward but at lower speeds than in the round 1 (0 - 1.5 m/s), the speed will vary in time
• we subtract approximation of the muscle fatigue: a sum of squared muscle activations with a small factor)
• we add small turns (changing the heading of the velocity vector at the rate 20 degrees per second)
• requested velocity will be given in the observation vector
• the task is to get as close as possible to the requested velocity vector in the (X,Z) plane projection
• each trial will last 10 seconds of simulation time

Other updates:

• we extend the first round by 1 month
• we switch to the branch with a few bugfixes https://github.com/stanfordnmbl/osim-rl/tree/ver2.1
• we will send out cloud credits as soon as we figure out logistics

[yobobobo]

How long will the Round 2 last?
Where can we find the extract reward definition like that in https://github.com/stanfordnmbl/osim-rl/blob/ver2.1/osim/env/osim.py#L394

[AdamStelmaszczyk]

@kidzik What are the rules regarding advancing to Round 2?

[mattiasljungstrom]

When are you planning to switch to branch v2.1?
How long will the episodes be in round 2?

[kidzik]

@mattiasljungstrom it'll be around 10 seconds (I've just updated the initial post)
@yobobobo we don't have the exact formula yet, we are tuning the scaling factor for activations
The round itself will be short, but the reward function will be posted this week (almost two months before the end)
@AdamStelmaszczyk we plan to keep it similar as the last year (last year we had ~50 teams)

[kidzik]

That's a rough formula for requested velocity vector (2d projection) in the Round 2:
https://github.com/stanfordnmbl/osim-rl/blob/master/examples/Round%202%20reward.ipynb
We will also subtract the sum of activations squared with a factor of 0.01.
(the notebook is only for visualization of the behavior of the reward, of course, it will be implemented in the repo)

We've received the Google Cloud credits and we will send them out tomorrow.
We will also release the ver2.1 branch.

[yobobobo]

a jupyter-notebook in localhost?

[kidzik]

Fixed, thanks!

[spiglerg]

Will the velocity be clipped to prevent it from going negative?

[kidzik]

We plan to leave the possibility of negative velocity (which happens with very low probability).

[kidzik]

Version 2.1 is now merged with the master branch and deployed on the grader. The reward for the second round might still change. We extended the first round until October 20th.

[wangzhengfei0730]

https://github.com/stanfordnmbl/osim-rl/blob/master/osim/env/osim.py#L527
In version 2.1, there is no argument Project for function reset(), therefore, we cannot receive dict type state_desc at the very beginning. Is that a bug needed to be fixed?

[beforethefirst]

I think that a target velocity should be given in advance so that it can know a goal and take an action pro-actively.
So, the target velocity should be from ‘prev_state_desc’ instead of ‘state_desc’ when computing the 'penalty'
Could you check the code from ‘reward_round2()’ and whether it is intentional or a bug?

penalty += (state_desc[“body_vel”][“pelvis”][0] - state_desc[“target_vel”][0])**2
penalty += (state_desc[“body_vel”][“pelvis”][2] - state_desc[“target_vel”][2])**2

[phunghx]

Why does the "target_vel" not include in observation state when using the summited server? Is the difficulty=0 with the round 2?

[beforethefirst]

@phunghx: If you set the difficulty to 0, a target velocity is a constant, so it may not need to specify.
For Round 2, you should set the difficulty to 1, and then you will have the "target_vel" in the observation dictionary.

[phunghx]

@beforethefirst Sure, from my computer, I set the difficulty to 1 and get the "target_vel" in the observation state. But when I submit to the server for grading, I did not get the "target_vel". So I guess there are some problems with the server code or they also use diificulty=0. @beforethefirst Have you tried to submit your model to the server?

[kidzik]

@phunghx right now the reward on the server is the same as it was before (difficulty = 0 in the new repo). We will run difficulty = 1 in the second round.
@beforethefirst good catch. Since it just affects ~3 steps out of 1000 and does not favor any tricks we may ignore this. However, if we get other suggestions on the reward for the second round, we may incorporate them all together.

[phunghx]

@kidzik Thank you very much

[beforethefirst]

@kidzik Currently, I am trying to train an agent to learn smooth transition, so it needs to know the target velocity when it takes an action. It might not be that critical, but could you update the code earlier? Or, could you make sure that it will be fixed when Round 2 begins?

[JohnnyRisk]

@kidzik WRT the google cloud credits, is there still time to get a positive score and be eligible for the credits? In order to qualify for them to we simply have to place before the end of round 1?

[kidzik]

@JohnnyRisk we will be able to award more credits (at least 50 x 250$). We will give details as soon as we know that everything went well in the first batch.
@beforethefirst We will discuss that with the team. We don't want to change the reward too often to avoid miscommunication, so we are hesitant to implement small changes.

[joneswong]

now, the observation is 160 dimensional. as my placeholder is <None, 158>, if I still want to submit my current model, how to modify the observation returned by client? how about obs[:158]? Thanks

[wangzhengfei0730]

@joneswong The two new dimension shall occurs at the index 156 and 159, I think you can remove them manually.

[kirk86]

@wangzhengfei0730 thanks for that, it was giving me a headache, I had the same problem as @joneswong.

[mattiasljungstrom]

@kidzik The way the reward function is setup for round 2 the model doesn't need to turn in the movement direction, it only needs to move sideways.

Is this what you intended? I had expected that the model should turn in the movement direction.

[kidzik]

@mattiasljungstrom good point! We hypothesize that moving sideways will be suboptimal due to energy constraints. Hopefully, at some point solutions to the challenge will serve as a tool for hypothesis testing (or at least screening for hypotheses).

[mattiasljungstrom]

@kidzik Interesting, thanks for the reply!

[kidzik]

Some updates regarding qualifications to the second round:

• We are planning to qualify to the second round participants with at least 1000 points in the first round (the threshold can still change),
• For testing, we will set up the REST API for the second round as it is in the first round (this we hope to have next week)
• For the actual second round, we will ask all qualified participants to submit a docker container with the solution (that way we can test it on unknown seeds and run as many times as needed)

[kretovmk]

Hi! I have a question about observation vector. Right now it is 160-dim independently of difficulty level.
If I want to prepare to Round 2, I would like to have usual observation vector (may be 162-dim) that includes target_vel. So should I now manually at every step of env call get_state_desc() and concatenate 160-dim observation vector with 2-dim target_vel vector?

Or am I missing something obvious here? For me it seems that tasks in Round 2 and Round 1 are very different, so doesn't make much sense to concentrate on Round 1 task and instead invest more time in Round 2.

[huschen]

@kidzik Thank you very much. Just to be clear, all the people are qualified for the second round, and it is the score of the second round that will qualify people (in case of capacity limitation) for the final docker submission.

[kidzik]

@yobobobo Right, we extended the deadline a little bit since then.
@huschen We will make the official statement about the requirements for the second round on the website shortly. Given that we have not too many people in the current Round 2, requirements won't be very constraining. So please go ahead and submit to the Round 2.

[joneswong]

all the homepages have not been updated and I am very confused.

before 21, oct, may I train models with round 2 env? If it is possible, no example in the homepage. just by env = Prosthetics(True, difficulty=1)?

for submission, no example also. There have been some submissions appearing in the leader board of round2. How to configure client.env_create(crowdai_token, env_id='ProstheticsEnv') to submit to round2?

Could anyone help me? Thanks!

[kidzik]

@joneswong Yes, you can train models for Round 2, the evaluation won't change.
The final submission for the second round will be done through docker containers. We are working with Mohanty on details (actually for now its mainly his work). It will look like the last year (https://www.youtube.com/watch?v=2e495B8kmUk).
The Round 2 which is up and running now is just a test one for checking the models etc.
We chose docker as the final evaluation environment so that the random seeds are not exposed.

[joneswong]

@kidzik thanks for your reply!

the evaluation won't change

I found that there are many ~9000 in the round2 leaderboard. How to submit to round2? (i.e., how to configure the crwdAI client? I cannot find any example.)

[joneswong]

@joneswong The two new dimension shall occurs at the index 156 and 159, I think you can remove them manually.

@wangzhengfei0730 hi zhengfei, could you teach me how to submit to round2? I didn't find any example in the homepage. Besides, when I set difficulty = 1, the target_vel is constantly [1.25, 0.0, 0.0]. could you also tell me how to use round2 env? I am very confused with current situation...actually, I have been tuning my agent with round1 env up to now.

[kidzik]

@joneswong you need to submit to the right server as you can see here 3ceadcc

[wangzhengfei0730]

@joneswong When set the difficuly as 1, the target_vel will change every 300 steps. I think your constantly target_vel caused by random seed.
As for submission, agree with @kidzik that you should check your port for round 2 if you want to submit to the leaderboard of Round 2. Instead, if you mean submit for docker submission, we'd better look forward to official instruction.

[joneswong]

@kidzik @wangzhengfei0730 thanks for your help! I have completed training and submission by reading the code and following your explanation. Thanks again.

@kidzik Frankly speaking, I am very disappointed at the organization of this competition. The following announcement:

Round 2 (test run): 1.10.2018 - 28.10.2018
Round 2: 29.10.2018 - 4.11.2018

appeared just around three days ago. I keep checking https://www.crowdai.org/challenges/nips-2018-ai-for-prosthetics-challenge every 2-3 days and it always

Round 2: 21.10.2018 - 28.10.2018 (tentative)

Besides, the qualification condition was not declared officially (maybe just in this thread). I was afraid that there will be more than 50 teams above 1000+ and had kept tuning my agent for round 1 until it reaches high rankings. I just turned to round2 yesterday (T_T).

We sincerely suggest to postpone the ddl of round2. Could you help us to communicate this with crowdAI? It would be more friendly to competitors like us who have not participated in the nips2017 competition. As you can see, most of the experienced competitors are more familiar with this channel (i.e., via a github issue).

Anyway, thanks for your efforts! This simulator is awesome and brings much fun to us. We will keep our RL research upon osim.

[kidzik]

Thank you @joneswong for your comment. We moved the deadlines for 1 week (both round 1 and round 2) and that’s the only change. We added the current test version of the round 2 only for convenience sorry for the miscommunication. NIPS is already very soon and we need some time to arrange the logistics (visa invitation letters etc), so it might be difficult to push it further.

[joneswong]

@kidzik I see. For now, how to qualify for docker submission? topK in round2 leaderboard or 9700+? Besides, Is there any entry to register for docker submission? It seems that crowdAI has no means to communicate with me. Thanks.

[kidzik]

We qualify top 50 solutions from Round 1, we've updated the website to reflect that.
Current Round 2 leaderboard is only a test and it is not taken into account for qualification.
@spMohanty is preparing the docker submission infrastructure and we will provide instructions as soon as it's ready (it'll be similar to the last year's system: https://www.youtube.com/watch?v=2e495B8kmUk)

[huschen]

@kidzik, what is the exact end time for round 1? 29 Oct 10:00 UTC as stated on crowdAI?

[kidzik]

Yes, the time on crowdAI is official. We were shooting for the midnight October 28 Hawaii time.

[huschen]

Thanks a lot for confirming it:-)

[joneswong]

@kidzik hi, as the ddl is approaching, what's the condition of qualifying for docker submission?

[kidzik]

We accept top 50 participants from the first round.

[joneswong]

@kidzik Thansk. It seems that I misunderstood that top50 from round1 qualify for round2 interaction (client-server) and topK from round2 qualify for docker submission. So I was afraid that my ranking was no high enough to qualify for the docker submission.

[kidzik]

I admit we were not 100% clear about that. But yes, the client-server test round 2 is meant to be just a test.

[whikwon]

Is docker submission prepared? or should i use round1's submission method for round2?

[wangzhengfei0730]

@whikwon check this repo for submission for round2: https://github.com/crowdAI/nips2018-ai-for-prosthetics-round2-starter-kit

[spiglerg]

Hmm I followed the instructions for the final round2 submissions, but I get this error in the submission link:

CrowdAI Submission Failed

" Submission failed : The challenge is not open for submissions at this time. Please check the challenge page at www.crowdai.org "

It must be something trivial, but any help would be appreciated. :)

[seanfcarroll]

@spiglerg please try again now.

[spiglerg]

Same problem. :/

[seanfcarroll]

Could you try 1 more time @spiglerg

[spiglerg]

It seems to be working now, thanks a lot! :)

[whikwon]

Anybody get trouble with test submission?

I was following the instruction and got error in ./run_local_grader.sh
ERROR:
docker: Error response from daemon: Conflict. The container name "/redis" is already is use by container

[spiglerg]

I changed the name to 'redis2' in the run_local_grader script and it worked.

[kidzik]

Please note that there is also a discussion and a 'support group' on the gitter channel: https://gitter.im/crowdAI/NIPS-Learning-To-Run-Challenge (some of quick small issues might have been solved there)