Closed osrf-migration closed 9 years ago
osrf-migration
commented
9 years ago Original comment by jasonzliang NA (Bitbucket: jasonzliang).
Parsing the nao.rsg file is very difficult since it is using ruby scene graph, a completely different format than the sdf or urdf. Right now I am just loading the official nao sdf provided by Aldebaran whenever a client sents init
osrf-migration
commented
9 years ago Original comment by nima shafii (Bitbucket: nima_sh).
Yes, In my test the agents after sending the scene message have waited to receive back the sense message from the simulator. I uploaded a aversion in which after Sence message the simulator sends back a time message to the agent , by using that the presented issue has been solved. I did not changed the initialization policy and the agent is initialized by Init message. I think multiple agents can now be run on the simulator. I also commented some parts in GameStae.cc related to the dependency of the beaming and initializing to the play_mode.
osrf-migration
commented
9 years ago Original comment by nima shafii (Bitbucket: nima_sh).
fixed issue #3
rev f0c507b3c7172168ba9be57ecf6b7b098bb01869
osrf-migration
commented
9 years ago
Original report (archived issue) by nima shafii (Bitbucket: nima_sh).
The original report had attachments: AgentSimulatorComminucation
The first message that RoboCup agent sends is Scene message, and with using that message Simspark simulator will initialize a robot model. Usually only after the agent receives the sense message from simulator, the agent will send its second message that is the Init message contains the robot number and team name. A sample of agent simulator communication sequence can be found in attached file. Currently we are initializing the agent in simulator only by using the Init message, thus we are not following the sequence of agents simulator messages and the agent is not initialized in the simulator. so the initialization approach should be changed. In branch Nima_Integration, this issue will be solved.