Skip to content

Omero-Metrics sometimes finds just one bead and then raises and error trying to create the average. #20

@iandobbie

Description

@iandobbie

We have a dataset that is from a light sheet instrument and it is currently not finding many beads. In these two files it only finds one valid bead and in the web interface raises and error

Opps! something happened
'average_bead'"

And in the omeroweb log file we get nothing of use except that there is only a single valid bead.

``
Image 1002 processed. 0 beads considered valid. 0 beads considered lateral edge. 0 beads considered self proximity. 0 beads considered axial edge. 0 beads considered intensity outlier. 1 beads considered bad fit in z. 0 beads considered bad fit in y. 0 beads considered bad fit in x.
2025-12-16 14:33:58,344 INFO [ microscopemetrics] (proc.63984) analyse_psf_beads():717 Processing image 1004...
2025-12-16 14:34:14,895 INFO [ omero.gateway] (proc.63976) connect():2302 created connection (uuid=1dbc4683-2bdc-484c-8917-3615f5703d15)
2025-12-16 14:34:14,897 INFO [ omero.gateway] (proc.63976) close():2004 closed connection (uuid=None)
2025-12-16 14:34:22,784 INFO [ microscopemetrics] (proc.63984) analyse_psf_beads():737 Image 1004 processed. 1 beads considered valid. 0 beads considered lateral edge. 0 beads considered self proximity. 0 beads considered axial edge. 0 beads considered intensity outlier. 0 beads considered bad fit in z. 0 beads considered bad fit in y. 0 beads considered bad fit in x.

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