Merge SlicerFreeSurfer and SlicerFreeSurferCommands and move into the Slicer GitHub organization?

PerkLab / SlicerFreeSurfer

This repository contains the SlicerFreeSurferImporter extension for 3D Slicer. The extension implements a module for importing models, scalar overlays, and segmentations from FreeSurfer, as well as handling the transformation of models from FreeSurfer to Slicer coordinates.

BSD 3-Clause "New" or "Revised" License

13 stars 4 forks source link

Merge SlicerFreeSurfer and SlicerFreeSurferCommands and move into the Slicer GitHub organization? #15

Open benzwick opened 1 year ago

benzwick commented 1 year ago

Should we merge SlicerFreeSurfer and SlicerFreeSurferCommands, and move them to the Slicer GitHub organization?

Please see the discussion here for more details.

One thing to consider is that the SlicerFreeSurfer extension doesn't have any external dependencies as far as I'm aware, whereas the SlicerFreeSurferCommands extension depends on FreeSurfer which needs to be installed and configured by the user, takes up about 14 GB of disk space, and can only be installed on Linux/Unix OS (on Windows WSL can be used).

jcfr commented 1 year ago

Instead moving the project SlicerFreeSurferCommands to the PerkLab GitHub organization, per suggestion of @pieper , the idea would be the following:

bundle the modules inside the PerkLab/SlicerFreeSurfer extension
make it clear that these commands are only available if freesurfer is installed.

That is, make it clear to the user at runtime, rather than in documentation, what features would be available if freesurfer is installed along with pointers to the installation instructions (even a button that opens the web page).

Sunderlandkyl commented 1 year ago

I agree, adding the SlicerFreeSurferCommands to SlicerFreeSurfer sounds like the best approach.