![]() ![]() The macro is made like this: I use NDPI-tools to extract the 10x data from. So I process all my H-DAB with one macro and all my Masson Trichrome staining with a second macro. If you assume that your image with 8000x8500 only contains much less different color combinations then 16777216 then you can assume that there exists additional strategies to speed up Color Deconvolution without using GPU processing.Īlex.h Usually, I build a macro for one staining. So to pre-calculated the CD values and using them as LUT is beneficial already for a single image. So there exist 256x256x256 color combinations - in total 16777216 combinations.Īn image with 8500x8000 pixels has in total 68000000 pixels. The color deconvolution plugin works with RGB color images with 8bit samples per color channel. This is much faster then processing every pixel of an image and even faster as using a GPU. The background of my question is that when you always use the same color vectors you can pre-calculate the color deconvolution, store it as an image and apply as a lookup table. Or do you use unique color vector for each image? Then I asked some Are you working with build-in color vectors or with your individual but ‘stable’ color vectors? I don’t have any skill in programming… So for the moment I use the macro from Fiji sorry After your NEUBIAS courses I thought to translate the macro in CLIJ I also need to use median filter etc and it take a long time to process the file.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |