You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With Numpy v1.12.1, I get float object cannot be interpreted as interger type error for np.ones() function calls in Pypsy -> signal -> analysis.py (line 193). There may be other such calls as well, I hit this one.
With Numpy v1.11.1, there was a VisibleDeprecationWarning with this.
The text was updated successfully, but these errors were encountered:
This issue is still present. Tried to resolve it with casting the winwidth2 variable in the bateman_gauss function as an integer. This resolves the issue of the error but my results are slightly off from what is shown in the tutorial.
I really wish I had time to address this...it's long overdue. My life just hasn't let me have the time to do so, though. It's on my list, but if someone wants to send over a PR, I'll gladly accept it.
With Numpy v1.12.1, I get
float object cannot be interpreted as interger
type error fornp.ones()
function calls in Pypsy -> signal -> analysis.py (line 193). There may be other such calls as well, I hit this one.With Numpy v1.11.1, there was a
VisibleDeprecationWarning
with this.The text was updated successfully, but these errors were encountered: