J
jimlux
Thu, Sep 8, 2016 10:13 PM
I've got a file with counter values that are latched once per second,
with the count read from the latch every half second. So, generally,
there are two identical values, then two different identical values,
etc. But, of course, the routine that does the every half second
reading isn't perfect.. it could run fast or slow.
I want to process the count values in timelab, and I was wondering if it
knows to eliminate the duplicates, or if I write some code to strip the
dupes.
I've got a file with counter values that are latched once per second,
with the count read from the latch every half second. So, generally,
there are two identical values, then two different identical values,
etc. But, of course, the routine that does the every half second
reading isn't perfect.. it could run fast or slow.
I want to process the count values in timelab, and I was wondering if it
knows to eliminate the duplicates, or if I write some code to strip the
dupes.
BC
Bob Camp
Thu, Sep 8, 2016 11:41 PM
Hi
I think you are stuck with writing some code. I would want to make sure that in the odd
case two latched values were identical, they didn’t get tossed (3 or 4 identical in a row => 2 not 1) ….
Bob
On Sep 8, 2016, at 6:13 PM, jimlux jimlux@earthlink.net wrote:
I've got a file with counter values that are latched once per second, with the count read from the latch every half second. So, generally, there are two identical values, then two different identical values, etc. But, of course, the routine that does the every half second reading isn't perfect.. it could run fast or slow.
I want to process the count values in timelab, and I was wondering if it knows to eliminate the duplicates, or if I write some code to strip the dupes.
time-nuts mailing list -- time-nuts@febo.com
To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
and follow the instructions there.
Hi
I think you are stuck with writing some code. I would want to make sure that in the odd
case two latched values were identical, they didn’t get tossed (3 or 4 identical in a row => 2 not 1) ….
Bob
> On Sep 8, 2016, at 6:13 PM, jimlux <jimlux@earthlink.net> wrote:
>
> I've got a file with counter values that are latched once per second, with the count read from the latch every half second. So, generally, there are two identical values, then two different identical values, etc. But, of course, the routine that does the every half second reading isn't perfect.. it could run fast or slow.
>
> I want to process the count values in timelab, and I was wondering if it knows to eliminate the duplicates, or if I write some code to strip the dupes.
>
> _______________________________________________
> time-nuts mailing list -- time-nuts@febo.com
> To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
> and follow the instructions there.
JM
John Miles
Fri, Sep 9, 2016 12:10 AM
I've got a file with counter values that are latched once per second,
with the count read from the latch every half second. So, generally,
there are two identical values, then two different identical values,
etc. But, of course, the routine that does the every half second
reading isn't perfect.. it could run fast or slow.
I want to process the count values in timelab, and I was wondering if it
knows to eliminate the duplicates, or if I write some code to strip the
dupes.
That's a pretty scary problem to have. Are these frequency counts or TI readings? You wouldn't normally see two identical TI readings in a row, but if they're frequency counts, how do you know for sure you're eliminating a duplicate reading, as opposed to one that just happened to be the same as the last?
There's nothing that TimeLab can do to help with this scenario, I'm afraid. Stable32 may be able to remove duplicate TI readings, but otherwise, yes, you'd need to write some kind of script to preprocess the sample file.
-- john, KE5FX
Miles Design LLC
> I've got a file with counter values that are latched once per second,
> with the count read from the latch every half second. So, generally,
> there are two identical values, then two different identical values,
> etc. But, of course, the routine that does the every half second
> reading isn't perfect.. it could run fast or slow.
>
> I want to process the count values in timelab, and I was wondering if it
> knows to eliminate the duplicates, or if I write some code to strip the
> dupes.
That's a pretty scary problem to have. Are these frequency counts or TI readings? You wouldn't normally see two identical TI readings in a row, but if they're frequency counts, how do you know for sure you're eliminating a duplicate reading, as opposed to one that just happened to be the same as the last?
There's nothing that TimeLab can do to help with this scenario, I'm afraid. Stable32 may be able to remove duplicate TI readings, but otherwise, yes, you'd need to write some kind of script to preprocess the sample file.
-- john, KE5FX
Miles Design LLC
JM
John Miles
Fri, Sep 9, 2016 12:55 AM
That's a pretty scary problem to have. Are these frequency counts or TI
readings? You wouldn't normally see two identical TI readings in a row,
Actually, that's not even safe to assume for TI readings, depending on how your triggering works. It would make sense to do whatever it takes to fix this at the source.
-- john, KE5FX
Miles Design LLC
> That's a pretty scary problem to have. Are these frequency counts or TI
> readings? You wouldn't normally see two identical TI readings in a row,
Actually, that's not even safe to assume for TI readings, depending on how your triggering works. It would make sense to do whatever it takes to fix this at the source.
-- john, KE5FX
Miles Design LLC
J
jimlux
Fri, Sep 9, 2016 3:59 AM
On 9/8/16 4:41 PM, Bob Camp wrote:
Hi
I think you are stuck with writing some code. I would want to make sure that in the odd
case two latched values were identical, they didn’t get tossed (3 or 4 identical in a row => 2 not 1) ….
since they are latched counts from a free running counter, not
frequencies, if I do a uniq first, then compute deltas between
successive samples. (the counter is big enough to not rollover)
On 9/8/16 4:41 PM, Bob Camp wrote:
> Hi
>
> I think you are stuck with writing some code. I would want to make sure that in the odd
> case two latched values were identical, they didn’t get tossed (3 or 4 identical in a row => 2 not 1) ….
>
since they are latched counts from a free running counter, not
frequencies, if I do a uniq first, then compute deltas between
successive samples. (the counter is big enough to not rollover)
J
jimlux
Fri, Sep 9, 2016 4:01 AM
On 9/8/16 5:10 PM, John Miles wrote:
I've got a file with counter values that are latched once per second,
with the count read from the latch every half second. So, generally,
there are two identical values, then two different identical values,
etc. But, of course, the routine that does the every half second
reading isn't perfect.. it could run fast or slow.
I want to process the count values in timelab, and I was wondering if it
knows to eliminate the duplicates, or if I write some code to strip the
dupes.
That's a pretty scary problem to have. Are these frequency counts or TI readings? You wouldn't normally see two identical TI readings in a row, but if they're frequency counts, how do you know for sure you're eliminating a duplicate reading, as opposed to one that just happened to be the same as the last?
There's nothing that TimeLab can do to help with this scenario, I'm afraid. Stable32 may be able to remove duplicate TI readings, but otherwise, yes, you'd need to write some kind of script to preprocess the sample file.
latched counts from a free running counter, so difference between
successive different values is basically "frequency"...
Timelab worked perfectly after fooling around with my file parser that
generates the data files.
On 9/8/16 5:10 PM, John Miles wrote:
>> I've got a file with counter values that are latched once per second,
>> with the count read from the latch every half second. So, generally,
>> there are two identical values, then two different identical values,
>> etc. But, of course, the routine that does the every half second
>> reading isn't perfect.. it could run fast or slow.
>>
>> I want to process the count values in timelab, and I was wondering if it
>> knows to eliminate the duplicates, or if I write some code to strip the
>> dupes.
>
> That's a pretty scary problem to have. Are these frequency counts or TI readings? You wouldn't normally see two identical TI readings in a row, but if they're frequency counts, how do you know for sure you're eliminating a duplicate reading, as opposed to one that just happened to be the same as the last?
>
> There's nothing that TimeLab can do to help with this scenario, I'm afraid. Stable32 may be able to remove duplicate TI readings, but otherwise, yes, you'd need to write some kind of script to preprocess the sample file.
>
latched counts from a free running counter, so difference between
successive different values is basically "frequency"...
Timelab worked perfectly after fooling around with my file parser that
generates the data files.
