naming style and standardize names and variable
- When applicable, change variable names to confirm with snake_case naming convention. For example, in the Spectrogram module, someone not familiar with the code can read flow as literally the word flow, instead of f_low, or thigh instead of t_high. But it is not applicable everywhere, for example lets use df instead of d_f.
- Standardize some methods and names throughout the code. For example:
- In the MagSpectrogram class, we have a method called from_wav that has a decibel=True argument as default. However the class constructor has a decibel=False as default, resulting in two different spectrograms if the user is not careful, and it is not immediately obvious. (Also, is the from_wav method even needed? seems like it does the same thing as the class constructor).
- In the same MagSpectrogram class and from_wav method, we have arguments called winlen and winstep in the constructor and window_size and step_size in the method.
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information