Differences

This shows you the differences between two versions of the page.

--- eyes:logics:boxmanipulation [2017/06/07 17:06]
bgraf
+++ eyes:logics:boxmanipulation [2017/06/12 19:08] (current)
jschlie1
@@ Line 1: / Line 1: @@
-====== Box Manipulation ======
+====== BoxManipulation ======
-THIS position should be used for a brief introduction (max 2 sentences!) of the logic, stating WHAT and WHY it is doing something.
+This logic provides functionalities, to change/enlarge/scale etc. the box of a stack of images.
 ===== Usage =====
-Here, a general/generic description of HOW the logic is USED should be given. Try to be as general as possible, but also mention prerequisites, restrictions, advantages, requirements which are specific of this logic. Basically everything the user needs to know to successfully use this logic.
+The input of this logic will be subjected to the selected process.
-===== Example ====
-Here, a very specific example should be given/described. In the future, this can be supported by screenshots etc.. For the moment, give an example easy enough for the user to understand, but specific enough to elaborate why a given parameter is a good set for this very situation.
 ===== Processes =====
-==== Crop Image ====
+==== Canvas Resize ====
+Resizes images to the side length specified by the input value. This is carried out by either cropping or padding the images, depending on whether the image size is supposed to be reduced or enlarged.
+|< 100% 30% >|
+^ Parameters                 ^ Description     ^
+| New Size (X=Y) | Final image side length in pixel  |
+==== Coarse ====
+Averages images with a certain factor n.
+n x n  pixels are averaged together resulting in a smaller image with respect to the image side length.
+Produces smaller images with higher pixelsize for initial image processing.
+|< 100% 30% >|
+^ Parameters                 ^ Description     ^
+| Value | Number of pixels to be averaged in each direction |
+==== Crop Image ====
 |< 100% 30% >|
 ^ Parameters                 ^ Description     ^
@@ Line 20: / Line 32: @@
 | Right | |
 | Top | |
-==== FFT Resize ====
-|< 100% 30% >|
-^ Parameters                 ^ Description     ^
-| Pad Size | |
-==== Coarse ====
-Averages images with a certain factor n specified by value. n x n pixels are averaged together resulting in a by factor n (with respect to the image side length) smaller image. Generates smaller images with higher pixelsize for initial image processing.
-|< 100% 30% >|
-^ Parameters                 ^ Description     ^
-| Value | Number of pixels to be averaged in each direction |
 ==== Fourier Coarse ====
@@ Line 42: / Line 40: @@
 | Coarse factor | The coarse factor used to calculate the new image size (oldSize / coarseFactor = newSize). |
- **Inputs**
+==== Noise Padding ====
-io:input: Any stack of images in real space, up to 3D
+|< 100% 30% >|
+^ Parameters                 ^ Description     ^
+| Pad Size | |
- **Outputs**
-io:output: Cropped images
 ==== Scale ====
 Scales images by the given value n
@@ Line 58: / Line 53: @@
 | Scale Factor| represents the factor n the input images are scaled with |
-**Written Header Values**
+|< 100% 30% >|
-  * **pixelSize:** Pixel size after scaling
+^ Written Header Values                 ^ Description     ^
+| pixelSize | Pixel size after scaling |
-==== Canvas Resize ====
-Resizes images to the side length specified by the input value. This is carried out by either cropping or padding the images, depending on whether the image size is supposed to be reduced or enlarged.
+==== Zero Padding ====
 |< 100% 30% >|
 ^ Parameters                 ^ Description     ^
-| New Size (X=Y) | Final image side length in pixel  |
+| Padding Factor | |
-=== Example Usage ===
-Changing image size without changing the magnification (or Angstrom/pixel ratio)
-===== Concept =====
-In this paragraph, the "HOW a logic works under the hood" and WHY someone should use it can be elaborated with higher detail. Describes a scenario in an image processing workflow where this logic can be used to solve the resulting problem. Also, wikipages, publications or anything else describing the theory behind an algorithm should be linked here, if applicable.