Open ivoflipse opened 11 years ago
At least users can now modify several tracking thresholds, which should fix tracking for most cases (if possible at all) as long as the contacts have at least 1 sensor separating them.
However, it'll still be useful to have more fine-grained control over the tracking, like the tool I made to create the ground truth for my tracking.
Reading the documentation on QToolBar:
If a toolbar button is not appropriate, a widget can be inserted instead using PySide.QtGui.QToolBar.addWidget() or PySide.QtGui.QToolBar.insertWidget() ; examples of suitable widgets are PySide.QtGui.QSpinBox , PySide.QtGui.QDoubleSpinBox , and PySide.QtGui.QComboBox . When a toolbar button is pressed it emits the PySide.QtGui.QToolBar.actionTriggered() signal.
It seems I can add combo boxes and other things to the toolbar, so I could easily add something to adjust the tracking parameters. Only question is: would I want to store that information somewhere?
In some cases my automatic tracking doesn't work. To fix this I could either allow the user to manually draw the contours of the paw and 'fix' things, but from experience I can tell you that this is very tedious and would require some hacking to be added to the current UI (though I do have most of the code somewhere).
Another option would be to let the user tweak the thresholds (those that I added to config at least). While currently those can only be changed when you launch the app, perhaps I can come up with a way to change these values while the program is running and see if tweaking those values is enough to fix the tracking.
Obviously if the paws touch each other or you have awkward situations, like amputees (I'm looking at you Lyn!), you might still prefer to have some manual control. Any other ideas, possibly different tracking algorithms (more naive/simple ones) which can be switched to on the processing widget?