From: Walter Roberson on
Luna Moon wrote:

> How do I do the following:
>
> 1. Take the intersection of the two timestamps arrays

intersect()

However, I would ask what representation you are using for the
timestamps. If the representation is a serial datenum, then you are
working with floating point values to sub-second resolution, and values
that print out the same might be different -- the usual floating point
roundoff and tolerance problems.


> 2. Figure out the index of the intersected timestamp in the date
> stream1
> 3. Figure out the index of the intersected timestamp in the date
> steam2

the two output form of histc()

> 4. Only sift out the data corresponding to those timestamps

Straight indexing


Do you have timestamps that match exactly? That would be uncommon unless
the data had been generated rather than measured.
From: Luna Moon on
On Jun 1, 11:01 am, Walter Roberson <rober...(a)hushmail.com> wrote:
> Luna Moon wrote:
> > How do I do the following:
>
> > 1. Take the intersection of the two timestamps arrays
>
> intersect()
>
> However, I would ask what representation you are using for the
> timestamps. If the representation is a serial datenum, then you are
> working with floating point values to sub-second resolution, and values
> that print out the same might be different -- the usual floating point
> roundoff and tolerance problems.
>
> > 2. Figure out the index of the intersected timestamp in the date
> > stream1
> > 3. Figure out the index of the intersected timestamp in the date
> > steam2
>
> the two output form of histc()
>
> > 4. Only sift out the data corresponding to those timestamps
>
> Straight indexing
>
> Do you have timestamps that match exactly? That would be uncommon unless
> the data had been generated rather than measured.

Yeah, the timestamps can match ... see:

Okay, I will take a look at histc(), it would be great if it can
replace my "for" loop.

Thanks a lot!

----------
K>> isequal(dDataTmp1(1, 1), dDataTmp1(2, 1))

ans =

1