Skip to content

Comments

60 stack scans cannot be analyzed during scanning saving stack images into additional tiff images could solve this issue#61

Merged
RussBerg merged 23 commits intomasterfrom
60-stack-scans-cannot-be-analyzed-during-scanning-saving-stack-images-into-additional-tiff-images-could-solve-this-issue
Jan 26, 2026
Merged

60 stack scans cannot be analyzed during scanning saving stack images into additional tiff images could solve this issue#61
RussBerg merged 23 commits intomasterfrom
60-stack-scans-cannot-be-analyzed-during-scanning-saving-stack-images-into-additional-tiff-images-could-solve-this-issue

Conversation

@RussBerg
Copy link
Collaborator

Epics/Pixelator

  • progress of scan coming from scan seq map no more calculating
  • fixed issue where ContactSheet would load data just acquired into current scene instead of correct dir named scene

Epics only

  • for nx_server added generation of a stack data file saved in stack directory that in the future can be used to start processing the stack as it is being acquired
  • disabled user selectable hardware acceleration scan for Epics E712 sample scans, this will be a future dev
  • SIS3820: added more rigorous checking of status

General

  • numerous small fixes

@RussBerg RussBerg merged commit 7232f93 into master Jan 26, 2026
1 check passed
@RussBerg RussBerg deleted the 60-stack-scans-cannot-be-analyzed-during-scanning-saving-stack-images-into-additional-tiff-images-could-solve-this-issue branch February 9, 2026 15:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Stack scans cannot be analyzed during scanning. Saving stack images into additional TIFF images could solve this issue.

1 participant