Bug 126641 - Should be able to calculate white noise limit
Summary: Should be able to calculate white noise limit
Status: RESOLVED DUPLICATE of bug 115451
Alias: None
Product: kst
Classification: Applications
Component: general (show other bugs)
Version: 1.x
Platform: Compiled Sources Linux
: NOR wishlist
Target Milestone: ---
Assignee: Duncan Hanson
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-05-02 23:12 UTC by Andrew Walker
Modified: 2007-02-07 00:10 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Andrew Walker 2006-05-02 23:12:29 UTC
Version:           HEAD (using KDE KDE 3.5.0)
Installed from:    Compiled From Sources
OS:                Linux

An LFI requirement reads:

"It shall be possible to calculate the white noise limit from an input scientific data stream (where the input data will allow such estimation. For example it is expected that for LFI data this will be possible only for data in differenced mode)"
Comment 1 Duncan Hanson 2006-05-26 20:55:55 UTC
The LFI team would also like to calculate the knee frequency of a power spectrum.

I would like to implement this as a fitting plugin. The plugin will operate on a power spectrum, fitting for the 1/(f^a) noise and the white noise limit at high frequencies. The options will be something like..

- # of points to fit 1/f noise (or a maximum 1/f noise frequency).
- # of points to fit white noise (or a minimum white noise frequency).

It will produce scalars for the knee frequency, the white noise limit, and the fit parameter a.

It will produce a plot with the original power spectrum, a fit curve which shows the intersection of the white noise limit with the 1/f noise, and labels containing the values of the calculated scalars.

Does this sound good?
Comment 2 Andrew Walker 2006-06-01 01:50:46 UTC
Sounds good, but this should be against bug report 115451 and not this one.
Comment 3 Duncan Hanson 2007-02-07 00:10:25 UTC

*** This bug has been marked as a duplicate of 115451 ***