I found it took me a while to understand the inner workings of markov.py. Building a complete model of the data should not rely on calling markov.generatemelody() in order to trigger markov.slice()'s side effects. It would also help comprehension of the code in future iterations to have sequential components of generated melodies represented as objects with their own methods and properties.
I found it took me a while to understand the inner workings of markov.py. Building a complete model of the data should not rely on calling markov.generatemelody() in order to trigger markov.slice()'s side effects. It would also help comprehension of the code in future iterations to have sequential components of generated melodies represented as objects with their own methods and properties.