self.world.wait_for_tick(seconds=1.0/self.fps + 0.1) gets struck forever.

[pranavAL]

trafficstars

In the env reset ticks never increase more than zero and the loop runs forever without moving forward. Seems the wait_for _tick id not at all receiving any input back from the server I wonder why?

[weizhaoji]

hello, do you know how to run the make package command in the root directory of CARLA and add the town07 to the make package?

[pranavAL]

Sorry but I have been using only Town01 and Town02.

---

From: wei [email protected] Sent: 26 November 2019 16:55 To: bitsauce/Carla-ppo [email protected] Cc: Pranav Agarwal [email protected]; Author [email protected] Subject: Re: [bitsauce/Carla-ppo] self.world.wait_for_tick(seconds=1.0/self.fps + 0.1) gets struck forever. (#6)

hello, do you know how to run the make package command in the root directory of CARLA and add the town07 to the make package?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://github.com/bitsauce/Carla-ppo/issues/6?email_source=notifications&email_token=AFLDQEATM4XU6PCZP4PPOHTQVUBQ5A5CNFSM4IPFUBI2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEFFVUTI#issuecomment-558586445, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AFLDQECGEVI7JX5S2AEBOGDQVUBQ5ANCNFSM4IPFUBIQ.

[bitsauce]

Hi Pranav,

Someone else mentioned this to me in an email, and I think it is strange that I didn't encounter this myself.

What I suggested is that maybe the simulation is taking longer than expected, and self.world.wait_for_tick will, therefore, time out repeatedly.

Have you tried to increase the seconds parameter (lets say, add 10 instead of 0.1) or replacing the self.world.tick() in the try-except block with a pass statement?

If it is caused by a timeout due to the seconds parameter, then that is an oversight on my part.

Good luck!

[pranavAL]

Hi Marcus,

I contacted one of the developers of CARLA and they suggested me that in the latest release you need not use world.wait_for_tick the same thing is done by world.tick and if used world.wait_for_tick after world.tick it always be struck in a deadlock situation. I am using 0.9.6 and your repo is based on 0.9.5 which might be making a huge difference.

Thanking You

Pranav Agarwal

---

From: Marcus Loo Vergara [email protected] Sent: 28 November 2019 03:08 To: bitsauce/Carla-ppo [email protected] Cc: Pranav Agarwal [email protected]; Author [email protected] Subject: Re: [bitsauce/Carla-ppo] self.world.wait_for_tick(seconds=1.0/self.fps + 0.1) gets struck forever. (#6)

Hi Pranav,

Someone else mentioned this to me in an email, and I think it is strange that I didn't encounter this myself.

What I suggested is that maybe the simulation is taking longer than expected, and self.world.wait_for_tick will, therefore, time out repeatedly.

Have you tried to increase the seconds parameter (lets say, add 10 instead of 0.1) or replacing the self.world.tick() in the try-except block with a pass statement?

If it is caused by a timeout due to the seconds parameter, then that is an oversight on my part.

Good luck!

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://github.com/bitsauce/Carla-ppo/issues/6?email_source=notifications&email_token=AFLDQEGRUZ5ZUP2ZVUG2EOLQV3SHHA5CNFSM4IPFUBI2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEFK2A4I#issuecomment-559259761, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AFLDQEBAWWJ2LKHHT7U2GX3QV3SHHANCNFSM4IPFUBIQ.

[https://my-email-signature.link/signature.gif?u=172524&e=76778917&v=9679b4dd670a1651583ec390543e59e4a8ea19bc0e4277dcbe955d17ae386633]

[BestPolarBear]

@Pranav, How do you solve this problem？