noisyspeech_synthesizer.py fails to run with numpy 1.18.5

[shivasv97]

There seems to be a breaking issue while running the noisyspeech_synthesizer.py while running it on Google Colab.
Colab has numpy 1.18.5 at the time this issue was posted. This version is installed by default when connecting to a runtime.
On following the standard procedure and prerequisites for running this scipt, it gives the following error.

Traceback (most recent call last):
  File "/usr/local/lib/python3.6/dist-packages/numpy/core/function_base.py", line 117, in linspace
    num = operator.index(num)
TypeError: 'float' object cannot be interpreted as an integer

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "./MS-SNSD/noisyspeech_synthesizer.py", line 124, in <module>
    main(cfg._sections[args.cfg_str])
  File "./MS-SNSD/noisyspeech_synthesizer.py", line 47, in main
    SNR = np.linspace(snr_lower, snr_upper, total_snrlevels)
  File "<__array_function__ internals>", line 6, in linspace
  File "/usr/local/lib/python3.6/dist-packages/numpy/core/function_base.py", line 121, in linspace
    .format(type(num)))
TypeError: object of type <class 'float'> cannot be safely interpreted as an integer.

However, when the numpy version is downgraded from 1.18.5 to 1.16.4, the script works perfectly fine as it is supposed to.

[majianjia]

same here

[NisargBhatt73]

The same was the case for me, in line number 47 just typecast every argument to int, that worked for me
like this -

SNR = np.linspace(int(snr_lower), int(snr_upper), int(total_snrlevels))

[jagger2048]

This PR may work for this issue #11

[anand0427]

This bug isn't fixed yet. So anyone working with this follow @NisargBhatt73 suggestion.

[anderzzz]

Still here. But easy fix. Just make lines 13-15 of noisyspeech_synthesizer.py into int. They are only used in for the linspace function

So:

    snr_lower = int(cfg["snr_lower"])
    snr_upper = int(cfg["snr_upper"])
    total_snrlevels = int(cfg["total_snrlevels"])

[majianjia]

There is already a PR for this bug but it seems like this repo is not maintained.
#15

[truc0]

Same problem