Page History

...

1. Run beadtrack using your final parameter file:

$beadtrack$ beadtrack -param beadtrack.param

Ideally, this will run smoothly. If you see any output line that starts with 'Metro Error', this likely means that your tracking will not be good and you will need to tweak some of the optional parameters to obtain optimal tracking. After the beadtrack run is complete, you will see a printout of how many points are missing. For example:

Obj cont:  Views on which points are missing
 1   1: 57
 1   3: 52-59
 1   5: 45-46,57,59
 1   6: 1-2
 1   9: 45-46,50-52,54-59
 1  10: 44-45,47-50,52-59
 1  11: 58-59
 1  13: 1-2
 1  14: 52-59
 1  15: 52-53,56-57
 1  23: 57-59
 1  29: 41,58-59
 1  35: 31-33
 1  43: 31
 1  50: 58
 1  53: 1-3
 1  67: 54
 1  70: 46
 1  77: 41,49,54-55
 1  78: 58
 1  80: 54
 1  81: 8
 1  91: 1-3
 1  92: 55,59
 1  95: 54-56,58-59
 1 104: 31-59
 1 107: 55,57
 1 108: 47
 1 110: 43,49-50,56-59
 1 113: 1
 Total points missing =         129

Ideally, the number of missing points will be small.

2. If you are not satisfied with the results, tweak some of the optional parameters (particularly the local area box size) and re-run beadtrack.