DZone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Newsletter
Log In / Join
Refcards Trend Reports
Events Video Library
Refcards
Trend Reports

Events

View Events Video Library

Related

  • Moving 900+ GB of Prometheus Without a Cutover Weekend
  • Building High-Performance Time-Series Applications With Java and QuestDB
  • Why Time Series Databases Matter for Modern Enterprise Applications
  • From 30s to 200ms: Optimizing Multidimensional Time Series Analysis at Scale

Trending

  • Your Event Storming Is Not Your Software Design
  • Data Integration Landscape 2026: Event Streaming, API, and Batch in the Era of Agentic AI
  • Claude Code Superpowers: The 5-Tool Stack That Ends Limits and Context Amnesia
  • AI-Powered CI Test Failure Triage

Draft This article hasn't been published, so readers can't see it.

In moderation This article is waiting for review, so readers can't see it yet.

Deleted This article has been deleted, so readers can't see it.

  1. DZone
  2. Data Engineering
  3. Databases
  4. Time Series Analysis vs. DSP Terminology

Time Series Analysis vs. DSP Terminology

Digital signal processing and time series analysis are very similar — but the terminology that they use is very different. This article is here to clarify the confusion.

By 
John Cook
·
Oct. 26, 17 · Opinion
Post on X (opens in a new tab) Share on LinkedIn (opens in a new tab)
5.2K Views

Join the DZone community Save articles, join the discussion, and download Refcards and Trend Reports with a free account.

Join for free Already a member? Log in

Time series analysis and digital signal processing are closely related. Unfortunately, the two fields use different terms to refer to the same things.

Suppose you have a sequence of inputs x[n] and a sequence of outputs y[n] for integers n.

Moving Average/FIR

If each output depends on a linear combination of a finite number of previous inputs:

Image title

...then time series analysis would call this a moving average (MA) model of order q, provided b0 = 1. Note that this might not really be an average, i.e. the bs are not necessarily positive and don't necessarily sum to 1.

Digital signal processing would call this a finite impulse response (FIR) filter of order q.

Autoregressive/IIR

If each output depends on a linear combination of a finite number of previous outputs:

Image title

...then time series analysis would call this an autoregressive (AR) model of order p.

Digital signal processing would call this an infinite impulse response (IIR) filter of order p.

Sometimes, you'll see the opposite sign convention on the as.

ARMA/IIR

If each output depends on a linear combination of a finite number of previous inputs and outputs:

Image title

...then time series analysis would call this an autoregressive moving average (ARMA) model of order (p, q), i.e. p AR terms and q MA terms.

Digital signal processing would call this an infinite impulse response (IIR) filter with q feedforward coefficients and p feedback coefficients. Also, as above, you may see the opposite sign convention on the as.

ARMA Notation

Box and Jenkins use as for input and zs for output. We'll stick with xs and ys to make the comparison to DSP easier.

Using the backward shift operator B that takes a sample at n to the sample at n-1, the ARMA system can be written as:

Image title

...where φ and θ are polynomials, and:

Image title

System Function Notation

In DSP, filters are described by their system function, the z-transform of the impulse response. In this notation (as in Oppenheim and Shafer, for example), we have:

Related

  • DSP and time series consulting
Time series

Published at DZone with permission of John Cook. See the original article here.

Opinions expressed by DZone contributors are their own.

Related

  • Moving 900+ GB of Prometheus Without a Cutover Weekend
  • Building High-Performance Time-Series Applications With Java and QuestDB
  • Why Time Series Databases Matter for Modern Enterprise Applications
  • From 30s to 200ms: Optimizing Multidimensional Time Series Analysis at Scale

Partner Resources

×

Comments

Loading comments

The comments didn't load

Please try again in a moment.

Likes

Loading

The next likes didn't load. Please try again.

The likes didn't load

Please try again in a moment.

See who liked this

Log in or join DZone for free to see who liked this article.

Log in Join for free
  • RSS
  • X
  • Facebook

ABOUT US

  • About DZone
  • Support and feedback
  • Community research

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • Become a Contributor
  • Core Program
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 3343 Perimeter Hill Drive
  • Suite 215
  • Nashville, TN 37211
  • [email protected]

Let's be friends:

  • RSS
  • X
  • Facebook