Internal:SlicerExtensions: Difference between revisions
| Line 22: | Line 22: | ||
The local execution module will enable the user to run APBNRR from Slicer similarly to how the PBNRR extension works. The user will be able to provide their own custom parameters for APBNRR. | The local execution module will enable the user to run APBNRR from Slicer similarly to how the PBNRR extension works. The user will be able to provide their own custom parameters for APBNRR. | ||
Both modules will be external. | |||
Revision as of 07:25, 25 July 2018
PBNRR Extension
Repository: https://github.com/aangelos28/Slicer-PBNRR
Status: TESTING
Built for: 4.9 (4.8 pending)
Tested on: 4.9 (4.8 pending)
Not yet uploaded (planned early August)
APBNRR Extension
Status: DESIGNING
I am currently in the process of the designing the APBNRR Slicer extension. At the moment, I am waiting for the feature requirements so I can integrate them into my design.
The core functionality will be carried out by two modules: a remote execution module and a local execution module.
The remote execution module will enable the user to execute my scripts for running APBNRR on Turing and later on an arbitrary cluster. Later on, the machine learning models that I have created will be used by this module for faster parameter optimization.
The local execution module will enable the user to run APBNRR from Slicer similarly to how the PBNRR extension works. The user will be able to provide their own custom parameters for APBNRR.
Both modules will be external.