Wiki source code of 2. Image preparation with Nutil
Show last authors
author | version | line-number | content |
---|---|---|---|
1 | == Image pre-processing with Nutil Transform == | ||
2 | |||
3 | |||
4 | **The //Transform// feature in the //Nutil// software **enables **image rotation, renaming, resizing and mirroring** and was used to prepare the image series for //QuickNII //alignment and //ilastik //segmentation. | ||
5 | |||
6 | >The input size requirements for the //QuickNII// and //ilastik// software differ. Naming convention of files is important. | ||
7 | |||
8 | For //QuickNII,// the input requirements described in (Puchades et al., 2019) are: | ||
9 | 24-bit PNG and JPEG. Images can be loaded up to the 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 | ||
10 | (1920x1080 or 1920x1200 pixels) the useful image area is approximately 1500x1000 pixels,using a similar resolution ensures optimal image-loading performance. | ||
11 | |||
12 | For //ilastik// (Borg et al.2019), the resizing was performed in order to enable efficient processing. To clarify, the pixel classification algorithm relies on input from manual user annotations of training images, and the features ‒ intensity, edge and/or texture ‒ of the image pixels. In practice, a test run was performed with //ilastik// on images of different sizes to find the optimal resolution for segmentation, with a final resize factor of e.g 0.1 for cellular features, and a factor of 0.05 for series with larger features like Alzheimer plaques. | ||
13 | |||
14 | ==== **Naming convention:** ==== | ||
15 | |||
16 | For //QuickNII, //the// //serial section images should be assigned consecutive serial numbers, preferably indicated by three-digit numbers at the end of the file name, e.g. Sample_ID_s001.tif. Section sampling is given by the serial numbers. | ||
17 | |||
18 | For running the QUINT analysis the Segmentation files and the customized atlas maps need to match and therefore | ||
19 | |||
20 | === H3 Headings Will Appear In The Table of Content === | ||
21 | |||
22 | ==== You can also add images ==== | ||
23 | |||
24 | [[image:Collaboratory.Apps.Article.Code.ArticleSheet@placeholder.jpg]] | ||
25 | |||
26 | Photo by David Clode | ||
27 | |||
28 | ==== Or code ==== | ||
29 | |||
30 | Code blocks can be added by using the code macro: | ||
31 | |||
32 | {{code language="python"}} | ||
33 | x = 1 | ||
34 | if x == 1: | ||
35 | # indented four spaces | ||
36 | print("x is 1.") | ||
37 | {{/code}} | ||
38 | |||
39 | (% class="wikigeneratedid" id="HH4Won27tAppearinToC" %) | ||
40 |