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
We recently ran into issue #200 for the 4-shank probe, that was fixed by either downgrading to 0.2.16 or using the dev version (i.e. this is broken in 0.2.17). I would suggest a release is made ASAP to make sure the pip-installable version does not have this bug, as it is a little subtle and users might not immediately realise.
I saw a note on the testing in #205, could the asserts be changed to check exactly against hard-coded positions as specified in the .meta file? This would be a little time consuming to extract these for each metadata file in the test suite but would pay off going forward, happy to help with this!
The text was updated successfully, but these errors were encountered:
Hi All,
We recently ran into issue #200 for the 4-shank probe, that was fixed by either downgrading to
0.2.16
or using the dev version (i.e. this is broken in0.2.17
). I would suggest a release is made ASAP to make sure the pip-installable version does not have this bug, as it is a little subtle and users might not immediately realise.I saw a note on the testing in #205, could the asserts be changed to check exactly against hard-coded positions as specified in the
.meta
file? This would be a little time consuming to extract these for each metadata file in the test suite but would pay off going forward, happy to help with this!The text was updated successfully, but these errors were encountered: