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

need clarification about generating roi.tif #36

Open
xuefei-wang opened this issue Dec 24, 2019 · 1 comment
Open

need clarification about generating roi.tif #36

xuefei-wang opened this issue Dec 24, 2019 · 1 comment

Comments

@xuefei-wang
Copy link

Thanks for making the great tool & writing the detailed tutorial!

I am now using it to help count cells. But I have a question about how to generate the roi.tif in Analyze_ROIs.m. This is the process I inferred: first I generate an ROI channel and combine it into the raw tif image as one single file. After the whole process, I will obtain the transformed tif file, then I split the roi channel out of the transformed tif file. This roi channel itself would be roi.tif. Is it correct? If so, I wonder whether there is available scripts to do this? Thank you!

roi_location = 'C:\Drive\Histology\for tutorial - sample data\SS096_1_1_ROIs.tif';

@philshams
Copy link
Collaborator

Yes, that is one way to do it. To merge the ROI channel with histology image, you can either use something like ImageJ or do it in matlab with something like:

multi_channel_image = zeros(dim_1_of_original_image, dim_2_of_original_image, 2);
multi_channel_image(:,:,1) = original_image;
multi_channel_image(:,:,2) = ROI_image;

If you then want to extract the roi image without the histology for analysis, it should be just one line:

roi_location = 'C:\Drive\Histology\for tutorial - sample data\SS096_1_1_ROIs.tif';
roi_location = roi_location(:,:,2)

(here, assuming 2 is the color channel that the ROI data are found on)

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

No branches or pull requests

2 participants