Skip to content

[Feedback] Consider stopping CaDecon based on changes to deconvolved output #132

@daharoni

Description

@daharoni

Feedback

In many cases, CaDecon more-or-less reaches a solution pretty quickly, within 5 or so iterations, but then keeps going because in each iteration the kernel shape varies enough to not satisfy our convergence criteria. We could always just decrease the strickness of the convergence but we might also want to look into using the change of the deconvolved output as what needs to converge.

Additional Context

In some cases, because we let the system keep going, it can end up finding a less optimal solution

Image

No response

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