Skip to content

Mishandling of missing buscar shuffled scores #69

@axiomcura

Description

@axiomcura
Image

We found a bug here #64 (comment)

The issue is that the shuffled scores can sometimes return None when the process fails—specifically when no clusters or on/off signatures can be identified. This behavior arises directly from how the shuffling is implemented.

The shuffling occurs before calculating the Buscar scores per treatment, which means the first point of failure is in the construction of the on/off signatures. In many cases, all features end up in the “off-morphological” signature, which is makes sense after shuffling.

Occasionally, by chance, one or two features may appear significant, producing a valid score, but these are effectively random and result in unstable or misleading values.

When examining the scores, we also noticed that the shuffled scores are systematically much lower. Since this process runs over 10 iterations, there is a high chance that 0.0 values outnumber actual computed shuffled scores. As a result, the 0.0s become dominant and drive the average downward, making the mean score much lower than the true underlying value.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Important!!These are issues that should be prioritized

    Type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions