Slicer Application Settings: User

I found that there are user settings in the Application Settings of Slicer, which can record Name, Login, Email, Organization, etc. How can these user information be used? Will the user information be saved to a file when saving the data? No instructions were found in the user manual of the community. In addition, I found that these user settings do not seem to be mandatory, and will not be reminded to restart after the settings.
Can anyone give me some information? Thank you.

User information is not used by Slicer core, only by certain extensions, such as Quantitative Reporting (to record who performed certain operations and record it in the exported DICOM structured report.

You can access the information like this:

1 Like

Thanks for your reply, what should I do if I want to save the user information to the Annotation module’s save data file(such as *.acsv) and Segmentation data(such as *.seg.nrrd)? Should I modify the code of the slicer core(the part of save data)? Or use the Quantitative Reporting Extension feature that you mentioned to save user information? Do you have any suggestions?

In addition, I installed the Quantitative Reporting extension, but found that nothing happens when I click the “Retrieve and lost data” button.

You can save information to the name or description of points in .acsv file and custom segment tags in .seg.nrrd file.

No Slicer core changes are needed. You can create a module that adds an observer to each loaded annotation / segmentation node and updates point description / adds custom segment tag that contains user information. You can also save the information in the scene (.mrml file) or additional text file if user information does not need to be saved inside the annotation/segmentation files.


Thank you, Lassoan.

I think this suggestion really helped me. But now I want to get user information from loadable module, what should I do? Can you give me some examples, such as Quantitative Reporting for python.

Search for applicationLogic in Slicer source code to see how it can accessed from various parts of a module.

1 Like