ros subscriber is interrupted by ginput

1 visualización (últimos 30 días)
Jin Dai
Jin Dai el 29 de Dic. de 2016
Respondida: Sebastian Castro el 19 de Sept. de 2017
I have a ginput command in my ros subscriber callback, which causes an interruption of the subscriber. The callback is entered once, and then it stops spinning. When I comment out ginput command, the callback is called continuously.
  4 comentarios
Geoff Hayes
Geoff Hayes el 30 de Dic. de 2016
Jin - doesn't the call to ginput "block" and so you are waiting for the user (?) to choose a point on the axes? What are you expecting to happen with the call to ginput?
Jin Dai
Jin Dai el 30 de Dic. de 2016
I deleted most codes to show you only the code structure. I clicked a point and found nearest neighbors of this clicked point. After this, it exits the callback, and never enters it again.

Iniciar sesión para comentar.

Respuestas (1)

Sebastian Castro
Sebastian Castro el 19 de Sept. de 2017
This is expected, sorry to say.
Recall that the MATLAB environment is single-threaded, with the exception of optimized math functions (which you can't control as a user), or if you're using the Parallel Computing Toolbox to explicitly assign tasks to multiple cores.
So, a blocking operation like ginput means your subscriber won't be receiving any messages until you free up computational resources.
- Sebastian

Categorías

Más información sobre Services and Actions en Help Center y File Exchange.

Etiquetas

Community Treasure Hunt

Find the treasures in MATLAB Central and discover how the community can help you!

Start Hunting!

Translated by