Skip to content

5.8 #2179

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 23 commits into
base: 5.8
Choose a base branch
from
Open

5.8 #2179

wants to merge 23 commits into from

Conversation

payabvashlab
Copy link
Contributor

https://github.com/payabvashlab/SlicerHeadCTDeid
We update for Slicer 5.8

Tier 1

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

  • [X ] Repository name is Slicer+ExtensionName (except if the repository that hosts the extension can be also used without Slicer)
  • [X ] 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
  • [X ] Extension description summarizes in 1-2 sentences what the extension is usable (should be understandable for non-experts)
  • [X ] Any known related patents must be mentioned in the extension description.
  • [X ] 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.
  • [X ] 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
  • [X ] 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)
  • [X ] Screenshot URLs (screenshoturls) are correct, contains at least one
  • [X ] 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:
    • [X ] Extension name
    • [X ] Short description: 1-2 sentences, which summarizes what the extension is usable for
    • [X ] At least one nice, informative image, that illustrates what the extension can do. It may be a screenshot.
    • [X ] Description of contained modules: at one sentence for each module
    • [X ] 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:
    • [X ] Click Settings and in repository settings uncheck Wiki, Projects, and Discussions (if they are currently not used).
    • [X ] 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:
    • [X ] Does not include or download binaries from unreliable sources
    • [X ] Does not send any information anywhere without user consent (explicit opt-in is required)

LennyN95 and others added 23 commits January 29, 2025 18:38
Update MHubRunner.json

Update repository URL to point to the new version of MHubRunner extension.
Bumps [actions/setup-python](https://github.com/actions/setup-python) from 5.3.0 to 5.4.0.
- [Release notes](https://github.com/actions/setup-python/releases)
- [Commits](actions/setup-python@0b93645...4237552)

---
updated-dependencies:
- dependency-name: actions/setup-python
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <[email protected]>
Bumps [actions/setup-python](https://github.com/actions/setup-python) from 5.4.0 to 5.5.0.
- [Release notes](https://github.com/actions/setup-python/releases)
- [Commits](actions/setup-python@4237552...8d9ed9a)

---
updated-dependencies:
- dependency-name: actions/setup-python
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <[email protected]>
This is a follow-up to Slicer@74a83cb when the SlicerWMA.json was removed from the extensions index. This commit re-adds the SlicerWMA.json to store in the ARCHIVE directory.
SlicerWMA was removed from the extensions index in Slicer@74a83cb.
* Update MorphoDepot.json - point to permanent home

The repo was transferred so github does the redirected correctly, but this is the new official repo.

* Update MorphoDepot.json - add .git

Maybe fix lint validation issue
The ANTsPy library wraps image processing framework ANTs in Python. It provides
modules tailored for integration with SlicerMorph extension and workflow.

It includes reading and writing of medical images, algorithms for registration,
segmentation, statistical learning. SlicerANTsPy extension makes ANTsPy
available inside 3D Slicer, and provides graphical user interface to some
of its common functionalities such as interactive registration, batch (group wise)
registration, template creation and tensor-based morphometry via Jacobian
analysis (WIP).

It provides some convenience features such as optionally initializing all
registrations via landmarks.
Extension name (in CMake Project name) must match .json file.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

10 participants