Closed gfetterman closed 3 years ago
Several faults were overlapping in this issue, confusing things.
RuntimeError
arose from the problem mentioned in #64 and resolved in #65 . The fixes in #65 also resolved this dat-segment
error; it no longer occurs under python 3.7 or python 3.8 (regardless of numpy or scipy version).DeprecationWarning
mentioned under python 3.6 arose from a bug in scipy versions prior to 1.2 interacting with changes to numpy indexing behavior sometime around numpy 1.15 or so. It can be resolved simply by upgrading scipy to 1.2+.Thus, the problems described in this issue have been resolved.
(Disregard issue renamings just prior.)
Offending command (run on a
.dat
file generated from an ARF file, normal in every respect):$ dat-segment -o test.csv -t 5 --timedomain pcm_000.dat
Stack trace:
This behavior occurs under both Windows and Linux. The above environment includes:
python=3.7
scipy=1.1.0
numpy=1.15.0
This behavior does not occur when Python 3.6 is used (with Numpy and Scipy versions identical to the above); however, the following deprecation warning is emitted (and so I suspect they're related):
c:\miniconda3\envs\bark-test-py36\lib\site-packages\scipy\signal\_arraytools.py:45: FutureWarning: Using a non-tuple sequence for multidimensional indexing is deprecated; use 'arr[tuple(seq)]' instead of 'arr[seq]'. In the future this will be interpreted as an array index, 'arr[np.array(seq)]', which will result either in an error or a different result. b = a[a_slice]
I think this is an easy fix, and will try to get to it soon; until then, use Python <= 3.6