Summary

• Page properties (1 modified, 0 added, 0 removed)
• Attachments (0 modified, 1 added, 0 removed)
  • Figure_2_v3.jpg

Details

Page properties

Content

...	...	@@ -11,7 +11,7 @@
11	11
12	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	13
14		-== Naming convention: ==
	14	+=== Naming convention: ===
15	15
16	16	The file names of the segmentation and atlas maps that correspond to a particular section must contain a unique ID 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).
17	17
...	...	@@ -21,24 +21,6 @@
21	21
22	22	For running the QUINT analysis the segmentation files and the customized atlas maps need to match and therefore the segmentation files should follow the same naming format.
23	23
24		-=== ===
	24	+=== Running the transformation ===
25	25
26		-==== ====
27		-
28		-[[image:Collaboratory.Apps.Article.Code.ArticleSheet@placeholder.jpg]]
29		-
30		-Photo by David Clode
31		-
32		-==== Or code ====
33		-
34		-Code blocks can be added by using the code macro:
35		-
36		-{{code language="python"}}
37		-x = 1
38		-if x == 1:
39		- # indented four spaces
40		- print("x is 1.")
41		-{{/code}}
42		-
43		-(% class="wikigeneratedid" id="HH4Won27tAppearinToC" %)
44		-
	26	+[[image:Figure_2_v3.jpg]]

Figure_2_v3.jpg

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.puchades

Size

...	...	@@ -1,0 +1,1 @@
	1	+4.4 MB

Content