You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Consistently, my experience has been that the spectral analysis of unevenly-spaced records results in spectra that are heavily distorted, regardless of the spectral method (LS or WWZ), and with all currently existing freq_method options.
The result shows a singularity near the Nyquist frequency:
Passing a custom vector can help, but it requires knowing a fair bit about the jargon (OFAC, HIFAC, etc) AND the AR(1) spectra still don't look like what they are supposed to (i.e. tapering off at low frequencies). I suspect that enough tinkering can solve the problem, but that is not fair to expect of our users. There has to be a better way.
Proposal: either better defaults for the choice of freq_method, or a tutorial that explicitly addresses this.
The text was updated successfully, but these errors were encountered:
Consistently, my experience has been that the spectral analysis of unevenly-spaced records results in spectra that are heavily distorted, regardless of the spectral method (LS or WWZ), and with all currently existing
freq_method
options.Here is a minimal working example:
The result shows a singularity near the Nyquist frequency:

Passing a custom vector can help, but it requires knowing a fair bit about the jargon (OFAC, HIFAC, etc) AND the AR(1) spectra still don't look like what they are supposed to (i.e. tapering off at low frequencies). I suspect that enough tinkering can solve the problem, but that is not fair to expect of our users. There has to be a better way.
Proposal: either better defaults for the choice of
freq_method
, or a tutorial that explicitly addresses this.The text was updated successfully, but these errors were encountered: