Skip to content

Values of the deconvolved trace in GUI vs in the spks.npy trace #1196

@harshidapancholi

Description

@harshidapancholi

Hello,

I have observed that the spks.npy values are scaled down from what I see in the GUI. For example, at a specific frame, the GUI shows a value of ~450, whereas the .npy file when loaded using Spyder shows a value of ~150. Is there a scaling factor somewhere of which I am unaware? How does that effect my interpretation of data? I work with very noisy (low res, sparse labeling) 2P imaging data.

Best,
Harshida

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