Projects:RegistrationImprovement:RecursiveScheme - Revision history

Meier at 13:54, 23 October 2009

2009-10-23T13:54:50Z

Meier at 13:54, 23 October 2009

2009-10-23T13:54:19Z

Meier at 18:22, 22 September 2009

2009-09-22T18:22:18Z

Meier at 18:20, 22 September 2009

2009-09-22T18:20:49Z

Meier at 18:16, 22 September 2009

2009-09-22T18:16:00Z

Meier at 16:40, 22 September 2009

2009-09-22T16:40:21Z

Meier at 16:36, 22 September 2009

2009-09-22T16:36:13Z

Meier at 16:34, 22 September 2009

2009-09-22T16:34:48Z

Meier at 16:31, 22 September 2009

2009-09-22T16:31:07Z

Meier at 16:29, 22 September 2009

2009-09-22T16:29:16Z

@@ Line 1: / Line 1: @@
 back to [[Projects:RegistrationImprovement]]
 Both multi-resolution and the sequence of calls with increasing DOF could be implemented as a single recursive scheme. The caller provides an array of DOF and a matching array of resolution levels, which is processed by recursive calls with the first/last element taken from the list.
 This would avoid multiple instances of pipelines to anticipate all the combinations that may occur. While it is safe to assume that noone will call a lower DOF alignment after having run a higher one, skipping lower DOF initializations does commonly occur, e.g. when a previous alignment has been obtained elsewhere or in other runs.
-This should also allow a single GUI for all instances. We can list the many combination as a single list of checkboxes for increasing DOF. The checked boxes then provide the input string for the recursive call. Example mockup shown here: [[Image:DOFHierarchy_GUI.jpg‎|right]]
+This should also allow a single GUI for all instances. We can list the many combination as a single list of checkboxes for increasing DOF. The checked boxes then provide the input string for the recursive call. Example mockup shown here:
 Presets as discussed can still be used and individual GUI widgets hidden or disabled. For example an "affine robust" would use [6,9,12] DOF sequence with higher associated multi-resolution settings, whereas an "affine direct" would have only [12] in the sequence.

@@ Line 5: / Line 5: @@
 This would avoid multiple instances of pipelines to anticipate all the combinations that may occur. While it is safe to assume that noone will call a lower DOF alignment after having run a higher one, skipping lower DOF initializations does commonly occur, e.g. when a previous alignment has been obtained elsewhere or in other runs.
-This should also allow a single GUI for all instances. We can list the many combination as a single list of checkboxes for increasing DOF. The checked boxes then provide the input string for the recursive call. Example mockup shown here: [[Media:DOFHierarchy_GUI.jpg‎ ]]
+This should also allow a single GUI for all instances. We can list the many combination as a single list of checkboxes for increasing DOF. The checked boxes then provide the input string for the recursive call. Example mockup shown here: [[Image:DOFHierarchy_GUI.jpg‎|right]]
 Presets as discussed can still be used and individual GUI widgets hidden or disabled. For example an "affine robust" would use [6,9,12] DOF sequence with higher associated multi-resolution settings, whereas an "affine direct" would have only [12] in the sequence.

@@ Line 9: / Line 9: @@
 Presets as discussed can still be used and individual GUI widgets hidden or disabled. For example an "affine robust" would use [6,9,12] DOF sequence with higher associated multi-resolution settings, whereas an "affine direct" would have only [12] in the sequence.
-*A simulation Matlab program and example is here: [[Media:DOFHierarchy.m]]
+*A Matlab program simulating the recursive scheme is here: [[Media:DOFHierarchy.m]]
 *Example call: the '''256''' symbolizes the image data size,''' [6,9,12]''' is the sequence of DOF, '''NoInit''' is the initial transform (if avail), and '''[4,3,2]''' are the multi-resolution levels for each of the DOF runs, respectively.
    a = DOFHierarchy(256, [6,9,12],'NoInit',[4,3,2],0)

← Older revision		Revision as of 18:20, 22 September 2009
Line 5:		Line 5:
	This would avoid multiple instances of pipelines to anticipate all the combinations that may occur. While it is safe to assume that noone will call a lower DOF alignment after having run a higher one, skipping lower DOF initializations does commonly occur, e.g. when a previous alignment has been obtained elsewhere or in other runs.		This would avoid multiple instances of pipelines to anticipate all the combinations that may occur. While it is safe to assume that noone will call a lower DOF alignment after having run a higher one, skipping lower DOF initializations does commonly occur, e.g. when a previous alignment has been obtained elsewhere or in other runs.

		+	This should also allow a single GUI for all instances. We can list the many combination as a single list of checkboxes for increasing DOF. The checked boxes then provide the input string for the recursive call. Example mockup shown here: [[Media:DOFHierarchy_GUI.jpg‎ ]]
		+
		+	Presets as discussed can still be used and individual GUI widgets hidden or disabled. For example an "affine robust" would use [6,9,12] DOF sequence with higher associated multi-resolution settings, whereas an "affine direct" would have only [12] in the sequence.

	*A simulation Matlab program and example is here: [[Media:DOFHierarchy.m]]		*A simulation Matlab program and example is here: [[Media:DOFHierarchy.m]]

@@ Line 2: / Line 2: @@
 Both multi-resolution and the sequence of calls with increasing DOF could be implemented as a single recursive scheme. The caller provides an array of DOF and a matching array of resolution levels, which is processed by recursive calls with the first/last element taken from the list.
 *A simulation Matlab program and example is here: [[Media:DOFHierarchy.m]]
 *Example call: the '''256''' symbolizes the image data size,''' [6,9,12]''' is the sequence of DOF, '''NoInit''' is the initial transform (if avail), and '''[4,3,2]''' are the multi-resolution levels for each of the DOF runs, respectively.

← Older revision		Revision as of 16:40, 22 September 2009
Line 1:		Line 1:
		+	back to [[Projects:RegistrationImprovement]]
		+
	Both multi-resolution and the sequence of calls with increasing DOF could be implemented as a single recursive scheme. The caller provides an array of DOF and a matching array of resolution levels, which is processed by recursive calls with the first/last element taken from the list.		Both multi-resolution and the sequence of calls with increasing DOF could be implemented as a single recursive scheme. The caller provides an array of DOF and a matching array of resolution levels, which is processed by recursive calls with the first/last element taken from the list.
	*A simulation Matlab program and example is here: [[Media:DOFHierarchy.m]]		*A simulation Matlab program and example is here: [[Media:DOFHierarchy.m]]

@@ Line 20: / Line 20: @@
 * Same example call with verbose flag set, showing the function calls:
    a = DOFHierarchy(256, [6,9,12],'NoInit',[4,3,2],1)
-   	 RunAlignment(256, 6,NoInit,4)
+   	 >>RunAlignment(256, 6,NoInit,4)
    		input data size 256. smooth & subsample
-   	 RunAlignment(128, 6,NoInit,3)
+   	 >>RunAlignment(128, 6,NoInit,3)
    		input data size 128. smooth & subsample
-   	 RunAlignment(64, 6,NoInit,2)
+   	 >>RunAlignment(64, 6,NoInit,2)
    		input data size 64. smooth & subsample
-   	 RunAlignment(32, 6,NoInit,1)
+   	 >>RunAlignment(32, 6,NoInit,1)
    	 running registration for 32 image at 6 DOF with init NoInit
    	 running registration for 64 image at 6 DOF with init result from 6 DOF run @ 32
@@ Line 32: / Line 32: @@
    	 running registration for 256 image at 6 DOF with init result from 6 DOF run @ 128
    DOFHierarchy (256 , [6,9,12,], NoInit )
-   	 RunAlignment(256, 9,result from 6 DOF run @ 256,3)
+   	 >>RunAlignment(256, 9,result from 6 DOF run @ 256,3)
    		input data size 256. smooth & subsample
-   	 RunAlignment(128, 9,result from 6 DOF run @ 256,2)
+   	 >>RunAlignment(128, 9,result from 6 DOF run @ 256,2)
    		input data size 128. smooth & subsample
-   	 RunAlignment(64, 9,result from 6 DOF run @ 256,1)
+   	 >>RunAlignment(64, 9,result from 6 DOF run @ 256,1)
    	 running registration for 64 image at 9 DOF with init result from 6 DOF run @ 256
    	 running registration for 128 image at 9 DOF with init result from 9 DOF run @ 64
    	 running registration for 256 image at 9 DOF with init result from 9 DOF run @ 128
-   DOFHierarchy (256 , [9,12,], result from 6 DOF run @ 256 )
+   >>DOFHierarchy (256 , [9,12,], result from 6 DOF run @ 256 )
-   	 RunAlignment(256, 12,result from 9 DOF run @ 256,2)
+   	 >>RunAlignment(256, 12,result from 9 DOF run @ 256,2)
    		input data size 256. smooth & subsample
-   	 RunAlignment(128, 12,result from 9 DOF run @ 256,1)
+   	 >>RunAlignment(128, 12,result from 9 DOF run @ 256,1)
    	 running registration for 128 image at 12 DOF with init result from 9 DOF run @ 256
    	 running registration for 256 image at 12 DOF with init result from 12 DOF run @ 128
     a =result from 12 DOF run @ 256

← Older revision		Revision as of 16:31, 22 September 2009
Line 15:		Line 15:
	running registration for 128 image at 12 DOF with init result from 9 DOF run @ 256		running registration for 128 image at 12 DOF with init result from 9 DOF run @ 256
	running registration for 256 image at 12 DOF with init result from 12 DOF run @ 128		running registration for 256 image at 12 DOF with init result from 12 DOF run @ 128
		+	* Same example call with verbose flag set, showing the function calls:
		+	a = DOFHierarchy(256, [6,9,12],'NoInit',[4,3,2],1)
		+	RunAlignment(256, 6,NoInit,4)
		+	input data size 256. smooth & subsample
		+	RunAlignment(128, 6,NoInit,3)
		+	input data size 128. smooth & subsample
		+	RunAlignment(64, 6,NoInit,2)
		+	input data size 64. smooth & subsample
		+	RunAlignment(32, 6,NoInit,1)
		+	running registration for 32 image at 6 DOF with init NoInit
		+	running registration for 64 image at 6 DOF with init result from 6 DOF run @ 32
		+	running registration for 128 image at 6 DOF with init result from 6 DOF run @ 64
		+	running registration for 256 image at 6 DOF with init result from 6 DOF run @ 128
		+	DOFHierarchy (256 , [6,9,12,], NoInit )
		+	RunAlignment(256, 9,result from 6 DOF run @ 256,3)
		+	input data size 256. smooth & subsample
		+	RunAlignment(128, 9,result from 6 DOF run @ 256,2)
		+	input data size 128. smooth & subsample
		+	RunAlignment(64, 9,result from 6 DOF run @ 256,1)
		+	running registration for 64 image at 9 DOF with init result from 6 DOF run @ 256
		+	running registration for 128 image at 9 DOF with init result from 9 DOF run @ 64
		+	running registration for 256 image at 9 DOF with init result from 9 DOF run @ 128
		+	DOFHierarchy (256 , [9,12,], result from 6 DOF run @ 256 )
		+	RunAlignment(256, 12,result from 9 DOF run @ 256,2)
		+	input data size 256. smooth & subsample
		+	RunAlignment(128, 12,result from 9 DOF run @ 256,1)
		+	running registration for 128 image at 12 DOF with init result from 9 DOF run @ 256
		+	running registration for 256 image at 12 DOF with init result from 12 DOF run @ 128
		+	DOFHierarchy (256 , [12,], result from 9 DOF run @ 256 )
		+
		+	a =
		+
		+	result from 12 DOF run @ 256