I am adding a new module directory via application settings, but after restart, the added directory disappears. There are no errors relevant to this during application startup. I observe this with both 5.10 and nightly. I am on a mac. I tried this with an empty directory, and the behavior is the same, so it is not related to the specific module.
Additional module paths are checked at application startup and if the folder does not exist then it is removed. Could you have a look at the Slicer-NNN.ini file and see what paths are listed there, how they are defined (with relative path?) and if they can be found on your system? Are the folders on a physical disk or some virtual/network drive?
It is not very useful but I want to add that I have seen this, and couple other variants, such as drag and dropping a module folder onto the Slicer windows not bringing the “add these python scripts to module paths” option, or extension wizard not recognizing some module folders, sporadically on MacOS. Never managed to consistently replicate though.
The folder definitely exists. I created the folder, and selected that folder from the file picker. I confirm the folder itself remains in place after Slicer restart.
When I look at the ~/.config/slicer.org/Slicer.ini file, I do not see the added folder anywhere before or after the restart. Is this the right file to check?
Physical drive, main drive on a mac mini.
I do not see this issue on linux.
The Slicer-NNN.ini file is the revision-specific config file in the application’s install path. You can get the path by typing this into the Slicer Python console:
slicer.app.slicerRevisionUserSettingsFilePath
If the path is not added to this .ini file then there may be some macOS permission issues. @pieper have you experienced something like this lately?
1 Like
I don’t usually use the settings files for this. I use the --additional-module-paths command line argument (this helps isolate different experiments using the same Slicer version).