Add GliomaAI extension

[xristosand]

Summary

This pull request adds GliomaAI, a scripted 3D Slicer extension for automated glioma grading from T1CE and FLAIR MRI.

Main features

• Automated MRI preprocessing
• Binary glioma grading (LGG/HGG)
• Multiple deep learning models
• Integrated Grad-CAM explainability
• Support for T1CE and FLAIR MRI

Repository:
https://github.com/xristosand/SlicerGliomaAI

Tested with:

• 3D Slicer 5.6.2

New extension

Tier 1

Any extension that is listed in the Extensions Catalog must fulfill these requirements.

• Extension has a reasonable name (not too general, not too narrow, suggests what the extension is for). The extension name should not start with Slicer (unless it explicitly provides a bridge between Slicer and a tool or library), because it would make it more difficult to find extensions if the name of many started with the same word.
• Repository name is Slicer+ExtensionName (except if the repository that hosts the extension can be also used without Slicer)
• Repository is associated with 3d-slicer-extension GitHub topic so that it is listed here. To edit topics, click the settings icon in the right side of "About" section header and enter 3d-slicer-extension in "Topics" and click "Save changes". To learn more about topics, read https://help.github.com/en/articles/about-topics
• Extension description summarizes in 1-2 sentences what the extension is usable (should be understandable for non-experts)
• Any known related patents must be mentioned in the extension description.
• LICENSE.txt is present in the repository root and the name of the license is mentioned in extension homepage. We suggest you use a permissive license that includes patent and contribution clauses. This will help protect developers and ensure the code remains freely available. MIT (https://choosealicense.com/licenses/mit/) or Apache (https://choosealicense.com/licenses/apache-2.0/) license is recommended. Read here to learn more about licenses. If source code license is more restrictive for users than MIT, BSD, Apache, or 3D Slicer license then describe the reason for the license choice and include the name of the used license in the extension description.
• Extension URL and revision (scmurl, scmrevision) is correct, consider using a branch name (main, release, ...) instead of a specific git hash to avoid re-submitting pull request whenever the extension is updated
• Extension icon URL is correct (do not use the icon's webpage but the raw data download URL that you get from the download button - it should look something like this: https://raw.githubusercontent.com/user/repo/main/SomeIcon.png)
• Screenshot URLs (screenshoturls) are correct, contains at least one
• Content of submitted json file is consistent with the top-level CMakeLists.txt file in the repository (dependencies, etc. are the same)
• Homepage URL points to valid webpage containing the following:
  • Extension name
  • Short description: 1-2 sentences, which summarizes what the extension is usable for
  • At least one nice, informative image, that illustrates what the extension can do. It may be a screenshot.
  • Description of contained modules: at one sentence for each module
  • Publication: link to publication and/or to PubMed reference (if available)
• Hide unused github features (such as Wiki, Projects, and Discussions, Releases, Packages) in the repository to reduce noise/irrelevant information:
  • Click Settings and in repository settings uncheck Wiki, Projects, and Discussions (if they are currently not used).
  • Click the settings icon next to About in the top-right corner of the repository main page and uncheck Releases and Packages (if they are currently not used)
• The extension is safe:
  • Does not include or download binaries from unreliable sources
  • Does not send any information anywhere without user consent (explicit opt-in is required)

[pieper]

Thanks for working on this. It seems promising, but it's hard to say without more description and documentation on the repository. Also you need to be sure to include and follow the checklist from the extension PR template.

[xristosand]

Hello Mr. @pieper, thank you for your feedback! I have expanded the repository documentation with detailed installation and usage instructions, module descriptions, updated screenshots, and publication information. I have also added and completed the Tier 1 checklist, updated the extension metadata, and reduced the repository size. The Windows and Linux CI builds are passing. Please let me know if any further changes are required.
Thank you!

[xristosand]

Hello @pieper, just following up on this PR.

The requested documentation, Tier 1 checklist, metadata, and repository updates have been completed. The PR currently appears to be awaiting maintainer approval for the validation workflows to proceed.

This extension is also the subject of a manuscript that is currently under peer review, so having the extension proceed through the official ExtensionsIndex validation process is particularly important for the associated work.

Whenever you have a chance, could you please review and approve the workflow run? Please let me know if any further changes are needed from my side.

Thank you!