Release: OpenDose4D, (need help to finish integration)


The OpenDose collaboration is proud to announce its first open beta release of the module opendose4d to perform dosimetry calculations in molecular radiotherapy procedures. The code is publicly available at gitlab.
We need some help to complete Slicer integration, the code already has its own unit testing ready, so every functionality is tested to run.
We already have some alpha testers for the raw code that has proven to be very useful catching bugs. We need also some beta testers that evaluates further the code.
The module expects a multipoint SPECT/CT or multipoint PET/CT, non dynamic. It also is able to proceed with at least one CT, although is not optimal (registration depends now from user).

The OpenDose Collaboration

1 Like

Sounds great. Please send a pull request to ExtensionsIndex that adds your .s4ext file (found in your build folder).

I am searching the build folder, but I think you are referring to a c++ build folder for c++ loadable extensions. This whole extension is purely python, there is no build folder.

Do you have plans to make it available through Slicer’s Extension Manager? Typically I only report bugs/issue bug fixes for extensions that are built by the Slicer organization and report their testing results at

yes, that’s the plan

1 Like

Even if you only have Python scripted modules, it is useful if you can build your extension, as it allows you to test automatic testing and package creation. It also creates the s4ext file, but you can also easily handcraft an s4ext file (there are many examples in the ExtensionsIndex repository.

I have created a s4ext file

# First token of each non-comment line is the keyword and the rest of the line
# (including spaces) is the value.
# - the value can be blank

# This is source code manager (i.e. svn)
scm git
scmurl git://
scmrevision develop

# list dependencies
# - These should be names of other modules that have .s4ext files
# - The dependencies will be built first
depends SlicerElastix

# Inner build directory (default is ".")
build_subdirectory .

# homepage

# Firstname1 Lastname1 ([SubOrg1, ]Org1), Firstname2 Lastname2 ([SubOrg2, ]Org2)
# For example: Jane Roe (Superware), John Doe (Lab1, Nowhere), Joe Bloggs (Noware)
contributors Alex Vergara Gil (INSERM, France), Janick Rueegger (KSA, Switzerland)

# Match category in the xml description of the module (where it shows up in Modules menu)
category Nuclear Medicine

# url to icon (png, size 128x128 pixels)

# Give people an idea what to expect from this code
#  - Is it just a test or something you stand behind?
status stable

# One line stating what the module does
description This module implements the full 3D Dosimetry for molecular radiotherapy on multiple time points.

# Space separated list of urls

# 0 or 1: Define if the extension should be enabled after its installation.
enabled 1

Looks like this is already the case, see

Probably I am missing something

The s4ext file has a couple of mistakes (wrong URLs, not ideal branch name), but we can sort these out in the pull request, where there is a comprehensive checklist. So, please send the pull request with this s4ext file and we’ll complete the review there.