Custom preset handling (storing/export/import) #50
Comments
che85
changed the title
|
Another idea would be to provide an option to change the database folder. The folder could store |
|
The selected database folder location would be saved in the parameter node. When loading the module, it can check if the database folder exists on the local machine. If it doesn't exist, a dialog is displayed with the message saying that the database folder couldn't be found. The user has the option to locate the folder which will then be updated in the parameter node if successfully associated other saved parameters. |
che85
added a commit
to che85/SlicerElastix
that referenced
this issue
Nov 13, 2024
lassoan
pushed a commit
to che85/SlicerElastix
that referenced
this issue
Jan 17, 2025
Built-in elastix registration presets can be copied into the scene, edited, and saved in the scene. When registration is launched then the in-scene configuration data is written to files and passed to Elastix. In-scene presets can also be saved as user presets, into the user profile folder (each preset in a separate subfolder, containing all necessary information, so that presets can be easily shared with other just by copying the complete folder content). see lassoan#50
lassoan
pushed a commit
that referenced
this issue
Jan 17, 2025
Built-in elastix registration presets can be copied into the scene, edited, and saved in the scene. When registration is launched then the in-scene configuration data is written to files and passed to Elastix. In-scene presets can also be saved as user presets, into the user profile folder (each preset in a separate subfolder, containing all necessary information, so that presets can be easily shared with other just by copying the complete folder content). see #50
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
@lassoan In #45 (comment) you mentioned the following:
"Custom presets could be saved in the applications settings folder
(os.path.dirname(slicer.app.slicerUserSettingsFilePath))to make sure they are preserved when the application is removed. But this can be added later, your preset editor is already useful as is."I could imagine creating custom presets and being able to add some functionality to export presets for the purpose of sharing. Especially when it comes to experiments, one wants to be able to reproduce results, so sharing custom presets would be very important. Other users could then import the presets into their database (including md5 checks to avoid duplication of txt files).
Let me know what you think
cc @DevLaurence
The text was updated successfully, but these errors were encountered: