chandeMomentumOscillator() function

chandeMomentumOscillator() applies the technical momentum indicator developed by Tushar Chande to input data.

The Chande Momentum Oscillator (CMO) indicator does the following:

  1. Determines the median value of the each input table and calculates the difference between the sum of rows with values greater than the median and the sum of rows with values lower than the median.
  2. Divides the result of step 1 by the sum of all data movement over a given time period.
  3. Multiplies the result of step 2 by 100 and returns a value between -100 and +100.

Output tables

For each input table with x rows, chandeMomentumOscillator() outputs a table with x - n rows.

Function type signature
(<-tables: stream[A], n: int, ?columns: [string]) => stream[B] where A: Record, B: Record
For more information, see Function type signatures.



(Required) Period or number of points to use in the calculation.


List of columns to operate on. Default is ["_value"].


Input data. Default is piped-forward data (<-).


Apply the Chande Momentum Oscillator to input data

import "sampledata"
    |> chandeMomentumOscillator(n: 2)

Was this page helpful?

Thank you for your feedback!

Introducing InfluxDB Clustered

A highly available InfluxDB 3.0 cluster on your own infrastructure.

InfluxDB Clustered is a highly available InfluxDB 3.0 cluster built for high write and query workloads on your own infrastructure.

InfluxDB Clustered is currently in limited availability and is only available to a limited group of InfluxData customers. If interested in being part of the limited access group, please contact the InfluxData Sales team.

Learn more
Contact InfluxData Sales

The future of Flux

Flux is going into maintenance mode. You can continue using it as you currently are without any changes to your code.

Flux is going into maintenance mode and will not be supported in InfluxDB 3.0. This was a decision based on the broad demand for SQL and the continued growth and adoption of InfluxQL. We are continuing to support Flux for users in 1.x and 2.x so you can continue using it with no changes to your code. If you are interested in transitioning to InfluxDB 3.0 and want to future-proof your code, we suggest using InfluxQL.

For information about the future of Flux, see the following: