But I got this one nice run. Not enough to nail down the maxima and minima, but plenty of food for thought for all you curve-fitters out there.
My working estimate would put the cycle length for 1167 Hz at 400, which would mean your data extended up close to, but not reaching the third cycle peak at 1200, and that your big wiggle section was somewhat less than midway in sequence between that peak and a preceding minimum at 1000.
The wiggles are certainly prominent. Unless we learn to predict wiggles in detail (not something I've even thought about trying to do), it emphasizes that for performance comparisons one needs enough samples to average away the wiggle effect, and to use matching methods which don't get driven wildly off course by them.
If convenient could you post or send me the linecount for the skygrid file for 1170 Hz? I'd initially estimate it to be about 335560 lines. I already see from the web site that you see 841 skypoints, which is no surprise. (at higher frequencies all I've seen is 840, 841, or 842)
Thanks, that means the Bikeman estimate method directly applied to linecount and skypoints specific to this case and my current best algorithmic estimate agree on an expected cycle length of 399 (I was rounding off before in saying 400). So your data got really close to the peak, it seems. Selfish oaf that I am, I'd have much preferred to see both sides.
Edit: I do have task with sequence numbers from 132 down to 94 in cache if it will help, but it will take a few days to process them...
In that frequency I'm already pretty confident that the "real" cycle length is 57, but it would be good to review your host's data when results from about 108 through 120 are available, as a check.
You can find the data for frequency 434.30 and sequence numbers 151 - 101 here.
You can find the data for frequency 434.30 and sequence numbers 151 - 101 here.
Thanks, I'd forgotten to look. As with my own hosts, there is a little more noise than convenient, but squinting a bit, the second peak fits about 113, which makes the cycle length estimate from this observation 56.5.
RE: But I got this one nice
)
My working estimate would put the cycle length for 1167 Hz at 400, which would mean your data extended up close to, but not reaching the third cycle peak at 1200, and that your big wiggle section was somewhat less than midway in sequence between that peak and a preceding minimum at 1000.
The wiggles are certainly prominent. Unless we learn to predict wiggles in detail (not something I've even thought about trying to do), it emphasizes that for performance comparisons one needs enough samples to average away the wiggle effect, and to use matching methods which don't get driven wildly off course by them.
If convenient could you post or send me the linecount for the skygrid file for 1170 Hz? I'd initially estimate it to be about 335560 lines. I already see from the web site that you see 841 skypoints, which is no surprise. (at higher frequencies all I've seen is 840, 841, or 842)
RE: If convenient could you
)
Who's a clever boy? Linecount is 335,619
RE: Linecount is
)
Thanks, that means the Bikeman estimate method directly applied to linecount and skypoints specific to this case and my current best algorithmic estimate agree on an expected cycle length of 399 (I was rounding off before in saying 400). So your data got really close to the peak, it seems. Selfish oaf that I am, I'd have much preferred to see both sides.
RE: RE: Edit: I do have
)
You can find the data for frequency 434.30 and sequence numbers 151 - 101 here.
RE: You can find the data
)
Thanks, I'd forgotten to look. As with my own hosts, there is a little more noise than convenient, but squinting a bit, the second peak fits about 113, which makes the cycle length estimate from this observation 56.5.