Re: [Orca-robotics-devel] time stamps

[<ama...@ma...>]

Quoting Tim Arney <ta...@en...>:

> Though I suppose latencies could be determined by doing such things as
> sending
> objects round trip, and then a common clock is used...
>

for testing purposes, query is the simplest because it uses the same clock.
to measure one way latencies you could send 1000 objects one way, log
times on both clocks, then send 1000 objects the other way, then find
average of 2000 time differences (half of them will probably be negative).

for distributed data fusion we'll need time synch anyway. how to do it
remains to be determined.

>
> Quoting Tim Arney <ta...@en...>:
>
> > Out of interest, to determine latencies are we assuming that the
> clocks used
> > to
> > generate these send and receive timestamps are synchronised
> (manually?), or
> > is
> > this one of those topics not yet explored?
> >
> > Tim
> >
> >
> > Quoting ama...@ma...:
> >
> > > lost the original email but wanted to add to the thread on time
> stamps in
> > > OrcaObject.
> > >
> > > agree with anders that having multiple ones may help in debugging.
> > >
> > > Player has 3 (they make it available on the level of each device
> proxy):
> > > 1. timestamp (data was generated by the device)
> > > 2. senttime (left the server)
> > > 3. receivedime (arrived at the client)
> > >
> > > alex m.
> > >
> > > ----------------------------------------------------------------
> > > This message was sent using IMP, the Internet Messaging Program.
> > >
> > >
> > > -------------------------------------------------------
> > > This SF.Net email sponsored by Black Hat Briefings & Training.
> > > Attend Black Hat Briefings & Training, Las Vegas July 24-29 -
> > > digital self defense, top technical experts, no vendor pitches,
> > > unmatched networking opportunities. Visit www.blackhat.com
> > > _______________________________________________
> > > Orca-robotics-devel mailing list
> > > Orc...@li...
> > > https://lists.sourceforge.net/lists/listinfo/orca-robotics-devel
> > >
> >
> >
> > ----------------------------------------------------------------
> > UTS CRICOS Provider Code:  00099F
> >
> >
> > -------------------------------------------------------
> > This SF.Net email sponsored by Black Hat Briefings & Training.
> > Attend Black Hat Briefings & Training, Las Vegas July 24-29 -
> > digital self defense, top technical experts, no vendor pitches,
> > unmatched networking opportunities. Visit www.blackhat.com
> > _______________________________________________
> > Orca-robotics-devel mailing list
> > Orc...@li...
> > https://lists.sourceforge.net/lists/listinfo/orca-robotics-devel
> >
>
>
> ----------------------------------------------------------------
> UTS CRICOS Provider Code:  00099F
>
>
> -------------------------------------------------------
> This SF.Net email sponsored by Black Hat Briefings & Training.
> Attend Black Hat Briefings & Training, Las Vegas July 24-29 -
> digital self defense, top technical experts, no vendor pitches,
> unmatched networking opportunities. Visit www.blackhat.com
> _______________________________________________
> Orca-robotics-devel mailing list
> Orc...@li...
> https://lists.sourceforge.net/lists/listinfo/orca-robotics-devel
>


--


----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.