Currently training is tightly coupled to the WindowDataset abstraction.
A clear drawback of this is that it prevents us from training in any other way, e.g. feeding in an entire vocalization (e.g. a birdsong bout) as one sample in a batch.
It's also the case that the logic wrapped up in this function is super hard to read, there's a lot of array-oriented programming that can lead to subtle errors, see for example #169 #213 #217 #219 #220
So this issue formalizes the idea of deprecating WindowDataset.
Instead each sample in a dataset will now be one vocalization, however it is defined for that particular dataset. Typically this will map to one audio file or one spectrogram, e.g. for birdsong one bout of song. In other words, one row from a dataframe representing a dataset, as produced by vocles,
Currently training is tightly coupled to the
WindowDatasetabstraction.A clear drawback of this is that it prevents us from training in any other way, e.g. feeding in an entire vocalization (e.g. a birdsong bout) as one sample in a batch.
It's also the case that the logic wrapped up in this function is super hard to read, there's a lot of array-oriented programming that can lead to subtle errors, see for example #169 #213 #217 #219 #220
So this issue formalizes the idea of deprecating
WindowDataset.Instead each sample in a dataset will now be one vocalization, however it is defined for that particular dataset. Typically this will map to one audio file or one spectrogram, e.g. for birdsong one bout of song. In other words, one row from a dataframe representing a dataset, as produced by
vocles,