Added definitions of Mazurka fold/splits.

hendriks73 · Oct 14, 2020 · 1ccd7c3 · 1ccd7c3
1 parent cd56a42
commit 1ccd7c3
Show file tree

Hide file tree

Showing 2 changed files with 14 additions and 1 deletion.
diff --git a/README.rst b/README.rst
@@ -116,6 +116,19 @@ Note that Mazurka models may be used to estimate a global tempo, but were
 actually trained to create tempograms (local tempo, see below) for Chopin
 Mazurkas [4]_.
 
+While it's cumbersome to list the split definitions for the Version folds,
+the Mazurka folds are easily defined:
+
+- ``fold0`` was tested on ``Chopin_Op068No3`` and validated on ``Chopin_Op017No4``
+- ``fold1`` was tested on ``Chopin_Op017No4`` and validated on ``Chopin_Op024No2``
+- ``fold2`` was tested on ``Chopin_Op024No2`` and validated on ``Chopin_Op030No2``
+- ``fold3`` was tested on ``Chopin_Op030No2`` and validated on ``Chopin_Op063No3``
+- ``fold4`` was tested on ``Chopin_Op063No3`` and validated on ``Chopin_Op068No3``
+
+The networks were trained on recordings of the three remaining Mazurkas.
+In essence this means, DO NOT estimate the local tempo for ``Chopin_Op024No2`` using
+``dt_maz_m_fold0``, because `Chopin_Op024No2`` was used in training.
+
 Batch Processing
 ================
 

diff --git a/tempocnn/version.py b/tempocnn/version.py
@@ -1 +1 @@
-__version__ = "0.0.5.dev1"
+__version__ = "0.0.5.dev2"