Neuronavigation: Implement UX principles to improve InVesalius usability

[paulojamorim]

The neuronavigation feature of InVesalius currently does not follow user experience (UX) principles in the user interface and workflow design. The software usability can be significantly improved by applying the basic UX design principles.

[faltunik]

Hi @paulojamorim . I am interested in this project. To get better understanding of issue and it's impact, I wish to work on some issue related to UX Experience. Can you please share some issue related to it?
Thanks

[DeeyaSingh]

Hello @paulojamorim, I too am interested in working on this project. I am proficient in python and would love to get involved with UX design. I can get started by learning more about the UX design principles. Could you please guide me through the required resources I can learn to familiarize myself with this project
Regards
Deeya Singh

[paulojamorim]

Hi @faltunik and @DeeyaSingh ,

We publish the instructions here: https://github.com/invesalius/gsoc/blob/main/gsoc_application.md

Please, follow the instructions.

Thanks

[vhosouza]

We need to break down this issue into smaller steps. @henrikkauppi and @mahansh564, in the next 2 weeks, please create separate issues as a roadmap to achieve the final goal of UI/UX enhancements. Here is a preliminary list of more urgent improvements:

• icons for probe, reference, object, robot - Anshul
• define the difference between state and project files, find a common process to work with both and improve both
• move neuronavigation settings to the settings dialog box - get inspiration from PyCharm - probably create a button specific for neuronavigation settings
• when loading the registration of the robot, no dialog or feedback to the user is given
• user feedback for the tractography
• for the progress bar used in creating a surface from a mask, it uses the async module. Apply this for other processes such as the tractography loading files, which takes a long time
• significant improvements are needed on the fiducial recordings - possibly a dialog with fixed order for recording the tracker fiducials. Check the UI prototype for a head to give feedback on the recorded image fiducials. Rethink the order and usability. User click the LEI, REI or NAI button and it activates the "cross" (there would be no need to click on the cross button on upper menu anymore)
• save the fiducials separate from the markers lists. Maybe include in the project file or the state file, as it is already done.
• discuss with Ana about the UI for E-field
• The UI for the tractography needs to be improved as well.
• Add a log file when the software crashes. Check with Olli-Pekka what the ROS saves.
• Add sound feedback to the registration clicks
• Add indication if the marker is not visible, also sound feedback
• in refine coregistration dialog, indicate the areas where to collect the markers similar to next
• need an indicator that head movement compensation with the robot is ON and add a button to turn it ON and offset
• Accessibility feature to scale the font size and other elements
• Undo for marker removal, like ctrll+z
• Compute and visualize the tangential direction of the coil while navigating. Possible solution: check if coil normal is aligned with the line between coil center and center of mass of the head/brain.
• Make the mouse cursor status as busy while trying to connect to tracking devices. User might not understand that the program is running.
• Create a Preference tab for navigation configs, i.e. external trigger update rate, COM port selection, enable/disable beep for marker creation, import markers files for MTC and Polaris, etc
• Visualize stimulus location on slices: Check if this is really beneficial.

[mahansh564]

Divided into smaller issues and many issues solved in the latest pull request