User Tools

Site Tools


other:dsx:x4d:object_tracking

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
other:dsx:x4d:object_tracking [2025/06/02 19:03] – [Object Tracking Widget] added links. wikisysopother:dsx:x4d:object_tracking [2025/06/02 19:03] (current) – [Object Tracking Widget] wikisysop
Line 20: Line 20:
   * **Stop** Stops the currently running optimization.   * **Stop** Stops the currently running optimization.
   * **Evaluate** Evaluates the poses of the currently selected bones using the selected image metric. The results are written to the output window.   * **Evaluate** Evaluates the poses of the currently selected bones using the selected image metric. The results are written to the output window.
-  * **Poses Saved During Tracking** Sometimes the global minimum of the image fitness function is not the correct pose of the bone being tracked. This is often because the X-ray and DRR image processing parameters are not ideal (see //Image Optimization//, below). Other times, it is because the bone in the X-ray images is occluded by soft tissue or other bones, or because of inherent differences between X-ray images and DRRs (image resolution, X-ray scatter, CT thresholding, etc.). To account for these other times, the ASA tracking algorithm attempts to save bone poses that result in local minima of the cost function, while still searching for the global minimum. The idea is that if the correct bone pose is not the global minimum, it is likely to be a local minimum somewhere within the search range. The ASA algorithm thus attempts to save a set of local-minimum poses so that you can revisit them once optimization has finished. The //Max Poses// field specifies how many local minima to save. When the tracking optimization has finished, if the final bone pose is not the correct pose, you can re-apply the saved poses by dragging the slider for that bone. If one of them is correct (or at least better than the final pose), you can use the //Add Current Poses to Maps// command in the //Pose Map// widget to add that pose to the map, thus overwriting the final pose.+  * **Poses Saved During Tracking** Sometimes the global minimum of the image fitness function is not the correct pose of the bone being tracked. This is often because the X-ray and DRR image processing parameters are not ideal (see example below). Other times, it is because the bone in the X-ray images is occluded by soft tissue or other bones, or because of inherent differences between X-ray images and DRRs (image resolution, X-ray scatter, CT thresholding, etc.). To account for these other times, the ASA tracking algorithm attempts to save bone poses that result in local minima of the cost function, while still searching for the global minimum. The idea is that if the correct bone pose is not the global minimum, it is likely to be a local minimum somewhere within the search range. The ASA algorithm thus attempts to save a set of local-minimum poses so that you can revisit them once optimization has finished. The //Max Poses// field specifies how many local minima to save. When the tracking optimization has finished, if the final bone pose is not the correct pose, you can re-apply the saved poses by dragging the slider for that bone. If one of them is correct (or at least better than the final pose), you can use the //Add Current Poses to Maps// command in the //Pose Map// widget to add that pose to the map, thus overwriting the final pose.
  
 ===== Adaptive Simulated Annealing ===== ===== Adaptive Simulated Annealing =====
other/dsx/x4d/object_tracking.1748890987.txt.gz · Last modified: 2025/06/02 19:03 by wikisysop