Talk:Window function

Incorrectness

Let's start with the very first sentence: The Fourier transform of the function: $\cos(\omega t)\,$ is zero, except at frequency $\pm \omega \,$.

For flip's sake, this is a completely inappropriate function to mention because $\cos(\omega t)\,$ is NOT lebesgue integrable on the real line. If you actually go and read the page on fourier analysis, you will discover that fourier transforms are only defined on L1 functions. I would delete the paragraph, but as everyone would probably then misunderstand my point completely, I thought I'd just write it here. Can't you do any better? —Preceding unsigned comment added by 212.44.43.13 (talk) 15:28, 7 August 2008 (UTC)

Despite that technicality, it is extremely common for textbooks to refer to the Fourier transform of sinusoids. That's really all the justification required for Wikipedia to do the same. And if you read on past Fourier analysis, to Fourier_series#Fourier series on a general interval [ab], you will discover the reason.

--Bob K (talk) 20:33, 7 August 2008 (UTC)

Well, it is true that $\exp(2i\pi ft)\,$ cannot be integrated over t into a classic function; however, people had been using this sum for decades, especially in quantum mechanics, sometimes with confusing demonstrations. However, "Distribution theory" from French mathematician Laurent Schwartz clarified this point in the 50's: it postulates an extension of the set of usual functions to include mathematical strange things such as the "Dirac distribution", that could be considered zero everywhere but at f=0, and the measure of which (i.e. the area) is 1. This integration precisely produces this distribution.

Almipa (talk) 19:42, 16 April 2010 (UTC)

Square integrable does not imply "that the function goes sufficiently rapidly toward zero." One can construct L2 functions (i.e. square integrable) that grow very large and are even continuous. I would suggest to remove that part of the sentence and stop after square integrable. — Preceding unsigned comment added by 141.52.58.13 (talk) 12:15, 18 December 2013 (UTC)

Doesn't a window need to be absolutely integrable? Something like a sinc function or a $1/(1+abs(t))$ that goes too slowly to zero, that is square integrable but not absolute integrable, does not make a usable window, does it?

FWIW, I don't know the answer, and don't care. If there is a WP:TOO_ACADEMIC card, this is a good place to play it, because in my 4 decades of using window functions, it's not something I ever worried about. And I have no scars to show for it. The "more general definition" is not sufficiently justified. It should be deleted, until its practical value can be convincingly demonstrated.

--Bob K (talk) 04:41, 21 December 2013 (UTC)

True, we usually use windows of finite support in DSP, but windows such as Gaussian and exponential are sometimes encountered, too. I wish I could see what the cited book says. Dicklyon (talk) 05:58, 21 December 2013 (UTC)

Comparison Table

this article is in dire need of a big comparison table that summarizes the key metrics of the various window functions. the comparison table should be similar to table 1 in the seminal article by harris "on the use of windows", page 5. see article, which is linked in the references.

Scalloping loss

The paragraph about scalloping loss seems to refer to a figure that isn't there. Sdrpyh 06:23, 14 February 2007 (UTC)

It's just as Bob K wrote it on 18 December 2005, this diff. The figure above is still the same "zoom view" figure in the previous subsection. I find it a bit confusing, too. Dicklyon 06:30, 14 February 2007 (UTC)

An excellent description of scalloping loss is given at [1]. There does not appear to be a clear definition and/or example of scalloping to date in Wikipedia that I could find, but the term is bandied about as if it were common knowledge. At some point, we should make a page (or at least a section) that describes the phenomenon clearly. Jtonti (talk) 11:54, 1 April 2018 (UTC)

All about frequency analysis?

In this article, it sounds like windowing's only use is in frequency analysis, as for example I am using it for making a windowed-sync FIR filter, and in this case the use of a window function (i chose the Blackman one) is to avoid riple in the frequency response of the FIR filter kernel. --SuperBleda 15:27, 19 August 2005 (UTC)

I still don't know, what is a window function? --anon

Whoever redid this, it's much much better now. 81.105.21.22 13:59, 7 April 2006 (UTC)

I can't claim all the credit, but I did a lot of it. So on behalf of the whole team... thanks! --Bob K 07:18, 10 April 2006 (UTC)

DFT-even vs. Matlab

I'm a bit puzzled as to why the window functions given were not put in "DFT-even" form ( /N rather than /(N-1)). The reason to use "DFT-even" windows is covered in one of the articles's references. See pg 52 of the following:

Frederic J. Harris, On the use of Windows for Harmonic Analysis with the Discrete Fourier Transform, Proceedings of the IEEE, Vol.66, No.1, January 1978, pp 51-83.

--SAMerritt 10 May 2006

Harris' rationale for truncating a symmetrical window (which increases its equivalent noise bandwidth and other metrics of spectral leakage) is that it enables real-valued DFT coefficients. Matlab's interpretation/explanation is "enables a windowed signal to have the perfect periodic extension implicit in the discrete Fourier transform". I don't think those really answer the question, because real-valued DFT coefficients (if that is important for some esoteric reason) can also be had with an odd-length (N+1) symmetric window and an even-length (N) DFT (or FFT) by using periodic summation (adding the N+1^th element of a data sequence to the 1^st element) instead of truncation. And the performance (in terms of spectral leakage metrics such as main lobe, sidelobes, and noise bandwidth) of an N+1 length symmetric window is better than an N-length asymmetric window. (see File:Comparison_of_symmetric_and_periodic_triangular_window_functions.svg) Furthermore, the sum of the first and last terms of the symmetrically-windowed data sequence is w(0)•x(0) + w(N-1)•x(N-1) = w(0)•[x(0) + x(N-1)]. Therefore, w(N-1) is unnecessary, and in fact causes an extra multiplication. So after adding x(0) and x(N-1), we only use the DFT-even portion of the symmetric sequence. (The other coefficients, except n=N/2, also occur in symmetrical pairs, but the periodic summation does not force us to combine those terms prior to the DFT.)

--Bob K (talk) 02:01, 18 March 2019 (UTC)

I agree some work needs to be done here. Looking at the Matlab documentation, Matlab can return either a "periodic" window or a "symmetric" window. Symmetric is the default; they say it is more appropriate for filter construction while the periodic form is more appropriate for spectral analysis. (There seems to be agreement on this; see "periodicity of window functions" below.) Numerical Recipes (3rd edition) doesn't discuss the distinction but (in chapter 13 on spectral applications) uses the periodic form where n goes from 0 to N-1 and the window has a zeroes at 0 and N. I'm not sure if Matlab's "periodic" or "symmetric" terminology is broadly accepted; ideally this page should describe them both and provide some guidance on how to choose between them. (I may try to take a stab at this later.)

--Rob Calhoun 18 Jul 2011 — Preceding unsigned comment added by Rcalhoun (talk • contribs) 20:25, 18 July 2011 (UTC)

There is now a good discussion of this at Talk:Window_function#Unnecessary_complexity_with_the_definition_of_N. The DFT-even convention simplifies many of the formulas by replacing N-1 with just N, without changing the definition of N as the length of the sequence. And N would not be restricted to even values. Odd values would create 2-point maxima, just as even values now do in our current convention.

--Bob K (talk) 23:32, 17 March 2019 (UTC)

The Comparison Graph

The comparison graph is great. The logarithmic frequency axis (in units of "DFT bins") is an excellent idea. It would also be helpful to label the axes. --Bob K 00:17, 10 September 2006 (UTC)

SUGGESTION: Please add a similar time-domain comparison of step-response, and maybe a table of statistics from that graph such as %-overshoot, group-delay, settling-time (to 1%, 0.5%, 0.1%). ALSO maybe add a step-response to each of the graphs in the "Window examples" section above. -- citizenDAK —The preceding unsigned comment was added by 70.91.225.169 (talk • contribs).

What does that mean? What is the step response of a window function? Dicklyon 22:29, 3 July 2007 (UTC)

Step response is (in summary) a way to see + compare important characteristics like the TRANSITION-DELAY or SETTLING-TIME and the RINGING or OVERSHOOT of a filter (a Window function *IS* a kind of FIR digital filter, commonly called a "moving average"). (Try a search-engine for "step response DSP window" for more info... One good example I just found is slide 10 of this Intro to Digital Filters PDF-file.) -- citizenDAK

Yes, I know about filters and step responses; but in what sense is a window usefully viewed as a filter? It's not convolved with an input, so it's not being used as a moving-average filter. If it were, its step response would have no overshoot, since windows are non-negative. They would all look very similar, sort of like the windows themselves. Maybe you can compute one of what you have in mind and show us. Dicklyon 19:23, 9 July 2007 (UTC)

An answer (besides moving average) that comes to my mind is FIR design by the Window method. An underlying IIR (sinc function) determines the nominal filter bandwidth, and its tapering function (window) determines the frequency-domain transition regions and the corresponding time-domain transients. This method is seen in applications requiring closed-form conversion of filter specs into FIR coefficients, on-the-fly design, as opposed to something like Remez iterations. However, this article is not the appropriate place for so much focus on filter design.

--Bob K (talk) 20:08, 3 November 2018 (UTC)

confusing wording

Can someone change this? In the third sentence of the following excerpt, it is unclear what "they" refers to (does it refer to window functions with low dynamic range, or window functions with poor resolution?): "This characteristic is sometimes described as low dynamic range. At the other extreme of dynamic range are the windows with the poorest resolution. And they are also poorest in terms of sensitivity." Lavaka 06:08, 8 January 2007 (UTC)

Yes, very. I believe I have fixed it correctly, but I invite others to check me. Dicklyon 06:30, 8 January 2007 (UTC)

Bartlett/Triangle Window

Can someone check the equation for the triangle window? I've normally seen it as 1-abs((n-.5N)/.5N), or equivalently 1-abs((2n-N)/N). This page shows 1-abs((2n-N+1)/N)

Kelauder 06:05, 2 April 2007 (UTC)Kevin

It's easy enough to verify by inspection that at the defined end indices of 0 and N-1 the values of the Barlett are 0 and of the triangle are 1/N; that is, the formulas work as expected. Your formula would work if the range was defined from 0 to N for Bartlett, or 1 to N-1 for triangle. But it's not. Dicklyon 06:35, 2 April 2007 (UTC)

I have made a correction to the equation for Triangle Window with non-zero endpoints. The new equation obeys the property that the next point outside the window on each side, following the same slope, would be zero, i.e., w(-1) = w(N) = 0. Note that Matlab's (7.9.1.705) triang function for Odd N is equivalent to the equation I have placed on Wikipidia. For even N, it is my belief that Matlab's implementation is "incorrect", because the equation in their documentation does not exhibit the property w(-1) = w(N) = 0, and because it seems unnecessarily complicated to use a different equation for N even than for N odd. Perhaps The MathWorks has some other rationale for preferring their definition -- I will take that up with them separately.--Rtbehrens (talk) 20:15, 6 March 2012 (UTC)

Gauss window

In the provided plots, I was suprised to see that the Gauss window in the Fourier doimain does seem to have sidelobes. This should not be the case though as the FT of a Gauss function is again Gauss. —The preceding unsigned comment was added by 129.27.140.171 (talk) 08:33, 17 April 2007 (UTC).

Truncated 2A01:119F:21D:7900:A1D6:ECD0:10D0:482B (talk)

Read (or re-read) the part about spectral leakage. A Gauss function has infinite duration. A Gauss window does not.

--Bob K 11:24, 17 April 2007 (UTC)

Tighter format?

What do you think of my "tighter format" edit? I can do the same on the next section, but it might run into problems for narrow browser windows with its longer equations. Any other good suggestions for how to format this without wasting tons of white space? I also like the tight way because it's so much easier to look at several equations at once to compare them. Dicklyon 20:03, 3 June 2007 (UTC)

The tighter format is also what I chose (e.g. http://wiki.riteme.site/w/index.php?title=Window_function&direction=prev&oldid=31779771).
--Bob K 21:30, 3 June 2007 (UTC)

OK, I'll do it. I see the "left" format was contributed by an anon. Dicklyon 23:20, 3 June 2007 (UTC)

PNG and SVG plots

mmm... how can you say that "The .png files have better resolution?, no bit-map picture can have higher resolution than a vector image! I have noticed that unfortunately I have lost the grid in the SVG generation and I couldn't fix it, but the grid is not necessary in this context. Alessio Damato 21:07, 26 October 2007 (UTC)

Request for revision

I think that this article is lacking in having a specification for how a window is applied (which would hopefully include an explicit equation). Also a non-technical intro about what windowing is used for, and why. Melcombe (talk) 08:53, 4 April 2008 (UTC)

Two+ years later, I must plead for the same. I read the upper sections of the article over and over, but still have no idea WHY windows are used. The article just says they used in particular applications, and goes on to describe the (apparently deleterious?) effects that applying a window has. It never explains the impetus for using them in the first place. Meanwhile I will repair some of the flaccid verbiage in the parts I do understand. Strebe (talk) 19:25, 10 August 2010 (UTC)

It does seem that it could be more written such that it is more obvious. The usual answer is that many signals are valid for infinite time, but computers can only process signals with a finite length. Note the integral in the Fourier transform is from t=-infinity to t=+infinity. The obvious solution is to cut off the ends, which is mathematically the rectangular window. I thought of adding this to the first paragraph, but I think I will let someone else try that. Gah4 (talk) 01:38, 17 February 2016 (UTC)

The second reason this exists is that the results of using a transform with periodic basis functions on non-periodic data is, what is called in the article spectral leakage. If the data doesn't naturally go to zero at the ends, the DFT, with periodic basis functions, gives the result as if the first point followed the last point, resulting in a discontinuity. That is, that the input is processed as periodic in its length (or, if zero padded, to some longer length). Windowing, other than rectangle, smooths off the discontinuity, giving more appropriate spectral results. Gah4 (talk) 01:38, 17 February 2016 (UTC)

I'm simplifing this explanation. The conclusion is unchanged. But my apologies to any followups specifically directed at the original explanation.

I think a better definition of leakage, in the context of the Fourier analysis, is an operation (such as truncation) that causes frequency components to appear that aren't in the original function. The result can still be periodic, such as squaring a sinusoid. For discrete-time functions, truncation of a sinusoid always creates leakage in the discrete-time Fourier transform (DTFT), which is a continuous function of frequency in general. And the DTFT definition does not change between comparisons. Only the input function changes. But the definition of the DFT has a parameter, N, the number samples, because it is just a sparse sampling of one cycle of the DTFT. In order to define leakage in a useful way, that parameter has to be held constant. So if you perform a DFT on 1000 samples of a sinusoid, and if there are exactly 10 samples per cycle, your "spectrum" has just one non-zero component, at bin 100. If you then rectangularly window the sinusoid to 500 samples, and perform the same DFT (now including 500 zeros), you see leakage in about half the bins, I think. Only if you change the DFT size to 500 (which is a more sparse sampling of the DTFT), do you miss all the leakage. Concluding that a rectangular window has no leakage for certain sinusoids is nonsense. Truncating any sinusoid with any kind of window causes leakage. So windowing is a necessary evil to extract a manageable subset of a long sequence (as you said), and the reason for non-rectangular windows is to obtain a more favorable tradeoff between side-lobe leakage vs main-lobe leakage.

--Bob K (talk) 22:07, 18 February 2016 (UTC)

The exact periodic case isn't so pathological if you can phase-lock the sample clock to the source. As an example, when measuring power-line signals, it should be easy to lock to a multiple of the power line frequency. Gah4 (talk) 20:49, 18 February 2016 (UTC)

My interpretation of this seemingly irrelevant remark is that my help here is not welcome. Good-bye.

--Bob K (talk) 22:07, 18 February 2016 (UTC)

Questions

Is there a terminology describing calculating two windows and using the best features of each?

I will be writing a "dual window FFT/IFFT" (basicly two seperate functions ran in sequence on the same data) that will calculate and use both "Low-resolution (high-dynamic-range) windows" and "High-resolution windows" (to use the terminology of this page) in order to provide (the FFT portion) a spectrum with high dynamic range and high resolution, and (the IFFT portion) a reproduction of the input wave with a low loss of residuals.

I've tried searching for any programs or papers describing (what would seem to be) this simple idea but there seems to be no information on this subject.

In the event that there is such a thing a description of it is missing from this page. —Preceding unsigned comment added by 24.85.104.61 (talk) 23:27, 2 June 2008 (UTC)

I'm not sure I would put it here anyway. For instance the Welch method uses window functions, but it is described in a separate article.

Also not sure why you need to "reproduce the input wave". Don't you already have it? And what does that have to do with this article?

--Bob K (talk) 02:45, 3 June 2008 (UTC)

Definitions

It is good to see that start has been made with provoding some proper definitions. But .... (and this may differ between fields of application) ... isn't there a need to start with a definition of the time-period over which a time-signal is defined, possibly called a data-window, and then define the window function as producing a new time-signal, possibly over a different data-window. Mathematically it might be convenient to define time-signals as zero outside a data-window but the exact definition of a data-window can radically affect the outcome of data-processing (eg application of discrete-time FFTs.). Melcombe (talk) 09:11, 11 August 2008 (UTC)

A specific example of the "problem" might help.

--Bob K (talk) 12:37, 11 August 2008 (UTC)

I don't really understand what you're trying to say. But I always think of signals (including windows) as functions defined on the entire real line. --Drizzd (talk) 14:21, 12 August 2008 (UTC)

Noise bandwidth

Besides that fact that the formula

$B_{n}={\frac {1}{g}}\int _{0}^{\infty }|H(f)|^{2}df$ where $g=|H(f)|_{max}^{2}$

applies to filtering applications (which is not the subject of the article), it also assumes real-valued, continuous-time I/O, which is not the main point of the article either. It is well-intentioned, but not sufficient. Let's either remove it or caveat its relevance and add the other necessary cases (especially complex-valued, discrete-time data). I.e., if it's worth doing, it's worth doing right.

But this particular subject, with the associated math, could distract from the main points that follow. It's a relatively unimportant (but interesting) detail. If done right, I think it deserves it's own article with a link from this one.

--Bob K (talk) 12:27, 15 September 2008 (UTC)

The Example Images for all the filters should be larger.

You can't read them at the current state without zooming-in (but this requires 2 clicks: one on the image, then one on "Full resolution"). I think this is important, as on aspect of the filtering is how much they filter the signal (-50dB, -100dB etc), so two images might look almost the same, but if you look at the scale, you will see that one filter actually suppresses side-lobes by -50dB the other by -80dB. I tried to increase the images to 400px (just in the sandbox), but then the thumb-text underneath goes away... perhaps someone with better knowledge on how formatting images could do the reformatting? Kusmi (talk) 08:07, 9 December 2008 (UTC)

It actually takes me 3 clicks, because my screen is 1024 wide, and the figures are about 1040-1050. The Wikipedia instructions say to always upload the full resolution. And that, of course, is because the article can use "thumbnails" to compress it. Anyhow, this is how to do what you suggest (see below). It's not the standard Wikipedia way of handling large images.

The general instructions for images are here:

Wikipedia:Extended_image_syntax#New_syntax_for_images

--Bob K (talk) 13:39, 9 December 2008 (UTC)

[[Image:Window_function_(blackman).png|frame|none|Blackman window; α = 0.16; B=1.73]]

Added pre tags around the image, it was so large after updating it that it was distracting. Olli Niemitalo (talk) 19:47, 9 February 2013 (UTC)

periodicity of window functions

IMHO, in order to minimise artifacts when calculating the DTFT of a finite time series of length N (0<=n<=N-1), it is recommended that 1.) both the signal and the window function are periodic with N,  2.) the window function as well as its first and second derivatives take a value of zero at n=0. At least, that's what I was taught 20 years ago by H.-P. Harjes, a German Geophysicist, whose lessons roughly followed the book of M. Bath, Spectral Analysis in Geophysics, Elsevier, Amsterdam 1974.
Georg Morscher schorsch (talk) 21:06, 5 February 2009 (UTC)

If a discrete-time signal is "periodic with N", its DTFT is a discrete-frequency function, with a maximum of N unique amplitudes which are the exact outputs of an N-point DFT. Any non-rectangular window will produce different (inexact) results. This is true even for an N-periodic sawtooth function.

Or perhaps what you mean by an N-periodic signal is essentially a sinusoid, or sum of several sinusoids, whose frequencies correspond to DFT basis functions,  $e^{i2\pi {\tfrac {k}{N}}n},$ where k is an integer. I've never been lucky enough to have such well-behaved, predictable "signals", but if I did, I would use only the rectangular window, which has no zero at n=0.

--Bob K (talk) 17:14, 6 November 2018 (UTC)

For a different explanation, same conclusion, you can also read https://community.plm.automation.siemens.com/t5/Testing-Knowledge-Base/Window-Types-Hanning-Flattop-Uniform-Tukey-and-Exponential/ta-p/445063 . But about "non-periodic signals" they make this statement:

Here, when the captured signal is repeated, the original sine wave signal is not re-created. In fact, several broadband transient events (circled in red in Figure 2) are introduced. These transients create a broadband response, or leakage, as shown in Figure 3.

Apparently they aren't talking about sawtooth functions. They're talking about sinusoids, and those whose frequencies don't correspond to a DFT basis function are "non-periodic". But isn't "non-periodic sinusoid" a confusing misnomer? Secondly, it's a cop-out to blame the discontinuities for "leakage". To understand what's really going on, we should look at windowing in continuous time: rectangularly chopping an integer number of cycles out of a sinusoid turns its Fourier transform from a Dirac delta into a sinc function, and that is "leakage". But if we only sample that FT at intervals of 1/T, and T is the rectangular window width, we can't see the leakage, because the samples fall at its zero-crossings. (That's why the FTs in all of our figures in this article are sampled much more densely.) When we tweak the frequency of the "periodic" sinusoid, yes, the so-called "broadband transient event" appears at the edge of the rectangular window. But all that happens in the FT domain is that the sinc function slides a little left or right to the new frequency. There is no "broadband" change in its shape. The width of the sinc function is determined by the window width, not the sinusoid frequency. But now when we under-sample the FT at intervals of only 1/T, the samples no longer fall at the zero-crossings, and voilà, the leakage caused by windowing "magically" appears!

--Bob K (talk) 17:14, 6 November 2018 (UTC)

The non-rectangular windows do suppress any transitions left by a rectangular window, but what they do in the frequency domain is much more insightful, because they do it even when there are no transitions to suppress (the so-called "periodic" signal). In the frequency domain, they convolve the sinc function, and all of its ripples (sidelobes), with the FT of the window function, which is another window-like smooth function. That broadens the sinc main lobe and does a "moving average" over the sidelobes, which reduces them since they oscillate around zero. That reduces broadband leakage at the expense of narrowband leakage (wider main lobe). The total leakage, as measured by the ENBW, actually increases.

Thus, there are different perspectives from which to understand windowing.

--Bob K (talk) 17:14, 6 November 2018 (UTC)

In the present version of the text, the window functions introduce a double zero for n=N-1 and n=N.
I found a significantly higher "background noise level" when comparing the results of a DTFT calculated with a double-zero window function to that obtained using a single-zero WF. I thus would recommend to change the denominator N-1 in the corresponding formulae to N instead of providing the somewhat non-binding comment on that point. Regards Georg Morscher schorsch (talk) 21:06, 5 February 2009 (UTC)

I think what you mean by "background noise level" is a value proportional to the equivalent noise bandwidth. In units of DFT "bins", the ENBW is given by:

$B=N\cdot \left(\sum _{n=0}^{N-1}w(n)^{2}\right)/\left(\sum _{n=0}^{N-1}w(n)\right)^{2}.$

For example, a standard rectangular window (to keep the math manageable) has B=1. Inserting a zero-valued end-point increases B to N/(N-1). And two zero-valued end-points increases B to N/(N-2). The decibel increase from 1 zero to 2 zeros is 10•log₁₀((N-1)/(N-2)). For N=8, that's 0.67 dB, but for N=128, it's only 0.035 dB. So it appears I'm not understanding what you mean by "background noise level". Regardless of what you mean, to eliminate one of the zeros, we ask that you simply generate your window with N+1, and delete the end point. For an even lower ENBW, generate your window with N+2, and delete both end points. The reason we prefer the symmetric window formulation is explained here:  It's_complicated.

--Bob K (talk) 17:32, 1 November 2018 (UTC)

Practical Recommendation When Using Hann Window

When using Hann windows for signal processing, better to use the form 0.5*[1-cos(2pi*[n+1]/(N+1))]

This squeezes an extra two points of size into the window, for free(ish). The DFT-even form also adds two non-zero points, but only one effective point of added width (while preserving many other esoteric properties, like an average window amplitude independent of N). —Preceding unsigned comment added by Kristo Miettinen (talk • contribs) 19:58, 27 April 2009 (UTC)

I agree that in practice that's the best thing to do. But the article also has a goal of introducing windows to newbies with minmal distracting details. In that spirit, there is a benefit to limiting the differences between formulas to just the ones that are unavoidable. For those who are going to go on and generate a window, we have the caveat about zero-valued coefficients and widening the window to prevent it. IMO, that's a good compromise.

--Bob K (talk) 21:58, 27 April 2009 (UTC)

Fixed a couple formulas

I noticed that the formula for the Hamming window was not the standard one, but seemed instead to be a modification that is sometimes suggested under another name. I put the Hamming window formula into a standard form. I also decompiled the factor of $\pi$ out of the parameter for the Kaiser window formula, so this way the parameter will be more in line with the literature where a reasonable value is around 3. 08:36, 28 April 2009 (UTC) —Preceding unsigned comment added by Safulop (talk • contribs)

All the formulas given were for a range from 0 to N-1, except the parzen formula which is from -N/2 to (N-1)/2. Is it wished like this? 178.3.83.62 (talk) 12:28, 21 October 2018 (UTC)

Good catch. The formula in the article is straight from Harris, which (as you say) is for the function our article calls W₀(n). So here is an easy fix:

$w_{0}(n)=\left\{{\begin{array}{ll}1-6\left({\frac {n}{N/2}}\right)^{2}\left(1-{\frac {|n|}{N/2}}\right),&0\leqslant |n|\leqslant {\frac {N}{4}}\\2\left(1-{\frac {|n|}{N/2}}\right)^{3},&{\frac {N}{4}}<|n|\leqslant {\frac {N}{2}}\\\end{array}}\right.$

$w[n]=\ w_{0}\left(n-{\tfrac {N-1}{2}}\right),\ 0\leq n\leq N-1.$

That approach is also used at Dolph–Chebyshev window.

--Bob K (talk) 14:36, 22 October 2018 (UTC)

Is the argument of the gauss function for the approximated confined gauss correct? the denominator of the argument is only sigma without a relation to the sequence length N. I would propose to add a (N-1)/2 to the denominator. 178.3.83.62 (talk) 12:28, 21 October 2018 (UTC)

But notice that σ_t is defined (in the example) as 0.1•N = N/10, which is related to the sequence length. However, I agree that the N-dependence belongs in the formula, not in the value of σ_t. Your suggestion is to change the formula to:

$G(x)=e^{-\left({\cfrac {x-{\frac {N-1}{2}}}{2(N-1)/2\sigma _{t}}}\right)^{2}}$

I suggest we use just N (instead of N-1) in the denominator, because that is the actual window width. And I suggest we do not introduce the "/2" denominator, because the whole idea is for the two figures (Approximate confined Gaussian window and Confined Gaussian window) to look alike.

--Bob K (talk) 18:59, 24 October 2018 (UTC)

Specific goals

It seems that many of these windows were created to solve a specific problem. Can you describe this problem and the derivation in each section? —Preceding unsigned comment added by 71.167.61.179 (talk) 07:00, 30 November 2009 (UTC)

Merge separate Hann function page

Of all the types of windowing functions only two have their own page, the Hann function and the Kaiser window. Of the two the Hann function does not provide any further useful information than is available in this page, and what is there is mostly incorrect or unclear. In its current state I think it's not that useful to have the Hann function as a separate page, until it is expanded upon perhaps it should be removed? Nonnumquam (talk) 07:39, 30 November 2009 (UTC)

Closes as unsupported. Dicklyon (talk) 20:56, 20 February 2011 (UTC)

diagram

show a graph of a sine wave before and after windowing, to make the function clear —Preceding unsigned comment added by 71.167.63.79 (talk) 20:56, 12 December 2009 (UTC)

the Applications section

There are numerous problems with this section. It is redundant with information elsewhere (and previously) in the article. It is not in a logical position within the article. And some of it is just nonsense, for instance "the ideal frequency response of a window is a Dirac delta function, as that results in the frequency response of the FIR filter being identical to that of the IIR filter". Deletion is necessary. Rewrite is optional. I'm happy to do the deletion, but not the rewrite.

--Bob K (talk) 22:37, 14 December 2009 (UTC)

I agree, so I took it out, and reorganized the following sections as subsections. There may be some recoverable bits in there if anyone wants to work on that. Dicklyon (talk) 23:15, 14 December 2009 (UTC)

flat top function

The "flat top" function that is mentioned here requires references.
Moreover it is not normalized.
Therefore, its present use to design a FIR will require a multiplication by a constant.
Because of its form, the way to normalize it is to choose a_k coefficients so that their sum is one.
Regards,
Almipa (talk) 11:27, 12 April 2010 (UTC)

It is already normalized (in the now referenced form) so that the integral over it is 1 (from the constant term, the cosine terms do not contribute).

Olli Niemitalo (talk) 08:25, 10 February 2013 (UTC)

By coefficients he probably meant cosine terms, not window values. Sum of cosine terms is equivalent to the peak.

2A01:119F:21D:7900:54E1:9029:DEED:43A1 (talk) 05:55, 8 August 2018 (UTC)

Actually, Olli, the integral is N•a₀ = N (not 1).

--Bob K (talk) 23:27, 4 November 2018 (UTC)

Or should it be normalized to peak value = 1 instead? I found a Max Planck Institute technocal report reference (Heinzel G, R?udiger A and Schilling R, 2002) for the flat top window and changed a₄ to 0.028 accordingly. This only improved the frequency spectrum, so the previous value was probably in error.

Olli Niemitalo (talk) 08:25, 10 February 2013 (UTC)

Yes, the peak should be 1, to facilitate comparisons with all the others in the article. As the other two contributors say, the coefficients should be divided by $\sum _{k=0}^{4}a_{k},$ because that is the peak amplitude of the window for odd values of N. It occurs at n=(N-1)/2, where the #1 and #3 cos(•) functions are -1. In practice, another common scaling is the divisor $\sum _{n=0}^{N-1}w(n),$ because that is the DFT gain (amplification) experienced by a sinusoidal component with no scalloping loss. So that scaling results in unity gain, which might be important for amplitude measurements or in fixed-point arithmetic implementations.

--Bob K (talk) 23:27, 4 November 2018 (UTC)

The source also gives a value for B for flat top, and other windows, I'll check if more of them can be harvested from it. The current practice to calculate B ourselves is somewhat suspect.

Olli Niemitalo (talk) 08:25, 10 February 2013 (UTC)

The formula for ENBW (which we abbreviate as B) is Eq (11), p 54, of On the use of Windows for Harmonic Analysis with the Discrete Fourier Transform, except, as can be seen from the values in Table I, it is missing a factor of N. The correct version appears on page 14, Eq (21), at Spectrum and spectral density estimation.

Bob K (talk) 19:30, 5 November 2018 (UTC)

Tukey function definition

I found it vexing that the Tukey function seemed to be the only function defined from -N/2 to N/2. Even the graph to the right of the function definition appears to plot it from 0 to N. I thought it would be more clear define it from 0 to N as it is in the other window functions and in the Matlab reference. Also, I realize now that there was nothing wrong with the original definition, just that it was defined on a different interval. Cheers. Ebmi (talk) 05:36, 28 September 2010 (UTC)

This seems taken care of. Olli Niemitalo (talk) 20:46, 10 February 2013 (UTC)

Frequency response graphs should have the same scale

Frequency response graphs (in orange) do not have the same scale: some are from -60dB to 0 ; others are from -100dB to 0 and even others are from -120dB to 0. It is thus very difficult to compare them quickly. I suggest all the graphs to be redrawn using the same scale. —Preceding unsigned comment added by 213.244.14.206 (talk) 14:17, 18 November 2010 (UTC)

The comparisons are done at Comparison of windows

--Bob K (talk) 02:24, 19 November 2010 (UTC)

The problem is that the scale is not visible on small graphs, and it leads to the false impression that some windows are almost identical whereas it is not the case at all. I suggest: either to make the scale visible on small pictures ; either make them all with the same scale. By the way, an harmonization is needed, because some frequency response graphs are in svg format and others are in png. --213.244.14.206 (talk) 12:51, 14 December 2010 (UTC)

I agree about the harmonization. A couple of editors started replacing png links with svg links, but they only did about four and lost interest. And the svg versions do not preserve the grid lines. The png links should still work, so one of us should restore them.

Regarding the scale variations, my opinion is that it's good the way it is, since there is also a fixed-scale comparison graph. The "small pictures" are only intended to serve as icons. Drawing conclusions from icons is certainly risky, but that's to be expected.

--Bob K (talk) 20:46, 15 December 2010 (UTC)

I made new images that address the raised issues. The amplitude scale is now different only for the flat top window which is really funky anyhow compared to others. Olli Niemitalo (talk) 19:24, 9 February 2013 (UTC)

Added OLA-Hann window in Other Windows

This article seems extremely well written, so the addition I've made likely needs to be improved. Advice welcome. Full disclosure: I am the inventor of the OLA-Hann window technique, but only work in this area as a hobby.WaywardGeek (talk) 12:41, 24 December 2010 (UTC)

If I understand correctly, you add a pair of 50% overlapped Hann windows, so you get a cosine-tapered window, flat in the middle, 50% longer than the Hann windows that it's based on (your article says 2X longer, which I don't get). Anyway, though it may be a novel and useful window, it's really not appropriate to report it in wikipedia until after you get it published in what we can cite as a WP:RS. Dicklyon (talk) 18:11, 24 December 2010 (UTC)

Close, but not quite right. The first frame is tapered on the left, the second frame is tapered on the right, and when overlapped and added, the resulting frame is not tapered at all, yet has very little spectral noise. A sine wave at a frequency equal to one of the FFT bins is not in any way modified by this window function, resulting in the 1.0 B. No other window functions on this page have anywhere near as low spectral noise. Sine waves that change phase by exactly 180 degrees from beginning to the end of the window result in half the amplitude assigned to the adjacent bins, with zero spectral noise outside this range. Sine waves that end 90 degrees out of phase are close to the worst case, generating some spectral noise, but the levels are many DB lower than other windows.

I have no intention of writing any papers for submission to any conference. If you believe only academics have valuable knowledge that belongs on Wikipedia, I guess there's nothing to be done. If only old and well established knowledge, rather than cutting edge technology, belongs in Wikipedia, then I can revisit this in a few years.WaywardGeek (talk) 18:32, 24 December 2010 (UTC)

I don't believe that, but we do have wikipedia policy and guidelines to follow, like WP:RS and WP:OR. So is it just a double-length Hann window then? Dicklyon (talk) 23:20, 24 December 2010 (UTC)

It is a double-length Hann window that is then split into a first and second half. The first half is then added to the second half, resulting in a single-length set of samples. I've added an informal introduction on the web page to give readers a better feeling for what's going on in this algorithm.

I read the guidelines you linked to, and I agree my web page isn't an acceptable source. Worse, I was able to get expert feedback on the algorithm, and while the algorithm does perform very well, it's a subset of "weighted overlapp-add DFT" algorithms that have been carefully explored. In my case, comp.dsp was a better place to post my algorithm than Wikipedia.org.WaywardGeek (talk) 12:13, 25 December 2010 (UTC)

Oh, I see, it's not exactly a window in the sense of the others. I'm glad you found a good place for it. Thanks. Dicklyon (talk) 16:50, 25 December 2010 (UTC)

Unnecessary complexity with the definition of N

This line threw me for a loop:

• In practice, N is typically an odd number. An even-length FFT window is generated by using only the coefficients corresponding to 0 ≤ n ≤ N-2.

Then, all of the functions are defined in terms of $N-1\,$. It seems clear that if $N\,$ were simply defined as the even-length FFT window, the function definitions would be simplified as well.

(To be fair, the triangular window with non-zero endpoints does use the odd-length $N\,$. Substituting $N+1\,$ in that case still seems like a net win.)

I imagine this might be a sort of "traditional" notation, but it sure seems to make things more confusing with no benefit that I can see. Is there a reason for it? Can we change it, or at least explain it a little better? --4368 (talk) 11:55, 26 October 2011 (UTC)

Not just the triangle, but for many windows it's useful to have a "center" point. Or at least, common, if not so useful. Might as well leave it. Dicklyon (talk) 15:17, 26 October 2011 (UTC)

Looking at all of the functions defined, $N-1\,$ seems much more common than $N\,$. That, in addition to a desire for symmetry with the way power-of-two lengths are common for FFTs, is my rationale. Could you explain how having a "center point" is actually more common/useful? Perhaps there's something in the literature not mentioned in the article? Thanks. --4368 (talk) 12:31, 27 October 2011 (UTC)

For DFT spectral analysis, it doesn't matter whether a window has a single maximum or a double maximum. Harris' rationale for a single-maximum at N/2 (N even) is that symmetry of the kind w(N/2-n)=w(N/2+n), n=1,2,...,N/2-1 results in real-valued DFT coefficients. IMO, he doesn't adequately explain why that is important, and the only reason I know is that it's an efficiency advantage when doing windowing by convolution in the frequency domain, instead of multiplication in the time domain. Other applications of window functions include FIR filtering (where the window is a lowpass impulse response or the envelope of an IIR function, such as sinc) and weighting of a statistical data distribution. In general, the time-delay of a symmetrical or anti-symmetrical FIR filter (not just window functions) have a time-delay of (N-1)/2, which is an integer number of samples for odd values of N. That is important when the filtered output has to be time-aligned with another sequence, such as the real part of an analytic signal or the synthesis stage of an audio equalizer (or other channelizer).

--Bob K (talk) 20:07, 17 March 2019 (UTC)

Details of proposed changes

First, the bullet point on $N$ (quoted above) would be removed. I believe that the existing definition of $N$ as the "width, in samples", will still be correct as-is. Then, here are some functions simplified with the new definition of $N$:

• Hann window: $w(n)=0.5\;\left(1-\cos \left({\frac {2\pi n}{N}}\right)\right),\ 0\leqslant n\leqslant N-1$
• Hamming window: $w(n)=0.54-0.46\;\cos \left({\frac {2\pi n}{N}}\right)$
• Tukey window: $w(n)=\left\{{\begin{matrix}{\frac {1}{2}}\left[1+\cos \left(\pi \left({\frac {2n}{\alpha N}}-1\right)\right)\right]&{\mbox{when}}\,0\leqslant n\leqslant {\frac {\alpha N}{2}}\\[0.5em]1&{\mbox{when}}\,{\frac {\alpha N}{2}}\leqslant n\leqslant N(1-{\frac {\alpha }{2}})\\[0.5em]{\frac {1}{2}}\left[1+\cos \left(\pi \left({\frac {2n}{\alpha N}}-{\frac {2}{\alpha }}+1\right)\right)\right]&{\mbox{when}}\,N(1-{\frac {\alpha }{2}})\leqslant n\leqslant N\color {Red}-1\\\end{matrix}}\right.$
• Gaussian windows: $w(n)=e^{-{\frac {1}{2}}\left({\frac {n-N/2}{\sigma N/2}}\right)^{2}}$

The red colored correction above was added by me, based on your statement that N="width in samples".--Bob K (talk) 20:07, 17 March 2019 (UTC)

There would also be some implicated changes on the Hann function and Kaiser window pages (and perhaps others). These changes would bring the function definitions closer in line with Wolfram MathWorld (for example, 'Hanning' Function). However, I'd like to get some kind of agreement before making any changes, since I (admittedly) am not any kind of expert on this topic, and there are a lot of involved changes. --4368 (talk) 14:47, 29 October 2011 (UTC)

In simple terms, changing N to N+1 (equivalently N-1 to N) in the w(n) formulas, simplifies most of them and widens the windows by 1 sample. Whereas now N is the width of a symmetric window and N-1 is the width of its asymmetric counterpart (by truncation), N would be the asymmetric width, and N+1 the symmetric width (obtained by extending the n-sequence from N-1 to N, or just copying w(N) = w(0)). The new definition would agree with the Harris paper and with Matlab's hann(N,'periodic') instead of hann(N,'symmetric'). The formula $w(n)=w_{0}\left(n-{\tfrac {N-1}{2}}\right)$ would simplify to $w(n)=w_{0}\left(n-{\tfrac {N}{2}}\right).$  It's a very logical suggestion. The disadvantages that come to my mind are:

• It's a lot of changes and some ripple effects (as you said).
• Wikipedia's convention would then differ from those with which we now agree, e.g. Rorabaugh, C. Britton (October 1998). DSP Primer. McGraw-Hill Professional. p. 196. ISBN 9780070540040..
• Our default window would be asymmetric, and symmetric would become the afterthought: "Generate a symmetric window by appending w(N) = w(0)." But the performance (in terms of spectral leakage metrics such as main lobe, sidelobes, and noise bandwidth) of an N+1 length symmetric window is better than an N-length asymmetric window, and it can be also implemented with an N-point DFT (or FFT) by using periodic summation (adding the N+1^th element of a data sequence to the 1^st element) instead of truncation. (see File:Comparison_of_symmetric_and_periodic_triangular_window_functions.svg)

• My intent here was to offer that as a reason to keep symmetry as our default convention. But it actually isn't, because the sum of the first and last terms of the symmetrically-windowed data sequence is w(0)•x(0) + w(N-1)•x(N-1) = w(0)•[x(0) + x(N-1)]. Therefore, w(N-1) is unnecessary, and in fact causes an extra multiplication. So after adding x(0) and x(N-1), we only use the DFT-even portion of the symmetric sequence. (The other coefficients, except n=N/2, also occur in symmetrical pairs, but the periodic summation does not force us to combine those terms prior to the DFT.)

• If we're changing conventions, consider another one (https://ccrma.stanford.edu/~jos/sasp/Matlab_Hann_Window.html), which changes our formulas from N-1 to N+1, and computes only $\{w(n),\ 1\leq n\leq N\},$ leaving out both zero-valued endpoints. But not all windows have zero-valued endpoints, so that is just a case-by-case decision, which designers can do by setting N higher by 2 than they actually want and just omit the 2 endpoints. Or with the proposed change, they would set N higher by just 1 and omit the first endpoint.

--Bob K (talk) 02:01, 18 March 2019 (UTC)

It's complicated

On further inspection, I see it's more complicated than I thought. See for example this page. The N+1 gives a "symmetric" window (N can be odd or even, giving a center point or not). But this gives the same point at beginning and end, which is zero for some windows, non zero for others, and messes up some of the analysis shown. The Hamming window in particular shouldn't have the repeated value at the end, and the hann window, with the extra zero, has the wrong periodicity to agree with note 2 if you include the extra zero. I'm not sure what we should do here. Probably discuss the alternatives and the complication. In fact, I think sampling continuous windows to get these discrete windows is inherently not quite right. Dicklyon (talk) 15:33, 29 October 2011 (UTC)

In any case, the spectra that we show are for some unstated large N, or for the continuous window function, effectively. It's not clear to me why we want these discrete expressions at all, especially given the complications that bring up. Dicklyon (talk) 17:09, 29 October 2011 (UTC)

That comment was 8 years ago. I hope you feel more comfortable with the "complications" now. And I don't know what you would propose in place of discrete expressions, unless it's a table lookup (and how would the table values be derived?).

I think the complications are manageable. The Hamming link is an interesting case, and it led me to the Hann link, which is the other "extreme". My conclusion is to stick with a convention that includes the leading "tail", even if it begins with zero. But for the reasons detailed above, I would change the default from symmetric to asymmetric/periodic [I omit DFT-even, because there is no necessity to restrict N to even values.]. It's not a slam-dunk no-brainer to make the change, but I tried to make the case for our current convention, and it really isn't there. The tie-breaker is the realization that N-length asymmetric windows don't have to take a performance hit (albeit small) compared to their N+1 length symmetric counterpart. The main reason to change is that it simplifies many of the formulas. And I think it aligns us with more authors than we now agree with (but I can't prove that). So I think it is worth doing, but it's not an overnight thing. My idea is to temporarily add a subscript (s for symmetric) to all the current w(n) functions. Then define a new temporary symbol, $w_{a}(n),$ that is asymmetric on $[0,N-1].$  As we convert formulas to their asymmetric forms, we change the subscript. And when everything is converted, we eliminate the subscript... back to just w(n).

I may start doing that soon, knowing that there might be a backlash, in which case we can just revert to the current version.

--Bob K (talk) 21:20, 18 March 2019 (UTC)

Update: I did it, and User:4368a is right. It simplifies a lot of formulas and a few explanations. Great idea, and well worth the trouble.

--Bob K (talk) 23:15, 19 March 2019 (UTC)

conversion to "vector graphics"

Regarding the last 3 edits, please explain why it is more important to have figures in .svg form than it is to have grid lines. And please explain why .svg cannot support the grid lines. As I recall, the guidelines for converting to .svg state that is should not detract from the rendered result.

--Bob K (talk) 18:52, 30 November 2011 (UTC)

Yes, we shouldn't lose the grid lines. I think it's great that the editor provided his matlab code; it should be straightforward now for him or someone else to add grid lines, and otherwise adjust the styling. Dicklyon (talk) 19:26, 30 November 2011 (UTC)

Now there are SVG images with grid lines. I set N to such a high value (2^17) that aliasing in the spectrum was eliminated and only plotted a portion of the Fourier transform. Making the SVG's was a big mess with rendering and font issues and I sympathize with anyone who made an effort for it. Olli Niemitalo (talk) 15:14, 13 February 2013 (UTC)

Two-dimensional window, separability error

The article suggests that functions of the form $\scriptstyle W(m,n)=w(r)$ are unseparable, whereas $\scriptstyle exp(-r^{2})=exp(-(m^{2}+n^{2}))=exp(-m^{2})exp(-n^{2})$ clearly is separable. 58.96.115.119 (talk) 02:03, 5 February 2013 (UTC)

I think you misread it. It's talking about a form w(r) that is not separable, in general. You are referring to the separable gaussian special case; if you wanted that case, you'd use the separable form. Dicklyon (talk) 03:21, 5 February 2013 (UTC)

I rewrote the section to include that exception. Olli Niemitalo (talk) 15:03, 5 February 2013 (UTC)

Frequency response

Is it correct to talk of a "frequency response" of a window function? A window function is not the impulse response of a system. Should we say "Fourier transform" instead? Olli Niemitalo (talk) 11:47, 14 February 2013 (UTC)

Good point. $w(t)$  is a dc-response, not an impulse response. --Bob K (talk) 16:40, 14 February 2013 (UTC)

We could explicitly say that  ${\mathcal {F}}\{w(t)\}$  is the "frequency response" to input   $1\ {\stackrel {\mathcal {F}}{\Longleftrightarrow }}\ \delta (f),$  which is probably how most people think of it. But I don't know what the concensus of the technical references might be. "Frequency domain plot" is one example. It might be customary, but it's also vague. --Bob K (talk) 16:24, 15 February 2013 (UTC)

Search string (with quotes)	Google Scholar hits	Google Books hits
"window function and its fourier transform"	23	6
"window function and its frequency response"	2	0
"window function and its frequency spectrum"	0	0
"window function and its frequency domain"	0	0

I did a bit of survey on the frequency of usage of different terms. So far "Fourier transform" seems the most common. Feel free to add further alternatives above. My guess why "frequency response" is sometimes used is that people are used to deal with filters and intuitively borrow the terminology from there. Olli Niemitalo (talk) 17:29, 15 February 2013 (UTC)

Fourier transform is a clear winner, by Wikipedia's criterion (popular usage).  My personal reason for preferring "frequency response" is different than your guess, because it actually is the spectral response to input $\delta (f).$  And the Fourier transform of a windowed waveform is the convolution of the transforms of the waveform and the window, just as in the time domain the output of an LTI system is the convolution of the input and the impulse response. --Bob K (talk) 13:46, 16 February 2013 (UTC)

I'll start converting things to "Fourier transform". What you have said also makes sense. Olli Niemitalo (talk) 16:15, 16 February 2013 (UTC)

List of window functions

I see that the Other Windows section has been marked for extension. More generally, it might be nice to include further examples of window functions. The question is which merit inclusion. As a starting point, I have compiled a list of the windows in the works of Harris and Nuttall. These miss more modern developments but should include all the classics.

Window functions and parameter choices in literature. Search string for ghit count was "xxx window" signal.

Window	Scholar ghits	Books ghits	Parameters	Peak sidelobe (dB)	Asymptotic decay (dB/octave)	Included
Rectangle Dirichlet Rectangular Unit	994 91 19,700 ambiguous	328 54 15,100 ambiguous	none	-13	-6	Yes
Triangle Fejer Bartlett Triangular	276 23 1,330 2,220	118 35 1,580 1,980	none	-27	-12	Yes
cosα(x) Hanning Hanning, if α = 2 Power-of-cosine Hann window, if α = 2	ambiguous 20,200 3 3,440	ambiguous 9,080 1 1,660	α = 1.0 α = 2.0 α = 3.0 α = 4.0	-23 -31 -39 -47	-12 -18 -24 -30	Yes
Hamming	23,900	13,800	α = 0.54 α = 0.53836 α = 0.53856	-42 -43.19 -43	-6 -6 -6	Yes
Riesz Welch Parabolic	25 456 ambiguous	10 127 ambiguous	none	-21	-12	No
Riemann Lanczos	8 150	6 76	none	-26	-12	Yes
B-spline window De la Vallé-Poussin, if order = 4 De la Vallée-Poussin, if order = 4 Parzen, if order = 4	58 6 4 ambiguous	3 4 2 ambiguous	order = 4	-53	-24	No
Tukey	1,150	391	α = 0.25 α = 0.5 α = 0.75	-14 -15 -19	-18 -18 -18	Yes
Bohman	17	8	none	-46	-24	No
Poisson Exponential Two-sided exponential	26 ambiguous 3	9 ambiguous 2	α = 2.0 α = 3.0 α = 4.0	-19 -24 -31	-6 -6 -6	Yes
Hanning-Poisson Hann-Poisson	16 1	6 2	α = 0.5 α = 1.0 α = 1.5	-35 -39 none	-18 -18 -18	Yes
Cauchy	14	7	α = 3.0 α = 4.0 α = 5.0	-31 -35 -30	-6 -6 -6	No
Gaussian Weierstrass	10,100 2	3,640 2	α = 2.5 α = 3.0 α = 3.5	-42 -55 -69	-6 -6 -6	Yes
Kaiser-Bessel Kaiser	1,280 4,110	751 4,520	α = 2.0 α = 2.5 α = 3.0 α = 3.5 Lf0 = 2 Lf0 = 3 Lf0 = 4	-46 -57 -69 -82 -39.79 -65.45 -91.22	-6 -6 -6 -6 -6 -6 -6	Yes
Barcilon-Temes Babic Temes	3 3	3 2	α = 3.0 α = 3.5 α = 4.0	-53 -58 -68	-6 -6 -6	No
Exact Blackman	34	10	none	-68	-6	Yes
Blackman	3,260	2,340	none	-58	-18	Yes
Minimum 3-sample Blackman-Harris "Minimum" 3-term	2 10	0 6	none	-71	-6
61 dB 3-sample Blackman-Harris 3-term	1 3	0 1	none	-62	-6
Minimum 4-sample Blackman-Harris "Minimum" 4-term	19 34	7 10	none	-92	-6
74 dB 4-sample Blackman-Harris 4-term	4 6	0 1	none	-74	-6
4-sample Kaiser-Bessel 4-term	2 2	2 0	α = 3.0	-69	-6	No
3-term with continuous third derivative			none	-47	-30
3-term with continuous first derivative			none	-64	-18
4-term with continuous fifth derivative			none	-61	-42
4-term with continuous third derivative			none	-83	-30
4-term with continuous first derivative Nuttall, continuous first derivative			none	-93	-18	Yes
Minimum 3-term			none	-71	-6
Minimum 4-term Blackman-Nuttall	ambiguous 23	ambiguous 0	none	-98	-6	Yes
Dolph–Chebyshev			a=5	-100	-0.0000000000

Looking at the table so far, I think that windows to potentially include are:

• Parzen window: it appears popular and is neatly linked to the rectangular and triangular windows as a B-spline.
• Bohman window: it is of some note and has good suppression for a parameterless window.
• Welch window: it seems notable although I've yet to figure out why exactly (perhaps something to do with Welch's method?).

