Last modified by puchades on 2021/12/07 10:37
From version 19.1
edited by evanhancock
on 2020/07/21 09:40
Change comment: There is no comment for this version
To version 15.1
edited by sharoncy
on 2020/03/28 14:06
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -2. Image pre-processing with Nutil Transform
1 +2. Image preparation with Nutil Transform
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.evanhancock
1 +XWiki.sharoncy
Content
... ... @@ -1,15 +1,16 @@
1 -**The //Transform// feature in the //Nutil// software **enables **image rotation, renaming, resizing and mirroring,** and is used to prepare image series for atlas alignment with QuickNII and segmentation with ilastik. It should be noted that QuickNII and ilastik have different input image size requirements. In addition, it is important that the input images follow the standard naming convention described below.
1 +== (% style="color:#c0392b" %)Image pre-processing with Nutil Transform(%%) ==
2 2  
3 ->(% style="color:#27ae60" %)The //QuickNII// and //ilastik// software have different input image size requirements. It is also important that the input images follow the prescribed naming convention.
4 4  
5 -== (% style="color:#c0392b" %)Input requirements(%%) ==
4 +**The //Transform// feature in the //Nutil// software **enables **image rotation, renaming, resizing and mirroring** and is used to prepare the images in the series for //QuickNII //alignment and //ilastik //segmentation.
6 6  
7 -For //QuickNII,// the input requirements are described in details in Puchades et al., 2019. To summarise, images should be in 24-bit PNG or JPEG format, with a resolution up to 16 megapixels (e.g. 4000x4000 or 5000x3000 pixels). Keep in mind that QuickNII does not benefit from image resolutions exceeding the resolution of the monitor in use. For a standard FullHD or widescreen display (1920x1080 or 1920x1200 pixels) the useful image area in QuickNII is approximately 1500x1000 pixels. Using a similar resolution ensures optimal image-loading performance.
6 +>(% style="color:#27ae60" %)The //QuickNII// and //ilastik// software have different input image size requirements. It is also important that the input images follow the prescribed naming convention.
8 8  
9 -For //ilastik// (Borg et al.2019), images are downscaled in order to enable efficient processing. The pixel classification algorithm relies on input from manual user annotations of the training images, and the features ‒ intensity, edge and/or texture ‒ of the image pixels. The resizing factor is determined by trial and error, with a test run performed with //ilastik// on images of different sizes to determine the optimal resolution for segmentation. As an example, in Yates et al., 2019, the images were downscaled by a factor of 10 for cellular features, and a factor of 20 for Alzheimer's plaques with respect to image width.
8 +For //QuickNII,// the input requirements are described in in Puchades et al., 2019. To summarise, images should be in 24-bit PNG or JPEG format, and can be loaded up to a resolution of 16 megapixels (e.g.4000x4000 or 5000x3000 pixels). However //QuickNII// does not benefit from image resolutions exceeding the resolution of the monitor in use. For a standard FullHD or WUXGA display (1920x1080 or 1920x1200 pixels) the useful image area is approximately 1500x1000 pixels. Using a similar resolution ensures optimal image-loading performance.
10 10  
11 -== (% style="color:#c0392b" %)Naming convention(%%) ==
10 +For //ilastik// (Borg et al.2019) images are downscaled in order to enable efficient processing. The pixel classification algorithm relies on input from manual user annotations of the training images, and the features ‒ intensity, edge and/or texture ‒ of the image pixels. The resizing factor is determined by trial and error, with a test run performed with //ilastik// on images of different sizes to determine the optimal resolution for segmentation. As an example, in Yates et al., 2019, the images were downscaled by a factor of 0.1 and 0.05 for cellular features and Alzheimer's plaques respectively (factor applies to the image width here).
12 12  
12 +=== (% style="color:#c0392b" %)Naming convention(%%) ===
13 +
13 13  For QUINT analysis, Nutil Quantifier quantifies objects extracted from segmentations and registers them to regions defined by customised atlas maps. To match segmentations and corresponding atlas maps together, Nutil Quantifier relies on a unique ID in the file name of both files.The ID should be unique to the particular brain section and in the format: sXXX.., with XXX.. representing the section number. The section number should reflect the serial order and spacing of the sections (e.g. s002, s006, s010 for every 4^^th^^ section starting with section 2).
14 14  
15 15  Example: tg2345_MMSH_s001_segmentation.png
... ... @@ -17,8 +17,8 @@
17 17  (It is fine to include a string of letters and numbers followed by the unique ID).
18 18  
19 19  
20 -== (% style="color:#c0392b" %)Running the transformation(%%) ==
21 +=== (% style="color:#c0392b" %)Running the transformation(%%) ===
21 21  
22 -Consult the Nutil user manual for the detailed procedure (included in the Nutil package [[available for download here>>https://www.nitrc.org/projects/nutil/]])
23 +Consult the Nutil user manual for detailed procedure (lincluded in the Nutil package available for download at Nitrc.org)
23 23  
24 24  [[image:Figure_2_v3.jpg]]