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
Hello
It's great to see that neuroseries is still updated.
I appreciate the new compatibility with pandas 0.23.
There is just one bug that is still here since the previous version.
In this function :
defin_interval(self, tsd):
""" finds out in which element of the interval set each point in a time series fits. NaNs for those that don't fit a interval :param tsd: the tsd to be binned :return: an array with the interval index labels for each time stamp (NaN) for timestamps not in IntervalSet. """bins=self.values.ravel()
ix=np.array(pd.cut(tsd.index, bins, labels=np.arange(len(bins) -1, dtype=np.int64)))
ix[np.floor(ix/2) *2!=ix] =np.NaNix=np.floor(ix/2)
returnix
Basically, it is solved by changing dtype=np.int64 to dtype=np.float64 when defining ix.
Yet, I am not quite sure why I can run the tests without this being detect as an error.
If it's not quite troublesome, would it be possible to change np.int64 to np.float64 since numpy nan are considered as float?
Thanks
Guillaume
The text was updated successfully, but these errors were encountered:
Hello
It's great to see that neuroseries is still updated.
I appreciate the new compatibility with pandas 0.23.
There is just one bug that is still here since the previous version.
In this function :
The error is
Basically, it is solved by changing dtype=np.int64 to dtype=np.float64 when defining ix.
Yet, I am not quite sure why I can run the tests without this being detect as an error.
If it's not quite troublesome, would it be possible to change np.int64 to np.float64 since numpy nan are considered as float?
Thanks
Guillaume
The text was updated successfully, but these errors were encountered: