Skip to content

motion correction and noise threshold calculations #4367

@ryan-budde

Description

@ryan-budde

I've shared a long thread of my motion correction results on the NPX discord

https://discord.com/channels/1446542289114763284/1468690639867740161

I've uploaded my powerpoint as a pdf here

In short I have three issues:

  1. I'm getting consistently poor motion correction results on what I believe to be a not-very-challenging input file
  2. For a 3 minute segment of data, the motion estimate changes, sometimes drastically, depending if the input is a 3 minute file or a 10 minute file. Small changes would make sense with how the motion vector is made-median, or potentially some causality effects, but some of these feels far outside what is reasonable.
  3. For the different data segments, the number of peaks used in motion correction appears very different. This is very likely due to different calculations of the MAD in the noise levels, which sets the peak thresholds for various methods. In my results the noise levels vector varies, but in the longer file values are sometimes as much as 20% higher than the shorter file. Still, this does not feel like the whole story.
  4. This feels separate, but is possibly related. My detection of bad channels seems inaccurate. In both probes numerous seemingly-good channels are called dead, and in one probe the 191 reference channel is not labeled dead.

winter_2026_short.pdf

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions