Add shortcuts for easier tracking and correction

[Daniel]

1. a shortcut for jumping x-frames forward will allow a faster manual tracking of landmarks.

2. a shortcut for jumping to the next frame with a marker point of the current tracked segment

[Benjamin Knorlein]

Hi Daniel, Did you check the shortcuts? There is a shortcut for tracking the current marker to the next window. And i am not sure which you mean with jumping x-frames forward for faster manual tracking.

[Benjamin Knorlein]

Hi Daniel, Regarding this issue here some feedback:

for 2. There is already a shortcut for tracking the currently selected point to the next or the previous frame (1 and 2). Is this what you meant? If not can you be more specific

for 1. I am not convinced that a shortcut for jumping x-frames ahead is useful out of several reasons. Tracking only works well when going from one frame to the next as there should be as small a change in position as possible and the images should look as similar as possible, so tracking from frame n to frame n+x would probably not give good results, so the algorithm would have to track x-frames in between. The recommended workflow is therefore to use the 1 and 2 key shortcut for tracking problematic frames and once it is tracked accurately to start the normal tracking until it does encounter problems again. In this case the tracking can be stopped by using Esc and the user can manually track frames by using the 1 and 2 shortcuts again. Also if i user would like to track x-frames he would also have to enter the number of frames he wants to track which makes it probably take longer than using the normal shortcuts. Another feature you can use for cleaning the results in case there are high reprojection errors is the Error threshold in the reprojection error plot. If you set it you can go through the points with errors higher than the threshold by using 4 (I will add the shortcut to the Help dialog)

I therefore put the issue to wontfix, but I will also discuss in the next meeting. If I misunderstood the feature you are requesting please provide me more information.

[Daniel]

Hi Benjamin, I'll try to explain in a little more detail. The same workflow as explained in the issue # 119 (https://bitbucket.org/xromm/xmalab/issues/119/smoothing-option-for-manually-tracked) is the foundation for this request. To make it short, no XROMM will be used after XMALab analysis and therefore no rigid body transformation is necessary. As no markers are set and the images are flickering automatic tracking is not possible. Therefore the 1 and 2 shortcut is not working. So I need to manually track (click) the landmarks by perceiving the underlying anatomical structures and their 3D orientation. As shown in issue # 119 manual tracking of every other frame (as seen here: http://imgur.com/a/lBGJ7) produces better results than tracking every single frame (as seen here: http://imgur.com/a/1AGTG).

1. To save time while manually tracking every other frame it would therefore be very helpful to have a shortcut which allows me to jump like 10-20 frames forward instead of having to click 10-20 times >. As motion and recording speeds can differ it would be nice to be able to manually refine the number of frames which will be jumped when using this shortcut.

2. It can be very helpful to manually track the landmark motion in one camera first and then manually track the same landmark in the second camera. For various reasons (X-ray fluctuations, varying speeds within a video) the number of untracked frames can also vary greatly. In this setup, it would be very convenient to have a feature, which allows me to jump to the next frame with a marker set in the first camera.

[Benjamin Knorlein]

Hi Daniel, Thanks for the description. I decided to add the jump n-frames as it is not too much to implement and also does not interfere with any other functionality, But be aware that there will be no prediction on where the marker is, so you will probably have to adjust the detail view in a lot of cases. Also make sure when you do not track markers that the detection method of the marker is set to "no detection"

[Benjamin Knorlein]

PS: I will also look into the other jump. If it is easy to be done i will also implement that.

[Benjamin Knorlein]

fixes #118 : Added Shortcuts for moving n-frames and to move to incomplete frames

→ <<cset 9132f6734286>>