Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

3-channel fluorescent images - support for identical autocropping #245

Open
sharoncy opened this issue Mar 7, 2022 · 1 comment
Open
Assignees

Comments

@sharoncy
Copy link
Member

sharoncy commented Mar 7, 2022

This is a request from @UlrikeS91.

Feature: Transform

Problem: She has fluorescent brain section images with 3-channels and used the autocropping feature in Transform to create images for anchoring. Which means that she has three identical series for each brain ( (red, blue and green channel). But because the images look different, the autocropping feature has cropped then differently. She has anchored one of the series and wanted to apply the same anchoring to the other series as they are identical, but this is not possible because the images are not the same size.

Suggestion: So ideally she needs a solution for setting the autocropping based on one of the series and then applying the same autocropping parameters to the other two series. There may be other solutions here.

Scope: This request is relevant for anyone working with 3-channel fluorescent images so may be worthwhile implementing a solution in Nutil.

@UlrikeS91
Copy link

Thanks @sharoncy for raising my issue ☺️ Here an example of what she described:

image

These are the thumbnail pngs (tiffs would look the same of course). As you can see, the dimensions are different for all 3 channels (and the merged image has the dimensions of the largest one - the green channel).

Maybe an easy solution could be to get an output file like the excel template that contains the image dimensions in addition to the rotation and stuff. Then, I would only have to change the file names to the names of the next series and use it as the input for a new Nutil Transform run.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants