CITATION — REFERENCE ENTRY

mir_eval.chord — mir_eval 0.8.2 documentation

Revision a2a528c4-f83d-4be2-a903-a456e46cd9bd · 11/10/2026, 11:56:12 PM UTC
Key
mir-eval-chord-docs
Type
webpage
Container
mir_eval 0.8.2 documentation
Raw CSL JSON
{
  "URL": "https://mir-eval.readthedocs.io/latest/api/chord.html",
  "type": "webpage",
  "title": "mir_eval.chord",
  "accessed": {
    "date-parts": [
      [
        2026,
        11,
        10
      ]
    ]
  },
  "container-title": "mir_eval 0.8.2 documentation"
}

Claims

  1. Under mir_eval's 'mirex' rule, an estimated chord counts as correct if it shares at least three pitch classes with the reference chord.
    "A estimated chord is considered correct if it shares at least three pitch classes in common."
    Locator: section: Metrics · Quote language: en
  2. The mir_eval documentation states that there is no single right way to compare chord label sequences, and provides every conventional comparison rule.
    "There is no single 'right' way to compare two sequences of chord labels. Embracing this reality, every conventional comparison rule is provided."
    Locator: section: Metrics · Quote language: en
  3. Under mir_eval's 'tetrads' rule, chords are compared at the level of their entire quality within one octave, so A:7 and A:9 match but A:7 and A:maj7 do not.
    "For example, ('A:7', 'A:9') are equivalent but ('A:7', 'A:maj7') are not."
    Locator: section: Metrics · Quote language: en
Available in