As an aside, the Hann-Poisson seems the least popular of those currently included, however I'm very fond of the fact that it can have no peak sidelobe, which seems an interesting (and potentially useful) peculiarity. — BobQQ (talk) 09:52, 28 February 2013 (UTC)

Hi. I am having trouble reproducing the seach results. For example, the link https://www.google.com/search?q=%22welch+window%22&btnG=Search+Books&tbm=bks&tbo=1 produces 429 links instead of the 127 shown in our table. Any suggestions? Thanks.--Bob K (talk) 15:59, 28 February 2013 (UTC)

Upon further investigation, 429 is the total number of occurrences, with multiple occurrences per book. To obtain a book count, I had to hop to the last page of links (10 per page) and read just below the toolbar at top. (If obscured, click on the button labeled "Search Tools".) That produced a count of 144. Is that what you do? --Bob K (talk) 16:35, 28 February 2013 (UTC)

Have a look at the search string in table caption again, it should include the quotation marks and the word signal. I just used the number from the first result page. Olli Niemitalo (talk) 22:33, 28 February 2013 (UTC)

Thanks, that helps. The link is https://www.google.com/search?q=%22welch+window%22+signal&btnG=Search+Books&tbm=bks&tbo=1

The number on the first result page is 121, but there are only 7 result pages @ 10 per page. If you hop to the 7th results page, at the top it says "Page 7 of 64 results", which is a confusing way of saying that the number of book hits is only 64. --Bob K (talk) 00:50, 1 March 2013 (UTC)

Now that's annoying! Well, it's lucky that we are not doing rocket science here. Olli Niemitalo (talk) 01:09, 1 March 2013 (UTC)

We should probably include Parzen and Welch, but use of Bohman seems pretty rare and random. I got a much smaller Scholar ghit number for it than was listed (I updated the value from 884 to 17). We could kind of include it as a brief mention in the power-of-cosine windows section, as it is a convolution of two cos^1 windows, resulting in doubling of all dB numbers in the Fourier transform, compared to cos^1. Welch window, being a polynomial window with only a single polynomial piece, is very easy to calculate. Maybe that is why it has gained some popularity. Olli Niemitalo (talk) 22:33, 28 February 2013 (UTC)

That all seems sensible. I think the high ghits was probably from a regular Google rather than Google Scholar... — BobQQ (talk) 17:45, 1 March 2013 (UTC)

Both papers refer to the Kaiser window as Kaiser-Bessel, so I think I may change that in the article. — BobQQ (talk) 14:40, 21 February 2013 (UTC)

(Nice table!) In general it's usually futile to try to keep multiple Wikipedia articles "in synch" with each other, but perhaps we should consider synching that change with Kaiser_window. --Bob K (talk) 16:24, 21 February 2013 (UTC)

I think it will be useful to get some hit counts from Google Scholar and from Google Books, to see which names that we know of are the most common ones for a window, for example Kaiser window appears about three times as popular as Kaiser-Bessel window, so a name change is probably not warranted at the moment. These searches will also tell if a particular window has found wider use, in which case it makes sense to include it. I think we should call it a "list of window functions" rather than the current "window examples", because we have so many and appear to be aiming for thorough coverage. I also think we should not categorize the window functions to different ranges of B, but perhaps in three categories with names to the effect of: "parameter-less windows", "parameterized windows" and "combination windows". In the first category, the windows could be sorted in approximately increasing order of B. Overall, the windows can be sorted logically, like Kaiser after DPSS (which it approximates). It's a good thing to use in examples parameter values from literature, such as those listed in BobQQ's table, as then we can sometimes also get the B value from literature, along with other figures of merit (like that peak sidelobe) which we could then also present. Olli Niemitalo (talk) 21:26, 21 February 2013 (UTC)

I agree that Kaiser appears the more commonly used term (short names are generally preferable). I'll just add Kaiser-Bessel as an alias. Google hits should be a useful metric for notability. I think if something has a high count it should be included, but not necessarily that something with a low count should be excluded as it may have a very niche use that is still interesting. Equally something could be widely used without being proportionately documented.

I agree about including also windows that are important in some particularly narrow field. I guess I was aiming for excluding early windows that "died out" along the years (unless they are pedagogically useful), or were only discussed by their authors (famous or not). Olli Niemitalo (talk) 11:41, 22 February 2013 (UTC)

On organisation: I think it would be more useful to organise by property, since I would suspect most people would be interested in looking up a window function for a particular use. For example, I want something that can handle a large dynamic range, so I need good sidelobe suppression. I assume that was the original rationale. However, since some of the parametrised windows can be adjusted to change their properties, that wouldn't really work. All that information could be put in a comparison table, which would allow people to look up the windows they want. I think a good grouping would be on functional form. We could have simple windows (rectangular, triangular); those based on sums of cosines (Hann, Hamming, Blackman-Harris, Nuttal, etc.); more complicated functions, and then combination (hybrid?) windows? — BobQQ (talk) 11:17, 22 February 2013 (UTC)

That sounds like a good organization, and it doesn't prevent from sorting by B within each category, if that is deemed useful. Olli Niemitalo (talk) 11:41, 22 February 2013 (UTC)

I expanded the table with exact citations and added columns for ghits, to be filled. Olli Niemitalo (talk) 10:18, 22 February 2013 (UTC)

Power of cosine with α=4, and 3-term with continuous third derivative, ARE the same window. 2A01:119F:31B:5D00:6188:970D:5F62:7FDF (talk) 06:45, 5 May 2021 (UTC)

Missing argument for \frac

Nageh's version of MathJax is giving me that error message for several of the formulas (both under "Triangular window" and the one under "Welch window"). "Always render PNG" doesn't have this problem (I still need to try the MathJax bundled with the MediaWiki software).

Does the LaTeX code need to be fixed, or is the problem in MathJax? I don't know enough LaTeX to see anything wrong by myself. --SoledadKabocha (talk) 00:08, 6 March 2013 (UTC)

I think that should be fixed now(?) — BobQQ (talk) 14:32, 6 March 2013 (UTC)

Absurd Gaussian window clipping

The Gaussian window and seemingly other infinite windows are shown and analysed as being clipped, like the Gaussian window being clipped really short. Why would anyone in their right mind ever choose to use such a crudely clipped window for anything mostly given the poor performance it would give? If you're going to clip the Gaussian function so short to make it a window you might as well just subtract by a constant so the first and last bins are 0.

One can say the same thing about the Hamming window (which has a similar FT), and yet it is a classic.--Bob K (talk) 23:16, 3 June 2013 (UTC)

My point is it just makes the analyses pretty worthless if it shows the FT of the window that uses a completely arbitrary, crude and absurd rectangular windowing of the window. Maybe it would make more sense to represent the FT of those windows in their infinity, then what you choose to do to that window to make it finite is your choice.92.135.65.207 (talk) 20:41, 3 June 2013 (UTC)

Maybe we shouldn't include Gaussian at all (doesn't matter to me). But I don't think it's helpful to include unrealizable functions. The article is large enough already without that.--Bob K (talk) 23:16, 3 June 2013 (UTC)

Perhaps a sub/section for unbounded prototype functions is in order, even though and exactly because an unbounded window is a misnomer. Gaussian and Poisson/Exponential would fit, others? The reader must not be confused about whether these are windows or not. I don't think they are, without the prefix truncated. Olli Niemitalo (talk) 23:40, 3 June 2013 (UTC)

"an unbounded window is a misnomer" No it's not. It's described right in the introduction. The Gabor transform uses unbounded Gaussian windows, for instance. 71.167.58.21 (talk) 02:33, 27 July 2016 (UTC)

The truncation scheme described corresponds to Matlab's gausswin function, according to this ref. Maybe if we make that clear it will seem less absurd or arbitrary. Dicklyon (talk) 23:31, 3 June 2013 (UTC)

Missing factor in Dolph-Chebyshev window

Isn't there a $(-1)^{k}$ missing in front of the Dolph-Chebyshev window in frequency domain?

${\begin{aligned}W_{0}(k)=(-1)^{k}{\frac {\cos\{N\cos ^{-1}[\beta \cos({\frac {\pi k}{N}})]\}}{\cosh[N\cosh ^{-1}(\beta )]}}\end{aligned}}$
— Preceding unsigned comment added by 141.24.211.22 (talk) 13:34, 16 August 2013 (UTC)

Good question. The W₀(k) formula in our article is correct. The (-1)^k factor converts it to W(k) when w(n) is defined as $\scriptstyle w(n)=w_{0}\left(n-{\frac {N}{2}}\right),$ which is an asymmetrical N-point window. Those are fine in applications that require only the DFT of the window, because that is equivalent to using the window's N-periodic summation, and the asymmetry is hidden. That, I believe, is the application frederic harris has in mind in eq 45 of his classic paper. The definition $\scriptstyle w(n)=w_{0}\left(n-{\frac {N-1}{2}}\right)$ produces symmetrical N-point windows, which are also fine for DFT applications as well as other things, such as FIR filter design.

Our formula for w₀(n) is also correct, except for a possible normalization factor (for unity peak amplitude). But our formula for w(n) only works when N is odd.  A more general formulation that works for any integer is:

${\begin{aligned}w(n)=w_{0}\left(n-{\frac {N-1}{2}}\right)&={\frac {1}{N}}\sum _{k=0}^{N-1}W_{0}(k)\cdot e^{i2\pi k(n-{\frac {N-1}{2}})/N}\\&={\frac {1}{N}}\sum _{k=0}^{N-1}(-e^{\frac {i\pi }{N}})^{k}\cdot W_{0}(k)\cdot e^{i2\pi kn/N},\end{aligned}}$

which is the inverse DFT of  $(-e^{\frac {i\pi }{N}})^{k}\cdot W_{0}(k),$  rather than  $(-1)^{k}\cdot W_{0}(k).$

None of the other w(n) functions in the article are computed from W₀(k), so this is only needed for the Dolph-Chebyshev case.

--Bob K (talk) 14:28, 17 August 2013 (UTC)

Dolph-Chebyshev window: no context for comment about discontinuities at the window edges

User 71.167.63.24 recently added:

Due to the equiripple condition, the time-domain window may have Dirac delta discontinuities at the edges. The Taylor window approximates this response without the discontinuities, allowing the equiripples to drop off at the edges.

But harris' paper, p 71, states:

The continuous solution to the problem exhibits impulses at the boundaries which restricts continuous realizations to approximations (the Taylor approximation). The discrete or sampled window is not so restricted, and the solution can be implemented exactly.

Our article only presents the discrete window solution.
--Bob K (talk) 01:33, 21 August 2013 (UTC)

The discontinuities are still there in the discrete version, though you can't see them in WP's plot. http://www.mathworks.com/help/signal/ref/taylorwin.html

Conflicting definitions of triangular window

Our current definition of triangular window is:

$w(n)=1-\left|{\frac {n-{\frac {N-1}{2}}}{\frac {N+1}{2}}}\right|$

which intersects the n-axis at n=-1 and n=N. The Matlab definition at http://www.mathworks.com/help/signal/ref/triang.html, for N even, intersects at n=½ and n=N+½, which is equivalent to n=-½ and n=N-½, in our axis system. The point is that the underlying w₀(n) function is 1 sample narrower than our definition, according to Matlab.

A definition that would agree with Matlab is:

$w(n)=1-\left|{\frac {n-{\frac {N-1}{2}}}{\frac {N}{2}}}\right|$

--Bob K (talk) 19:34, 22 August 2013 (UTC)

Also, Harris, p 59, defines our w₀(n) as intersecting the axis at n = ±N/2, which defines its width as N, in agreement with Matlab.

--Bob K (talk) 20:05, 22 August 2013 (UTC)

Dolph–Chebyshev window: I have a curiousity motivated question

The formula:

${\begin{aligned}W_{0}(k)&={\frac {\cos\{N\cos ^{-1}[\beta \cos({\frac {\pi k}{N}})]\}}{\cosh[N\cosh ^{-1}(\beta )]}}\\\beta &=\cosh[{\frac {1}{N}}\cosh ^{-1}(10^{\alpha })]\end{aligned}}$

appears to be well-established in the literature.  But I can't help focussing on the core $\cos({\tfrac {\pi k}{N}})$ element, and seeing 2N periodicity, instead of the expected N periodicity.

So apparently the outer shell:   $\cos\{N\cos ^{-1}[\beta \ xxx]\}$   does the magic.  Is that about right?

--Bob K (talk) 01:11, 24 August 2013 (UTC)

The inner element creates a half-cycle, not a complete cycle, with the ends exceeding -1..+1 by some amount, which creates the mainlobe, as cos-1 changes from real to imaginary at that point.

Note that some references use cos(N cos-1( while others use cosh(N cosh-1 for either bottom or top, but both are equivalent. Maybe we should use the same functions for top and bottom?

— Preceding unsigned comment added by 71.167.59.208 (talk) 16:19, 24 August 2013 (UTC)

Thanks. I tracked down an example of that: http://www.ijera.com/papers/vol%201%20issue%202/012109116J.pdf It has a nice symmetry to it. I guess harris prefers having 3 cos() functions in the numerator, instead of 1 cos() and 2 cosh(). I'm inclined to leave it alone, but you've made a good point.

--Bob K (talk) 17:42, 26 August 2013 (UTC)

Further Reading

The paper "The Dolph–Chebyshev Window: A Simple Optimal Filter" by PETER LYNCH" is commonly cited as a reference for this window; should it be added to the (general) Further Reading section, or perhaps to the section on the window itself? Also, I notice, in the Further Reading section, references to papers on the Ultraspherical window (of which, Dolph-Chebyshev is a special case), but we don't seem to have a section on that window. If we want to add one, Kabal's "Time Windows for Linear Prediction of Speech" includes matlab/octave code. Aquegg (talk) 04:34, 4 September 2013 (UTC)

In fact, Bergen's code [2] seems better for octave. Aquegg (talk) 05:25, 4 September 2013 (UTC)

Section has been created. Aquegg (talk) 11:53, 3 February 2014 (UTC)

Planck-taper

The formula for the Planck-taper window function is incorrect. This is easily seen by putting n=0 or n=N-1, when the function should be zero (The appropriate Z parameter should be infinity) The correct formulae for the function are given in [3] Gordone (talk) 15:21, 5 April 2014 (UTC)

Or maybe it's correct (didn't check), and the difference is because it excludes the zero-valued endpoints. Olli Niemitalo (talk) 08:20, 7 April 2014 (UTC)

The mathematics as shown are incorrect, as Niemitalo stated above, as n approaches N-1, the filter quantity approaches 1/2, not 0! — Preceding unsigned comment added by 68.104.252.75 (talk) 23:07, 12 March 2015 (UTC)

That formula is definitely wrong, as noted above. The one cited by Gordone does work, but you have to be sure not to divide by 0.FundmntlTheorem (talk) 02:36, 18 May 2015 (UTC)

FFT of the Window functions

Hi there,

I just posted this at Help desk and a bevy of comments appeared immediately saying that it was not appropriate place for this stuff. Somebody recommended that I should post here instead.

As a part of a larger project I have to deal with Fast Fourier Transform (FFT) which is a variation of Discrete Fourier Transform (DFT). After some trials and errors I settled on Librow FFT. The source code there is in C but most of my software is in Gfortran and I had to convert Librow's source to Gfortran. I tested Librow's code before conversion using Wikipedia's Window functions. The test consisted of invoking Forward and Inverse FFT. Everything worked. The GFortran software derived from the C source code likewise worked perfectly well in a sense that by invoking the Inverse transform I could always get the original functions. Specifically I used Blackman-Harris window, Flat top window, Triangular window & Sine window. Everything worked except one thing: I could never get anything even remotely similar to the Fourier transform functions the website demonstrates. So, I began looking critically at the "Fourier Transforms" displayed on that page.

First we know that DFT gives us a set of complex numbers. The illustrations given on the web page did not mention how these seemingly real numbers had been obtained. Are they real or imaginary parts? How come the abscissas contain negative domain? In a way of reminding:

DFT of a signal $x$ is defined (Stanford) as:

$\mathrm {X} (\omega _{k})\triangleq \sum _{n=0}^{N-1}x(t_{n})e^{-j\omega _{k}t_{n}}~~~k=0,1,2...N-1$

That is one definition. According to Discrete_Fourier_transform#Definition, it is an N-periodic sequence. So that includes negative values of k. The plots you see in the article are 20•log₁₀(|X_k|). Code is available for inspection at Rectangular.svg

--Bob K (talk) 20:15, 19 June 2015 (UTC)

where

$\omega _{k}~\triangleq ~{\frac {k2\pi }{NT}}~~~$; where N - number of samples; 1/T - sampling rate

I don't see how one can get negative numbers of anything for the abscissas.

This situation is very unsettling for me because I don't understand what is going on, how those functions were obtained, why my real and imaginary parts of FFT differ from the illustrations given in the Wikipedia article. Am I on the right track or what? Now I have to question a lot of things. I am wondering if there is anybody out there who can explain to me the discrepancy? Thanks --AboutFace 22 (talk) 15:36, 16 June 2015 (UTC)

it's odd anyone directed you here. An article's Talk page is only for discussing how to improve the article, not a general discussion of the topic nor for helping with people's problems in the domain. You would need to find a technical forum for FFTs. Good luck. Strebe (talk) 20:14, 16 June 2015 (UTC)

I suppose so, but if the article isn't clear enough that the OP can figure it out, then it seems that this could be a good place to discuss it. Gah4 (talk) 01:25, 17 February 2016 (UTC)

Seems to me that the OP might have missed that the graphs are logarithmic on the y-axis. Gah4 (talk) 01:25, 17 February 2016 (UTC)

Well, another blow :-) I think my post may be considered an attempt to improve the article, provided my comments make sense. But to determine it is the case the post should be read. I reviewed most of the previous posts and it seems many competent mathematicians dwell here. Thanks, - --AboutFace 22 (talk) 00:55, 17 June 2015 (UTC)

Maybe you could try posting your question on an external forum such as this one. Or perhaps try emailing the author of the Librow article you cite. I'm neither a mathematician nor a coder, but it seems likely that your problem will be resolved outside Wikipedia. Best of luck! >MinorProphet (talk) 07:58, 18 June 2015 (UTC)

Color choice is not contrasting enough: Window functions in the frequency domain

This image does use colors that are not contrasting enough. Prefer a clear bright yellow that makes a clear destinction and isn't too close to orange or green. Similarily, using blue and only adding red/green to it to create other shades of blue makes it too hard to distinguish. Please consider how different people have different color perceptions. As such, prefer brightness contrast over color contrast (that different people perceive differently). — Preceding unsigned comment added by 88.219.148.170 (talk) 16:47, 10 February 2016 (UTC)

Windows in actual use

I have always thought that in actual use, and especially in the case of long signals, one applied a window function at the ends, and left most of the signal as-is. This happens naturally with the rectangular window, but the triangle would turn into a trapezoid, and other windows would also look different. One might have signals thousands, or even millions of points long. All that is needed is to remove the effects from the discontinuity due to the periodicity of the DFT, or at least get the effect low enough that one can live with it. Yet the windows, and spectra shown, don't seem to work this way. Am I missing something? Gah4 (talk) 01:49, 17 February 2016 (UTC)

For starters, it's the same question, discrete-time or continuous-time. The DFT has nothing to do with it. Given an effectively infinitely long function s(t), and a finite window w(t) (rectangular, Hann, trapezoidal, etc),

${\mathcal {F}}\{s\cdot w\}={\mathcal {F}}\{s\}*{\mathcal {F}}\{w\},$

and your question is "When w(t) is relatively long, why would one choose a conventional window instead of a more trapezoidal-like window, for spectral analysis?". Throwing in the DFT adds unnecessary complexity. See Spectral_leakage#Discrete-time_functions.

--Bob K (talk) 16:11, 17 February 2016 (UTC)

And the answer is that just as a trapezoidal-like window is better than rectangular in terms of sidelobes (resolution of disparate amplitude sinusoids) and worse than rectangular in terms of main-lobe width (resolution of similar amplitudes), a conventional window (e.g. Hann or Nuttall) is better than trapezoidal-like (e.g. Tukey or Plank-taper) in terms of sidelobes and worse than trapezoidal in terms of main-lobe width.

--Bob K (talk) 16:53, 17 February 2016 (UTC)

Your example of "millions of points" implies that your trapezoidal choice would be similar to a Tukey or Plank-taper function with extremely narrow "skirts". In the limit, they become essentially rectangular. So you might as well just use the simpler rectangular window.

--Bob K (talk) 17:07, 17 February 2016 (UTC)

In Fourier terms, the sharpness of the transition determines the frequency components. Right now, I am working on smoothing the transitions at the beginning and end of audio files (CD tracks). The problem is a little different from the DFT problem, as the ear is more sensitive to high frequencies. (Most audio sources have lower amplitude at high frequencies.) A sharp edge makes a very noticeable click. I want to smooth the transition enough to avoid the click, but otherwise not change the main part of the audio track. Gah4 (talk) 09:34, 18 February 2016 (UTC)

OK, then the missing point you are looking for is that window functions can be used as lowpass filters, but it is implemented by convolution, not multiplication, in the time domain. When you apply them by multiplication, the purpose is spectral analysis.

--Bob K (talk) 10:48, 18 February 2016 (UTC)

The human aural system works in both time and frequency domain, so the signals have to be considered both ways. I want to avoid the click that comes at the beginning, so it is both time and frequency domain. Smoothing the transition at the beginning and end is a low-pass filter only for the beginning and end, with no filter in between. Gah4 (talk) 20:58, 18 February 2016 (UTC)

Looking at some Tektronix articles, it seems that spectrum analyzers tend (maybe tended) to do a series of 1024 point DFTs and display them sequentially. That is, again, both time and frequency domain. For an audio signal, such a series of transforms would have an audible effect at the transition. Gah4 (talk) 20:58, 18 February 2016 (UTC)

I don't care about any of that. You are way off the original target you wanted help with. I am not interested in your game.

--Bob K (talk) 22:16, 18 February 2016 (UTC)

It is the original target that I wanted, but I didn't explain it very well. OK, the reason for asking was that I was looking at the transform graphs and realized that they didn't apply the way I wanted to use them. Some years ago, 1024 points was a lot to compute in the time available, so things might have changed over the years. Thanks. Gah4 (talk) 09:15, 21 February 2016 (UTC)

The DFT is greatly misunderstood, by the way. It's best thought of as just a discrete-frequency sampling of the actual continuous-frequency DTFT (Discrete-time_Fourier_transform#Sampling_the_DTFT). Whatever undesirable things happened to the DTFT as a result of DSP manipulations are merely sampled, not created, by the DFT. What gets lost, when you sample the DTFT, is whether the DTFT was actually a continuous-frequency or discrete-frequency function. If it was actually a discrete-frequency function, then the original discrete-time function was periodic, and it can be unambiguously recovered by the inverse DFT. If the DTFT was actually a continuous-frequency function, the inverse DFT can only recover a periodic summation of the original discrete-time function. If the periodic summation does not cause overlap of the copies of the original discrete-time function, then one cycle of the inverse DFT is the original function. A necessary and sufficient condition for that to happen is that the original function has a finite number of non-zero samples, and the parameter N used to sample the DTFT (as follows):

Yes, but the DFT is often used on finite length regions of longer signals. Even more, sharp transitions may be added when they don't exist in the original signal. Gah4 (talk) 09:34, 18 February 2016 (UTC)

If you're still talking about lowpass filtering, we're talking about two different things.

--Bob K (talk) 10:48, 18 February 2016 (UTC)

$\underbrace {X_{1/T}\left({\frac {k}{NT}}\right)} _{X_{k}}=\sum _{n=-\infty }^{\infty }x[n]\cdot e^{-i2\pi {\frac {kn}{N}}}\quad \quad k=0,\dots ,N-1$

must be large enough that the individual terms of this periodic summation do not overlap; i.e. the duration of the non-zero samples in each term is not greater than N:

$x_{N}[n]\ {\stackrel {\text{def}}{=}}\ \sum _{m=-\infty }^{\infty }x[n-mN].$

--Bob K (talk) 18:16, 17 February 2016 (UTC)

Section 1.4 issue

Reference #10 (http://www.bksv.com/doc/bv0031.pdf Technical Review 1987-3 Use of Weighting Functions in DFT/FFT Analysis (Part I); Signals and Units) asserts the following:

An application where Rectangular weighting is a "must", is in system analysis using a pseudo-random excitation signal. A pseudo-random signal is a periodic signal with its period length adjusted to the record length T of the analysis. All the components of the pseudo-random signal will therefore coincide with the centre frequencies of the filters (lines) and the analysis will be free of leakage assuming Rectangular weighting is used (optimal situation or "best case").

This assertion is false, and therefore we need to be careful about the claim "A window function is also not used when a periodic signal's period matches that of a Fourier transform".

To understand, let the filter/line center-frequencies be k/T, for integer values of k. A component $\cos \left(2\pi {\tfrac {k}{T}}t\right),$ rectangularly windowed to interval [0,T], will have a sinc-shaped spectral leakage pattern (Fourier transform) with zeros at every center-frequency except k/T. So computing only those lines gives the appearance of no leakage, whether the windowed function is repeated periodically or not. Periodic repetition causes the entire Fourier transform to be zero at every frequency except k/T, which is what the author interprets as no leakage.

However, a component $\cos \left(2\pi {\tfrac {k+0.5}{T}}t\right),$ rectangularly windowed to interval [0,T], will also have a sinc-shaped spectral leakage pattern (Fourier transform), but it will have non-zero values at every center-frequency. The peak amplitude at frequencies k/T and (k+1)/T will be distorted (reduced) by about 4 dB relative to the previous case (the $\cos \left(2\pi {\tfrac {k}{T}}t\right)$ component), due to scalloping loss. And the amplitude at frequency (k+10)/T (for example) will be only about 26 dB lower than that, which makes it impossible to resolve a lower-level component at that frequency using a rectangular window. In this case, periodic repetition of the windowed function does not hide the leakage. It does cause the underlying Fourier transform to be zero in-between the center-frequencies, but all the center-frequencies contain non-zero leakage, which can be redistributed (but not eliminated) by a non-rectangular window function.

--Bob K (talk) 16:06, 15 March 2016 (UTC)

The same problem appears to apply to the unreferenced shaft alignment claim. And the OFDM point is unnecessary at best, irrelevant at worst, because no OFDM algorithm description calls for windowing. The same is true when FFTs are used for fast convolution and probably many other non-spectral-analysis applications. No need to list them all here... this article is about windows, not FFTs.

--Bob K (talk) 11:59, 16 March 2016 (UTC)

Doesn't the +0.5 make the signal have a period of 2 T and therefore violate the premise of period T? Glrx (talk) 18:54, 20 March 2016 (UTC)

${\tfrac {k+0.5}{T}}$ is the frequency (cycles per second). Therefore, the period is ${\tfrac {T}{k+0.5}}$ (seconds per cycle). The number of cycles per T sec is $\scriptstyle k+0.5$.
--Bob K (talk) 21:45, 21 March 2016 (UTC)

If in T seconds you have a half cycle left over, then the period is 2 T not T. That is, everything repeats over 2 T. Glrx (talk) 18:51, 24 March 2016 (UTC)

Oh, now I see what you mean. However, pseudorandom usually means it is generated randomly (in some sense) for a known duration (T), and it is repeatable. Repeating it with period T makes it periodic, regardless of its frequency content. Then the Fourier transform of the periodic signal is a line spectrum (Fourier series). A sinusoidal component with frequency ${\tfrac {k}{T}}$ will have just one line (no leakage). If one knows apriori that all the components are harmonics of ${\tfrac {1}{T}}$, and the purpose of analysis is to determine which harmonics are present, then rectangular windowing is indeed necessary. Good point!
--Bob K (talk) 12:33, 25 March 2016 (UTC)

Belatedly pinging @Damian Yerrick:, who was the last to edit the offending section, just to make sure he is aware of the removal and subsequent discussion; I have no opinion other than that this edit seems to satisfactorily resolve the issue. --SoledadKabocha (talk) 00:11, 17 May 2016 (UTC)

External links modified

Hello fellow Wikipedians,

I have just added archive links to 2 external links on Window function. Please take a moment to review my edit. If necessary, add {{cbignore}} after the link to keep me from modifying it. Alternatively, you can add {{nobots|deny=InternetArchiveBot}} to keep me off the page altogether. I made the following changes:

• Added archive http://web.archive.org/web/20090425152259/http://ccrma.stanford.edu:80/~jos/sasp/Properties.html to https://ccrma.stanford.edu/~jos/sasp/Properties.html
• Added archive http://web.archive.org/web/20080704210436/http://ccrma.stanford.edu/~jos/sasp/Rectangular_window_properties.html to https://ccrma.stanford.edu/~jos/sasp/Rectangular_window_properties.html

When you have finished reviewing my changes, please set the checked parameter below to true or failed to let others know (documentation at {{Sourcecheck}}).

N An editor has determined that the edit contains an error somewhere. Please follow the instructions below and mark the |checked= to true

• If you have discovered URLs which were erroneously considered dead by the bot, you can report them with this tool.
• If you found an error with any archives or the URLs themselves, you can fix them with this tool.

Cheers.—^{cyberbot II}_{Talk to my owner:Online} 22:50, 18 March 2016 (UTC)

Unfortunately, those archived sources are not useful. It's best to just remove the links completely, which I will do.--Bob K (talk) 02:55, 19 March 2016 (UTC)

Signs

There is a recent edit, and revert, regarding the signs of the Blackman and Blackman-Harris window functions. Looking at the actual references, they are inconsistent on these signs.

Note that mathematical convention is normally to put the sign into the unknown constant, instead of into the summation, for the more general case.

But given that two reliable sources (Stanford University and National Instruments) can't agree on the sign, someone should work this out. Gah4 (talk) 18:22, 11 February 2017 (UTC)

The 10 Feb version of Blackman Window was incorrect for w[n] defined on 0 ≤ n < N. It might be correct for w₀(n), defined on -N/2 ≤ n ≤ N/2. So the 11 Feb correction is the right version. Whether or not the coefficients should include negative signs is a different issue. In general, I would expect that they would, and some references surely use that convention. But in this case, we have a class of windows ("cosine sum") that all exhibit the property that their even-numbered coefficients are positive and their odd-numbered coefficients are negative. That is a distinctive feature of the class, and it is made more apparent by this formulation (where all coefficients a_k ≥ 0):

$w(n)=\sum _{k=0}^{K}(-1)^{k}a_{k}\;\cos \left({\frac {2\pi kn}{N-1}}\right),\quad 0\leq n\leq N-1$

--Bob K (talk) 17:11, 30 September 2017 (UTC)

I strongly believe the signs should go into the coefficients. It will make manipulation of the equations easier and less error-prone with just addition. The signs alternating is not a rule that could not be broken. Consider for example "genetic algorithm"-type optimization of window functions. Would one optimize coefficients with one sign each only? I would not as no-one has shown evidence that the signs will always alternate for useful window functions. Olli Niemitalo (talk) 04:40, 6 May 2018 (UTC)

Strongly? Well I strongly disagree with you for the reason I already mentioned, and these:

• The 15-year history of this article is also against you... the coefficients have always been positive-valued. That convention actually dates back at least as far as the 1978 frederic harris paper (page 63, eq 31b).
• It is also the convention adopted by MATLAB (e.g. https://www.mathworks.com/help/signal/ug/generalized-cosine-windows.html and http://www.mathworks.com/help/signal/ref/blackmanharris.html).
• In evaluating the formulas:

$w(n)=\ w_{0}\left(n-{\tfrac {N-1}{2}}\right)$

$w_{0}(n)\ =w\left(n+{\tfrac {N-1}{2}}\right),$

it's the cos() functions that change sign, not the coefficients.

--Bob K (talk) 18:47, 6 May 2018 (UTC)

You are right, I was wrong. I figured out the reason for the alternating sign: A "zero-centered" version of such a window has the same coefficients and only additions in the formula. In other words the value of the cosine terms, before multiplication by the coefficients, is always positive at the center of the window, and alternates at each end. The article's formulas need the alternating signs to take this into account. I made the common mistake of forgetting that the article does not have zero-centered windows functions. However, the coefficients need not be positive. Olli Niemitalo (talk) 14:58, 7 May 2018 (UTC)

Perfect windowing function!

1. Double 'k'
2. Create a B–spline window with 'k'

rinse and repeat

This procedure reduces sidelobe levels each time it is done!

Cosine sum optimization

cos(2 pi n) can be turned into cos(4 pi n) by (cos(2 pi n))²×2-1 so that another cosine won't have to be calculated. 2A01:119F:21D:7900:54E1:9029:DEED:43A1 (talk) 09:44, 8 August 2018 (UTC)

There's more to it. cos (6×π×n) is also (cos (2×π×n))³×4-(cos (2×π×n))×3. And cos (8×π×n) is also (cos (2×π×n))⁴×8-(cos (2×π×n))²×8+1. So we have t=cos (2×π×n), and five cosine sum terms:

• cos (0×π×n)=1
• cos (2×π×n)=t
• cos (4×π×n)=2t²-1
• cos (6×π×n)=4t³-3t
• cos (8×π×n)=8t⁴-8t²+1

Five cosine sum terms with one cosine computation.79.185.231.241 (talk) 17:59, 2 May 2021 (UTC)

Approximate confined Gaussian window

This section contains the statement:

The temporal width of the approximate window is asymptotically equal to Nσ_t for σ_t < 0.14.

Looking at the σ_t=0.1 example, the 0.1•N width occurs at an amplitude of about 0.94 (-0.5 dB). That seems like an unusually high level at which to define a window's "width".  The -3 dB width, for example, is about 0.25•N.  I'm going to assume, without proof, that we're actually talking about the temporal standard deviation, which is actually a measure of half-width.  So, multiplying by 2, the 0.2•N "width" occurs at an amplitude of about 0.8 (-2 dB), which is somewhat more intuitively pleasing. Bottom line: I'm going to change "temporal width" to "standard deviation".
--Bob K (talk) 16:27, 25 October 2018 (UTC)

How would a function like this rolloff?

The sine window to the power of the inverse of the sine window

Hfaiovena4t (talk) 05:45, 18 September 2019 (UTC)

This forum is for discussion about improving the article. Perhaps someone at https://dspguru.com/comp.dsp/ or https://www.dsprelated.com/groups/comp.dsp/1.php will take an interest in your question.

--Bob K (talk) 12:36, 18 September 2019 (UTC)

Does "lower noise bandwidth" mean "lower-noise bandwidth" or "smaller noise bandwidth"?

The current article version contains the text:

"But the function designed for N+1 or N+2 samples, in anticipation of deleting one or both end points, typically has a slightly narrower main lobe, slightly higher sidelobes, and a slightly lower noise bandwidth."

What is meant: "lower-noise bandwidth", "smaller noise bandwidth" , or something else? Since "high" and "low" are already in use for the height of the graphs, I suggest to use "large" and "small" for the bandwidth, to help prevent misunderstanding.Redav (talk) 14:24, 18 July 2020 (UTC)

"smaller noise bandwidth" works fine. I'll make the change if you haven't.--Bob K (talk) 15:31, 18 July 2020 (UTC)

Asymmetric

There are these useful alternative ways to see a window function:

1. A prototype continuous-time function that is zero-valued outside an interval. (Not applicable to all window functions.)
2. A finite-length discrete-time sequence, possibly obtained by sampling the continuous-time function.
3. A two-way infinite-length periodic extension of the finite-length sequence.
4. A two-way infinite-length sequence obtained by zero-padding the finite-length sequence on both sides.

I think only those windows should be called "asymmetric" that are asymmetric in all applicable views. For examples of such window functions, see M. Schnell, M. Schmidt, M. Jander, T. Albert, R. Geiger, V. Ruoppila, P. Ekstrand, M. Lutzky, B. Grill, MPEG-4 Enhanced Low Delay AAC - a new standard for high quality communication, 125th AES Convention, San Francisco, CA, USA, preprint 7503, Oct. 2008 or Schnell, M., et al. 2007. Enhanced MPEG-4 Low Delay AAC – Low Bitrate High Quality Communication. In 122th AES Convention. Olli Niemitalo (talk) 08:13, 9 August 2020 (UTC)

Hi Olli. It's been a while. The term asymmetric is applicable to the only view defined in the article. Or to put it another way, the term is clearly defined in the article. Other articles or references may define it to suit their particular purposes. Perhaps you would like to add a section about all the views that are not covered in the article. Or perhaps just a footnote to the effect that our definition is not ubiquitous across the literature (which is not at all unusual).

Otherwise, what term are you proposing instead? DFT-even? Periodic? Those are the only ones I know of, and I don't think either of them is as descriptive as Asymmetric. And none of them are ubiquitous in the literature. To my surprise, a google search for the actual term DFT-even only turned up the original 1978 article, some amateurish chat pages, and the abstract of an article containing the statement "It can be shown [for short window lengths], that the DFT-even sampling technique as proposed by Harris is not the most suitable one."

--Bob K (talk) 15:52, 9 August 2020 (UTC)

Hi Bob! Yep I've spent much more time at DSP Stack Exchange lately. It might be best to be verbose as in "has a symmetric periodic extension", while "periodic" is also popular but not very descriptive and is also technically correct only in view 3 which is not the main view 2 of the article (the lede takes view 1 or 4). "Asymmetric", while technically correct in view 2, not in view 3 and possibly not in views 1 and 4, is only used in this article, and is not very descriptive. I think Harris means by "even" (also in "DFT-even") not even-length sequences but sequences with even symmetry, in contrast to an odd symmetry. "DFT-odd" is then a misnomer as we are not dealing with anti-symmetric windows. Olli Niemitalo (talk) 06:17, 10 August 2020 (UTC)

Good point. Upon re-reading Harris, I noticed the term DFT symmetry (bottom of p 52). So DFT-symmetric is another possibility, and less of a mouthful than "has a symmetric periodic extension" (which would be better as a footnote).

--Bob K (talk) 12:02, 10 August 2020 (UTC)

"DFT-symmetric" sounds fine to me! Olli Niemitalo (talk) 14:25, 10 August 2020 (UTC)

And thanks so much for all your help, now and before. You are amazing.

--Bob K (talk) 15:27, 10 August 2020 (UTC)

Olli, I scanned the links you provided, and my conclusion is that your problem is easily addressed by moving Section 1.5 to 1.1.5, where it will be clear that the symmetry/asymmetry discussion is about windows for DFT spectral analysis, not filter banks or filtering.

--Bob K (talk) 18:21, 9 August 2020 (UTC)

Generalized Adaptive Polynomial (GAP) window

The figure provided looks fine, but I was not able to reproduce it using the formula provided and the coefficients published at https://www.semanticscholar.org/paper/Generalized-Adaptive-Polynomial-Window-Function-Justo-Beccaro/d8a89c11dcd8698b4ec47f5f9f2d015807d0bf75/figure/0 This is my attempt, using the plotWindow function at https://commons.wikimedia.org/wiki/File:Window_function_and_frequency_response_-_Rectangular.svg

N = 2^14;
ak = [-1.950123 1.751639 -0.965132 0.362922 -0.094316 0.014043 0.000638 -0.000907 0.000200 -0.000016];
k  = 1 : length(ak);
n  = -N/2 : N/2;
w = [ ];
for m=n
   w(end+1) = sum(  ak.*((m/N).^(2*k))  );
endfor
w = w - min(w);
w = w / max(w);
plotWindow(w, "GAP")

I also tried these (Hann) coefficients:
ak = [-0.827799 0.296717 -0.354860 0.754177 -0.972745 0.759919 -0.365929 0.106195 -0.017029 0.001159];

--Bob K (talk) 20:13, 31 October 2020 (UTC)

Probably you need an a0 term of 1, and maybe run from -N:N. But that still doesn't quite do it. Dicklyon (talk) 01:19, 1 November 2020 (UTC)

This seems to work pretty nearly. I have no idea why the 1.65 (I haven't looked at the paper).:

N = 2^10;
ak = [-1.950123 1.751639 -0.965132 0.362922 -0.094316 0.014043 0.000638 -0.000907 0.000200 -0.000016];
ak = [-0.827799 0.296717 -0.354860 0.754177 -0.972745 0.759919 -0.365929 0.106195 -0.017029 0.001159];
k  = 1 : length(ak);
n  = (-1.65*N):(1.65*N);
w = [ ];
for m=n
   w(end+1) = 1 + sum(  ak.*((m/N).^(2*k))  );
end
figure(1)
plot(w)

The article is here: https://ieeexplore.ieee.org/stamp/stamp.jsp?tp=&arnumber=9223641

It has the same formula (#2) that I am using (n = -N/2 : N/2).

When n=-N/2:N/2, the statement w=w-min(w) causes an effective a0=0.4, which gives a better result than 1.0.

Instead of n=(-1.65*N):(1.65*N), I think you can get the same effect with w(end+1)=sum( ak.*((m/N*2*1.65).^(2*k)) ).

--Bob K (talk) 03:06, 1 November 2020 (UTC)

The article says a0 = 1. And the shape starts to look more Hann-like if you go out to 1.65*N. Obviously, something is wrong, but I don't think subtracting the min is the answer. Dicklyon (talk) 01:50, 2 November 2020 (UTC)

Turns out the authors have a matlab implementation at Mathworks File Exchange. It has different coefficients, but the big difference is that they convert the index sequence to an x sequence by dividing by standard deviation of the index sequence, rather than by N. That ratio N/std(...) is about 3.3, changing the needed N/2 to 1.65*N. The article is not self-consistent, and this approach to normalizing in the Matlab code is also not quite consistent with the letting t run to T/2. Too bad they messed up this way. Here's what they have for Hann:

   case 'hann' 
    a2 = -0.8236640350672578; a4 = 0.2396934226088473; a6 = -0.0910329438155984; 
    a8 = 0.1546641760773942; a10 = -0.2008340012917025; 
    a12 = 0.1591065890832292; a14 = -0.0777111572266440; a16 = 0.0228723527427099; 
    a18 = -0.0037192072905112; a20 = 0.0002565996927828;

Dicklyon (talk) 02:47, 2 November 2020 (UTC)

Yep, that works. Congratulations. Here is my original code, slightly modified:

% optimized Nutall
ak = [-1.9501232504232442 1.7516390954528638 -0.9651321809782892 0.3629219021312954 -0.0943163918335154 ...
0.0140434805881681 0.0006383045745587 -0.0009075461792061 0.0002000671118688 -0.0000161042445001];

N = 2^14;
k  = 1 : length(ak);
n  = -N/2 : N/2;
sigma = std(n);
w = [ ];
for m=n
   w(end+1) = sum(  ak.*((m/sigma).^(2*k))  );
endfor
w = w + 1;
w = w / max(w);
plotWindow(w, "GAP")

Note that when n=-N/2:N/2, mean(n)=0. No need to compute it and subtract it.
I also noted that w+1 is slightly better than w-min(w), even though -min(w) = 1.0002
It doesn't matter now, but when using the original normalization factor (N), the function width exceeded the window width (N), so its min value never got near -1. That is why -min(w) = 0.4 was a better choice.

Their matlab implementation, with a couple of improvements, looks like this:

% optimized Nutall
ak = [-1.9501232504232442 1.7516390954528638 -0.9651321809782892 0.3629219021312954 -0.0943163918335154 ...
0.0140434805881681 0.0006383045745587 -0.0009075461792061 0.0002000671118688 -0.0000161042445001];

N = 2^14;
n = -N/2:N/2;
x = n/std(n);
w = 1;
for k = 1 : length(ak)
   w = w + ak(k)*(x.^(2*k));
endfor

w = w/max(w);
plotWindow(w, "GAP")

--Bob K (talk) 15:51, 2 November 2020 (UTC)

You should put that code in your new figure description. File:Window function and frequency response - GAP optimized Nuttall.svg. Dicklyon (talk) 18:11, 2 November 2020 (UTC)

The source code section of that file has a link to the place where all the source code resides for all of the window functions, including this one. The link is https://commons.wikimedia.org/wiki/File:Window_function_and_frequency_response_-_Rectangular.svg

--Bob K (talk) 18:19, 2 November 2020 (UTC)

Replacement of N + 1 by L

In this diff the formulas for the approximate confined Gaussian window and the Tukey window have been changed. It seems that $N+1$ should be replaced by $L$. The formulas for the approximate confined Gaussian window seem to changed correctly. But in the formulas for the Tukey window $L$ has been used to replace $N$ instead of $N+1$, which changes the window definition and the formulas for the Tukey window seem to be wrong now. If this change wasn't intended, it should be fixed. Christian Gruber (talk) 09:56, 13 January 2021 (UTC)

Good catch. Thank you. I also clarified that the convolution described there is in terms of the convolution of continuous functions. In terms of discrete convolution, each function has one sample more than the number of sample-intervals.

--Bob K (talk) 19:09, 13 January 2021 (UTC)

Discrete convention is bad idea at all for purpose of this page

Essential purposes of window functions are not related to their discretisations within particular applications. Discretisation of window functions, where it needed, is separate problem. Lets not mix that all into common messy heap. Lets define window function as function defined on real range [-1,1] instead. Almost all windows have simplest definition in this form, and simplest method to get discrete version from it is trivial and common, but more advanced methods are also may be useful, and they may relate on rather technical application-specific details, and not related to selection of particular window function.

There are two well-known windows which can be complicated to understand in this context, Dolph-Chebyshev and ultraspheric. Here problem can arise because of specific way how they defined mathematically. They are defined by periodic functions in frequency domain, with explicit parameter N in definition, hence they intrinsically discrete in time domain. From such definition, we have natural prescription how to calculate window in discrete form only, but it is not prescription how to understand and use such calculated window, we can still understand it as discrete samples of some non-discrete function to use it same way as any other window function. — Preceding unsigned comment added by Lexey73 (talk • contribs) 12:29, 19 December 2021 (UTC)

The separate articles Hann_function and Kaiser_window are examples of what you suggest except for the parameter $L,$ which you suggest should be simply 2. Both the zero-phase forms and the lagged forms are equally simple functions, but someone decided both windows deserve their own article, which is fine. And that is the approach you should take for your two examples. Let's see what you come up with, and then revisit how it affects this article, or not.

--Bob K (talk) 23:26, 19 December 2021 (UTC)

That "L" is trivial scaling factor, it only unnecessary complicates equations, and makes illusion that it is essential parameter of window function. Anyone can apply such trivial scaling where needed. Lets simply say something like "support bounds of windows here assumed to be [-1,1]" in "convention" section,

The continuous Hann function is not defined as duration 2. In these examples, it is length T :  https://www.sciencedirect.com/topics/engineering/hanning-window and http://www.vibrationdata.com/tutorials_alt/Hanning_compensation.pdf

And in this one it is T_Span :  https://www.dataphysics.com/downloads/technical/Effects-of-Windowing-on-the-Spectral-Content-of-a-Signal-by-P.-Wickramarachi.pdf

And here is one with length L (see eq.(3)): https://zenodo.org/record/1280930

It is easier for someone to set L=1 (or 2) in a general version of a formula, or a subsequent result of the formula, than to reinsert a missing parameter in all the correct places. For instance these results in Hann_function:

$W_{0}(f)={\tfrac {1}{2}}{\frac {\sin(\pi Lf)}{\pi f(1-L^{2}f^{2})}}$

$W_{0}(f)={\tfrac {1}{2}}{\frac {\sin(\pi Lf)}{\pi f}}+{\tfrac {1}{4}}{\frac {\sin(\pi L(f-1/L))}{\pi (f-1/L)}}+{\tfrac {1}{4}}{\frac {\sin(\pi L(f+1/L))}{\pi (f+1/L)}}.$

Not so trivial, I would say.

--Bob K (talk) 01:07, 27 December 2021 (UTC)

and remove all that annoying "N" and "L" from where they not really necessary.

That is how you do the transformation from continuous to discrete, which is your original suggestion.

I think it is bad idea to make separate page for every simple thing like Hann_function and Kaiser_window Lexey73 (talk) 10:36, 26 December 2021 (UTC)

But those articles are able to go into greater depth, if someone cares to do so. Window function is already long enough.

--Bob K (talk) 23:25, 26 December 2021 (UTC)

$W_{0}(L,f)={\frac {L}{2}}W_{0}({\frac {L}{2}}f)$ - it is common formula for any window to convert it from [-1,1] convention to [-L/2,L/2]  --Lexey73

The fact that it's correct does not make it common. Much more common to set T or T_Span or L to whatever specific length an application calls for. I've given you several online examples. Where are yours? --Bob K (talk) 21:14, 27 December 2021 (UTC)

$W_{0}(f)={\frac {\sin(2\pi f)}{2\pi f}}+{\tfrac {1}{2}}{\frac {\sin(2\pi (f-1/2))}{2\pi (f-1/2)}}+{\tfrac {1}{2}}{\frac {\sin(2\pi (f+1/2))}{2\pi (f+1/2)}}.$ for [-1,1] convention (simply replace L by 2 everywhere in formulas where [-L/2,L/2] convention was used)  --Lexey73

Yeah... it is simple... which is my point. Thank you. --Bob K (talk) 21:14, 27 December 2021 (UTC)

Note that your first formula is wrong Lexey73 (talk) 14:57, 27 December 2021 (UTC)

$W_{0}(f)={\tfrac {1}{2}}{\frac {\sin(\pi Lf)}{\pi f}}+{\tfrac {1}{4}}{\frac {\sin(\pi L(f-1/L))}{\pi (f-1/L)}}+{\tfrac {1}{4}}{\frac {\sin(\pi L(f+1/L))}{\pi (f+1/L)}}$

Here you are caught by illusion that L is essential parameter of function, because L not appeared everywhere near f, but it exactly equals to:

$W_{0}(f)=L\left({\tfrac {1}{2}}{\frac {\sin(\pi Lf)}{\pi Lf}}+{\tfrac {1}{4}}{\frac {\sin(\pi (Lf-1))}{\pi (Lf-1)}}+{\tfrac {1}{4}}{\frac {\sin(\pi (Lf+1))}{\pi (Lf+1)}}\right)$

Lexey73 (talk) 18:56, 27 December 2021 (UTC)

Declaring a mathematical equivalence wrong is not a credible way to make your point. But I'm OK with either expression, as long as they are parametric in L.

BTW, what I like about $L(f\pm 1/L)$ vs $(Lf\pm 1)$ is that the frequency offset between terms is more readily apparent (at least to me).

--Bob K (talk) 21:38, 27 December 2021 (UTC)

It is clear that two formulations of same function are not equivalent, and I see that second is exact, hence something wrong with first expression. Maybe it is approximation? than you will say clearly that it is approximate equation. And it is unclear reason to introduce approximate equation which is only slightly simpler than exact equation. So I suggest to simply remove that suspicious first equation from that page if you can't clarify this question in any other way. --Lexey73 (talk) 08:46, 28 December 2021 (UTC)

And yesterday you said: "it exactly equals to:

$W_{0}(f)=L\left({\tfrac {1}{2}}{\frac {\sin(\pi Lf)}{\pi Lf}}+{\tfrac {1}{4}}{\frac {\sin(\pi (Lf-1))}{\pi (Lf-1)}}+{\tfrac {1}{4}}{\frac {\sin(\pi (Lf+1))}{\pi (Lf+1)}}\right)$"

which I agree with. Apparently all you want is the last word, so I'm probably done with this thread.

--Bob K (talk) 15:59, 28 December 2021 (UTC)

I'm about this pair:

$W_{0}(f)={\tfrac {1}{2}}{\frac {\sin(\pi Lf)}{\pi f(1-L^{2}f^{2})}}$

$W_{0}(f)={\tfrac {1}{2}}{\frac {\sin(\pi Lf)}{\pi f}}+{\tfrac {1}{4}}{\frac {\sin(\pi L(f-1/L))}{\pi (f-1/L)}}+{\tfrac {1}{4}}{\frac {\sin(\pi L(f+1/L))}{\pi (f+1/L)}}.$

they are far not equivalent to each other --Lexey73 (talk) 16:56, 28 December 2021 (UTC)

Nuttal - Window - Text shortened

For some reason, the test "Nuttal" is shortend in the image's headline. The "N" is not visible. The graphic will have to be changed, i think. 85.190.194.180 (talk) 14:36, 3 February 2022 (UTC)

Thanks. But you're only looking at a "thumb" representation of the actual figure. Thumbs are just approximations. To see the actual, click on the thumb and then click on the Original file link.

--Bob K (talk) 22:52, 3 February 2022 (UTC)

Nulls on chart are wrong

See the WikiCommons discussion: https://commons.wikimedia.org/wiki/File_talk:Window_functions_in_the_frequency_domain.png — Preceding unsigned comment added by 92.40.200.3 (talk) 12:55, 29 April 2022 (UTC)

I replaced the figure with a better one. --Bob K (talk) 13:04, 1 May 2022 (UTC)