Project

General

Profile

Actions

Feature #4527

closed

Avoid using bad phase plate patches and save which phase plate patch position is used in the image acquired in database

Added by Anchi Cheng about 8 years ago. Updated almost 7 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
-
Start date:
10/16/2016
Due date:
% Done:

0%

Estimated time:
Deliverable:

Description

This can be used to track performance of the phase plate patch as well as whether an advancement or avoidance for recovery is needed.

Actions #1

Updated by Anchi Cheng about 8 years ago

  • Subject changed from save which phase plate patch is used in the image acquired in database to Avoid using bad phase plate patches and save which phase plate patch position is used in the image acquired in database
  • Status changed from Assigned to In Test

a11e4f66 will track the usage.

Require binding PhasePlateUsagePublishEvent from PhasePlateAligner to the Acquisition Node that uses on-plane position.

If the position is to be recorded correctly, PhasePlateAligner "bypass conditioner" has to be deactivated and the current phase plate and patch position number set correctly in PhasePlateAligner node (usually aliased as Phase Plate in MSI applications).

If some of the patches are bad, use toolbar "patch state mapping" to mark bad positions so that they will be skipped when advancing. Note that the initial position is not checked for the state.

Actions #3

Updated by Anchi Cheng almost 7 years ago

  • Status changed from In Test to Closed
Actions

Also available in: Atom PDF