Ideas for New Directions

[MattClarkson]

• Integrate with ROS
• Integrate with OpenIGTLink? i.e. use OpenIGTLink to integrate with Slicer/PLUS
• Make it easier for MSc/BSc projects to use?

[thompson318]

Get a nice GUI for camera calibration, integrating surgery-calibration and surgery*tracker so people can easily do camera and handeye calibration. It would be worth doing a bit more research into what's out there, but from what I can see the Matlab toolboxes are the preferred way to do this. That would make a nice application that people would use?

[thompson318]

Get some more models of registration error built into core, or perhaps a new library, sk-uncertainty, sk-regerror?
https://doi.org/10.1007/s11517-020-02265-y
https://doi.org/10.1007/978-3-030-59716-0_26
https://ieeexplore.ieee.org/document/4359072

[thompson318]

Get BARD setup so it functions as a bare bones clinical guidance system by swapping sksurgeryaruco with sksurgerynditracker

[tdowrick]

Test edit

[thompson318]

Simone mentioned a general GUI that we could hook up to his models to get visualisation in real time. Could an RSE develop general GUI's for us that could be more widely useful. SNAPPY webapps. Visualisation using three.js

[mxochicale]

Creating of a new repository to support a Atracsys tracker interface?.

I wonder if we have accessibility to Atracsys SDK. I am not sure if I can find anything but just description of "C (DLL), C++, Python in Windows and Linux" for fusionTrack250 and fusionTrack500 . Similarly, I have come across with the few repositories that pretty much support ROS and one for python. This is telling me: (a) Linux will be the main OS for development, (2) either use ROS for development (or maybe ROS2) or going into the direction of https://github.com/luoshaqi/atracsysTracker which seems to be new one but doesn't have clear plans on the software life cycles.

Roadmap

This is roughly how I see the roapmap for this one (of course we need to sit together and discuss them):

1. Understanding what we have (SDKs?, hardware versions)
2. Identify other related libraries and how much effort we want to put to create a new library or just fork something that already is useful for us
3. Identify application and work towards publication of open-source libraries, experiments, or integration of tools
4. Dissemination of the development via tutorial, workshop, or just contacting Atracsys to cite us in their website.

References:

• Repositories for atracsysTracker:
  • https://github.com/jhu-saw/sawAtracsysFusionTrack/tree/devel
  • https://github.com/cerberos79/atracsys_fusionTrack
  • https://github.com/luoshaqi/atracsysTracker
• PlusLib supports Atracsys devices
  • https://github.com/PlusToolkit/PlusLib/tree/master/src/PlusDataCollection/Atracsys
  • http://perk-software.cs.queensu.ca/plus/doc/nightly/user/DeviceAtracsys.html
  • Integration of Atracsys Optical Trackers PlusToolkit/PlusLib#241

Thanks, --Miguel

[thompson318]

We should aim to create scikit-surgeryatracsys based on our tracker base class.

https://github.com/SciKit-Surgery/scikit-surgerycore/blob/master/sksurgerycore/baseclasses/tracker.py