Skip to content

Sample level alerts should provide details that can be traced to specific samples #504

@georgebzheng

Description

@georgebzheng

I had the chance 0n 5/28/2020 to scan through all the JUnit files from previous runs of TASBE on SD2 experiments without the replicate group information and have compiled the following sample level alerts (classname, name) that have shown up:

TASBE:ReadFCS,TooMuchDataDiscarded
TASBE:WeightedMean,ZeroWeights
TASBE:ReadFCS,UnusuallySmallFile
TASBE:Analysis,HighGatingVariation
TASBE:Analysis,HighConditionSizeVariation
TASBE:Analysis,SaturationDetected
TASBE:ReadFCS,MajorityNegativeData

In some cases, condition is provided and in others, file name is provided. To uniquely identify samples they are associated with, it would be great if you can always provide file name so I can map each to the corresponding sample, even when TASBE is run with replicate group info.

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