Add DeepLearningUI extension

[mturja-vf-ic-bd]

New extension

• Extension has a reasonable name (not too general, not too narrow, suggests what the extension is for)
• Repository name is Slicer+ExtensionName
• 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.
• If source code license is more restrictive for users than BSD, MIT, Apache, or 3D Slicer license then the name of the used license must be mentioned in the extension description.
• Extension URL and revision (scmurl, scmrevision) is correct, consider using a branch name (main, master, release, ...) instead of a specific git has 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
• 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
  • Tutorial: step-by-step description of at least the most typical use case, include a few screenshots, provide download links to sample input data set
  • Publication: link to publication and/or to PubMed reference (if available)
  • License: 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. We suggest you use the Slicer License or the Apache 2.0. Always mention in your README file the license you have chosen. If you choose a different license, explain why to the extension maintainers. Depending on the license we may not be able to host your work. Read here to learn more about licenses.
  • Content of submitted s4ext file is consistent with the top-level CMakeLists.txt file in the repository (description, URLs, dependencies, etc. are the same)

[pieper]

This is interesting and I'm glad you were able to implement it, but I have some questions that were unclear from the readme. First, how is one expected to generate the training data and why is it jpeg? Is there a repository of example training data? Second, how does on use the resulting model? Can you apply it to new data loaded in Slicer?

[mturja-vf-ic-bd]

This is interesting and I'm glad you were able to implement it, but I have some questions that were unclear from the readme. First, how is one expected to generate the training data and why is it jpeg? Is there a repository of example training data? Second, how does on use the resulting model? Can you apply it to new data loaded in Slicer?

Great questions. I am currently working on making the data generation process easier by designing another module that will be added to the same extension. The same goes for prediction. So There will be three modules in this extension: 1. Data preparation, 2. Training, 3. Testing. Among which only Training part is done.

[pieper]

Sounds good, looking forward to seeing it 👍

It probably makes sense to wait for the complete workflow before merging this and then posting on discourse with an example video or tutorial.

[mturja-vf-ic-bd]

@Connor-Bowley Will you have a look?

[Connor-Bowley]

Yes I will take a look at your extension.

[Connor-Bowley]

I have added some issues into your extensions git repo that should probably be addressed before merging this.

• Update module help text mturja-vf-ic-bd/SlicerDeepLearningUI#1
• Random Review questions: mturja-vf-ic-bd/SlicerDeepLearningUI#2
• Proper pip installs mturja-vf-ic-bd/SlicerDeepLearningUI#3
• Rename src/ folder to DeepLearnerLib or _DeepLearnerLib mturja-vf-ic-bd/SlicerDeepLearningUI#4

[jcfr]

@Connor-Bowley Thanks for the help reviewing 🙏

@mturja-vf-ic-bd After reviewing the suggestions linked above, let us know if you have any questions.

[mturja-vf-ic-bd]

@Connor-Bowley I have addressed your additional comments.

[Connor-Bowley]

@mturja-vf-ic-bd The extension is looking good. There are a few checkbox items you still need to address (e.g. the license)

[mturja-vf-ic-bd]

The checkbox items are addressed.

[Connor-Bowley]

The icon URL is incorrect. It should be https://raw.githubusercontent.com/mturja-vf-ic-bd/SlicerDeepLearningUI/main/DeepLearningUI.png

[Connor-Bowley]

Similarly the screenshot URL should be https://raw.githubusercontent.com/mturja-vf-ic-bd/SlicerDeepLearningUI/main/screenshot.png

One way to get the URL on Chrome is to go to the file in github, right-click on the image, and do "Open image in new tab". That should open the image where you can grab the correct link.

[jcfr]

Before we can more forward with the integration, I suggest you review and address the following issues:

• Add acknowledgement text mturja-vf-ic-bd/SlicerDeepLearningUI#6
• Fix Link in README mturja-vf-ic-bd/SlicerDeepLearningUI#7
• Output clarification mturja-vf-ic-bd/SlicerDeepLearningUI#8
• Update README Download module mturja-vf-ic-bd/SlicerDeepLearningUI#9
• Add icon different form the placeholder one mturja-vf-ic-bd/SlicerDeepLearningUI#29

[lassoan]

We are cleaning out our backlog of open pull requests. We have introduced tiers for extensions, making it easier to add experimental extensions to the index. @mturja-vf-ic-bd if you want your extension to be added to the index then let us know and we can add it as a tier 1. If we don't hear from you then we will close the pull request (but you can reopen it anytime).