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're currently saving data in uint16 files because that's the native output from Intan chips. I assume this goes for many ADCs. Would it make sense to you guys to add an option to switch preprocessDataSub from assuming int16 to a uint16 with a (2^16)/2 offset? Looks to me like that would be a very easy addition?
We could of course patch our copy of kilosort, or (as we do now) just convert our files separately, but that seems messier than having a config flag for these cases.
The text was updated successfully, but these errors were encountered:
We're currently saving data in uint16 files because that's the native output from Intan chips. I assume this goes for many ADCs. Would it make sense to you guys to add an option to switch preprocessDataSub from assuming int16 to a uint16 with a (2^16)/2 offset? Looks to me like that would be a very easy addition?
We could of course patch our copy of kilosort, or (as we do now) just convert our files separately, but that seems messier than having a config flag for these cases.
The text was updated successfully, but these errors were encountered: