Feature comparison
Feature |
NaviNIBS |
Brainsight |
Localite |
Nexstim |
visor2 |
InVesalius |
Software |
|
Open source |
✔ |
✖ |
✖ |
✖ |
✖ |
✔ |
Commercial support |
✖ |
✔ |
✔ |
✔ |
✔ |
✖ |
Extensible with addons |
✔ |
✖ |
✖ |
✖ |
✖ |
≈ |
Imaging data |
|
MRI import |
✔ |
✔ |
✔ |
✔ |
✔ |
✔ |
Integrated image segmentation |
✖ |
✔ |
✔ |
✔ |
✔ |
✔ |
SimNIBS head model import |
✔ |
✔ |
✖ |
✖ |
✖ |
✖ |
fMRI overlay visualization |
🕓 |
✔ |
✔ |
✔ |
✔ |
✖ |
DTI visualization |
🕓 |
✖ |
✖ |
✖ |
✖ |
≈ |
Targets |
|
Create planned targets |
✔ |
✔ |
✔ |
✔ |
✔ |
✖ |
Import planned targets |
✔ |
≈ |
≈ |
? |
✖ |
? |
Create grid of targets |
✔ |
✔ |
✔ |
✔ |
✖ |
✖ |
E-field modeling |
🕓 |
≈ |
✖ |
✔ |
≈ |
✖ |
Tracking |
|
NDI Polaris camera support |
✔ |
✔ |
✔ |
✔ |
✔ |
✔ |
OptiTrack camera support |
✔ |
✖ |
✖ |
✖ |
✖ |
≈ |
Other tracking systems support |
≈ |
✖ |
✖ |
✖ |
✖ |
✔ |
Coil calibration |
✔ |
✔ |
✔ |
✔ |
✔ |
✔ |
Pointer calibration |
✔ |
✖ |
✖ |
✖ |
✖ |
✖ |
Registration |
|
Autoset planned fiducials |
✔ |
✖ |
✖ |
✖ |
✖ |
✖ |
Fiducial registration |
✔ |
✔ |
✔ |
✔ |
✔ |
✔ |
Head points refinement |
✔ |
✔ |
✔ |
✔ |
✔ |
✖ |
Sample point re-registration |
✔ |
✖ |
✖ |
✖ |
✖ |
✖ |
Template anatomy warping |
🕓 |
✔ |
✔ |
✔ |
✔ |
✖ |
Navigation |
|
Real-time pose error metrics |
✔ |
✔ |
✖ |
✔ |
≈ |
≈ |
Stimulation-triggered sampling |
✔ |
✔ |
✔ |
✔ |
✔ |
✖ |
API control of targeting |
✔ |
✖ |
✖ |
✖ |
✖ |
✖ |
Real-time data streaming out |
✔ |
≈ |
✖ |
? |
✖ |
✖ |
Electrophysiology |
|
EEG electrode digitization |
✔ |
✔ |
✔ |
✔ |
✖ |
✖ |
EMG response visualization |
✔ |
✔ |
✔ |
✔ |
✔ |
✖ |
Automated thresholding |
🕓 |
✖ |
✖ |
✔ |
✖ |
✖ |
EEG response visualization |
🕓 |
✖ |
✖ |
✔ |
✖ |
✖ |
Robot integration |
|
Basic Cobot control |
✔ |
✔ |
✔ |
✖ |
✖ |
✖ |
Advanced Cobot control |
✔ |
✖ |
✖ |
✖ |
✖ |
✖ |
Other robot control |
✖ |
✖ |
✖ |
✖ |
≈ |
≈ |
✔ |
Supported |
🕓 |
Planned |
≈ |
Partial |
✖ |
Not supported |
? |
Unknown |
Note: this feature comparison is accurate to the best of our knowledge as of the time of writing. If you notice any inaccuracies or would like to suggest changes, please let us know by opening an issue in the documentation repo, or contacting us directly.