Re: [robocup-rescue-s] Rescue Simulation outlook

From: Sarvapali Ramchurn <sdr_at_ecs.soton.ac.uk>
Date: Mon, 4 Jun 2007 21:53:52 -0000

Dear Mohammad,

You have made an interesting point and it is clear that we need to have a
clearer roadmap and more involvement from the community. The TC and
trustees have discussed long term plans and we are on the lookout for better
simulators too.

Unfortunately, without a set of dedicated programmers it is nearly
impossible to make significant progress. It is our intention to create this
team of programmers. I would urge all of you who are actively developing
code for both the simulator and the teams to make yourselves known so we
know exactly who is interested in what. Then, either at Atlanta or through
this mailing list, we should get together to agree on short and long term
developments for the simulator.

As everyone knows, RobocupRescue is open-source and everyone has been
invited to contribute in one form or another. The reason we are always so
uncertain about the simulator is that more people expect to receive rather
than give to the initiative - both are needed but currently we have an
imbalance.

I hope we'll get enough people interested.

Regards,

Gopal

> -----Original Message-----
> From: robocup-rescue-s-bounces_at_cc.gatech.edu
> [mailto:robocup-rescue-s-bounces_at_cc.gatech.edu] On Behalf Of
> Mohammad Tavakoli Ghinani
> Sent: 04 June 2007 20:33
> To: robocup-rescue-s_at_cc.gatech.edu
> Subject: [robocup-rescue-s] Rescue Simulation outlook
>
> Hi Rescuers!
>
> I think the fact is the rescue simulation will be vanished in
> the near future. Believe it or not, the current simulators
> are too far from the reality. Just as an example consider
> Misc simulator. I have selected it because it has the main
> effect on a simulation. The concepts such as HP, damage or
> buriedness do not have any justification. I don't want to
> list all of these problems because in my opinion these are
> not the causes, these are the effects. We should have some
> plans in the rescue simulation for promoting this league. The
> rescue simulation does not need the new protocols or new
> kernel, it needs some new and better simulators, some
> simulators which resembles the real world not the fantastic
> and imaginary one (Consider the 3D soccer simulation).
>
> Please consider the aim of the rescue simulation, to help the
> people in a disaster environment. Can anybody say firmly we
> can achieve this with this system? What are our priorities in
> the rescue simulation?
> I think we need a good plan for rescue simulation. But the
> current habit in the rescue simulation shows that each year
> before the Robocup competitions some very quick and abrupt
> changes are made into the system. We can observe it in this
> year even. I don't know why we should have a buggy and
> not-completed Kernel in the competitions also why the teams
> should be a test bed for the new kernel? It has so many
> revealed bugs which mean, it still has some unrevealed ones.
> I urge everybody to think about this sentence: Shouldn't we
> have a plan for developing and promoting the rescue
> simulation step by step, just like 3D Soccer simulation? And
> how we can reach to this plan?
> Suppose all of the KNOWN bugs fixed before the competitions
> what happen if a new bug discover during the competitions.
> Doesn't it question the whole purpose of rescue simulation.
> We should be clear the purpose of simulation this year.
>
> Finally remember that it is not the responsibility of TCs to
> keep alive this league we have responsibilities too.
>
> --
> Mohammad Tavakoli Ghinani
> _______________________________________________
> robocup-rescue-s mailing list
> robocup-rescue-s_at_cc.gatech.edu
> https://lists.cc.gatech.edu/mailman/listinfo/robocup-rescue-s
>

_______________________________________________
robocup-rescue-s mailing list
robocup-rescue-s_at_cc.gatech.edu
https://lists.cc.gatech.edu/mailman/listinfo/robocup-rescue-s
Received on Mon 04 Jun 2007 - 20:57:04 GMT

This archive was generated by hypermail 2.2.0 : Mon 04 Jun 2007 - 20:57:05 GMT