Re: [simspark-devel] [Sserver-three-d] Fwd: Re: Timer

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 422-6466

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Hi,<br>
<br>
On ۰۹/۱۱/۲۷  08:19, Mahdi wrote:
<blockquote   cite="mid:fca...@ma..."   type="cite">Hi Hedayat<br>
  <br>
� In my opinion, this may be good way of implementing a timer. But can
you provide more detail on your proposal? Since there are some points
which shall be calrified before implementing any timer solutions. There
are things which shall be considered in mind, like:<br>
  <br>
� * How and When agents are informed of a new cycles and data
associated with each cycle?<br>
� * How and When agents shall send their commands to the proxy?<br>
</blockquote>
Why this should be different from the current situation? I was thinking
about the same way as now. Agents can receive data from sensors in each
cycle, and they should their commands before the end of the cycle
(about 0.02 seconds from the time they receive senses). (BTW, this
model fits well with the Player integration goal; and when done agents
will communicate with sensors/actuators in the Player way).<br>
<br>
<blockquote   cite="mid:fca...@ma..."   type="cite">� * How will the proxy behave if a team responds after
specified time for a cycle?<br>
</blockquote>
The received commands will be sent to the server in the next cycle.<br>
<br>
<blockquote   cite="mid:fca...@ma..."   type="cite">��� - Will proxy announce a player dead after several
cycles<br>
��� - Or will it just send the actions of agent in the next cycle?<br>
  <br>
� I think any proposal shall answer these question besides describing
it's scheme of communication between agents and simulator.<br>
</blockquote>
What is in my mind is that with the current protocol, players should
communicate with the proxy in the same way as they communicate with the
simulator now. So there is no need to modify agents' code. When
integrated with Player, agents will communicate with the server using
that method. <br>
<br>
Good luck,<br>
Hedayat<br>
<br>
<blockquote   cite="mid:fca...@ma..."   type="cite"><br>
Best Regards<br>
Mahdi<br>
  <pre wrap="">
<fieldset class="mimeAttachmentHeader"></fieldset>
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with
Crystal Reports now.  <a class="moz-txt-link-freetext" href="http://p.sf.net/sfu/bobj-july">http://p.sf.net/sfu/bobj-july</a>
  </pre>
  <pre wrap="">
<fieldset class="mimeAttachmentHeader"></fieldset>
_______________________________________________
Simspark Generic Physical MAS Simulator
simspark-devel mailing list
<a class="moz-txt-link-abbreviated" href="mailto:sim...@li...">sim...@li...</a>
<a class="moz-txt-link-freetext" href="https://lists.sourceforge.net/lists/listinfo/simspark-devel">https://lists.sourceforge.net/lists/listinfo/simspark-devel</a>
  </pre>
</blockquote>
</body>
</html>