Notice: In order to edit this ticket you need to be either: a Product Owner, The owner or the reporter of the ticket, or, in case of a Task not yet assigned, a team_member"

User Story #8599 (closed)

Opened 7 years ago

Closed 6 years ago

Last modified 6 years ago

Integration field for OME-XML

Reported by: crueden-x Owned by: ajpatterson
Priority: minor Milestone: 5.0.0-beta1
Component: Specification Keywords: schema, xsd-2013-1
Cc: eliceiri@… Story Points: n.a.
Sprint: n.a. Importance: n.a.
Total Remaining Time: n.a. Estimated Remaining Time: n.a.

Description (last modified by crueden-x)

The acquisition systems at LOCI have a configurable parameter for "integration" or "averaging" that controls the number of sequential frames that get averages, to improve the signal-to-noise ratio.

This is very similar to the Binning attribute of DetectorSettings, except that it is an average over T rather than over XY.

From the book "Video Microscopy: The Fundamentals" by S. Inoué and K. R. Spring:

"Because noise is random and the signal is not, a running average both reduces the noise contribution and enhances the signal component of the output digital image. ... A running average is a very convenient way to monitor dynamic events under low-light-level conditions, as in studies of fluorescently labeled living cells. Image quality is improved by averaging, with some sacrifice of temporal resolution, but with the benefit of a constant video output that allows one to monitor specimen focus and position."

Thus, I suggest adding an "Integration" attribute to the DetectorSettings element, with type="PositiveInt" and use="optional".

Change History (9)

comment:1 Changed 7 years ago by crueden-x

  • Description modified (diff)

comment:2 Changed 7 years ago by crueden-x

Another useful explanation from "Principles and Practice of Variable Pressure/Environmental Scanning Electron Microscopy" by D. Stokes:

"2.6.8.1 Integration


"Live digital images can be placed in a framestore and then integrated to form a single image. The process of integration smoothes out noise by adding a specified number of successive frames together (2, 4, 8, 16, 32, 64, etc). Constant signal detail is added together, while random fluctuations (noise) tend to cancel out. Integration is usually performed at fast frame rates and/or small beam currents, which is also an excellent way of avoiding artefacts arising from charge accumulation at slow frame rates and/or high beam currents. Note that integration is not useful if either the sample or the beam is drifting, since this causes image blurring.


"2.6.8.2 Averaging


"Also known as a recursive filter, this method increases the signal-to-noise ratio by giving a running average of several frames in real time, with pixels weighted so that the most recent frame contributes the most. Unlike integration, averaging does not stop after a specified number of frames, i.e. it is a continuous, real-time process, which means that contrast and/or brightness can be adjusted in real time."

comment:3 Changed 7 years ago by ajpatterson

  • Keywords schema added

comment:4 Changed 7 years ago by ajpatterson

  • Component changed from Model to Specification

comment:5 Changed 7 years ago by ajpatterson

  • Keywords xsd-2013-1 added

comment:6 Changed 7 years ago by ajpatterson

  • Milestone changed from Unscheduled to OMERO-5

comment:7 Changed 6 years ago by ajpatterson

  • Status changed from new to accepted

comment:8 Changed 6 years ago by ajpatterson

  • Resolution set to fixed
  • Status changed from accepted to closed

comment:9 Changed 6 years ago by Andrew J Patterson <workonly@…>

(In [31173eee6358c0c6ad3631f193d780e482178aa0/ome.git] on branch develop) Adding Integration field, see #8599

Note: See TracTickets for help on using tickets. You may also have a look at Agilo extensions to the ticket.

1.3.13-PRO © 2008-2011 Agilo Software all rights reserved (this page was served in: 0.81780 sec.)

We're Hiring!