尚未偵測到更新。GitHub 發布版本後會顯示在這裡。
個人 GitHub 帳號下公開儲存庫的擁有者可以登入並驗證所有權,自行管理介紹,無需管理員核准。
登入並產生驗證檔案,在 30 分鐘內將其提交至此儲存庫的預設分支。其他分支或分叉儲存庫中的檔案無效。然後在下方檢查檔案,即可無需管理員核准直接管理專案。請保留檔案以維持管理權限。
如需登入,將前往登入頁面。登入後請回到此處,再次點擊所選的驗證按鈕。
在專案資料夾中執行 /nomorevibe verify,即可驗證所有權並自行管理介紹。
一分鐘完成驗證SlicerDSpace: an integrated 3D Slicer workflow for anatomical reconstruction and connectivity analysis from diffusion MRI
翻譯準備中
取自儲存庫 README
正在載入完整 README。
檢視完整 README ↗Diffusion MRI anatomical priors, microstructure and connectivity in 3D Slicer
Overview | Video | Technology | Agent Skills | Install | Quick Start | CLI | Documentation | Citation | 中文
Project Website | User Guides | Release Status
SlicerDSpace combines T1-weighted-image-free anatomical reconstruction, microstructural mapping and white-matter analysis in one 3D Slicer module. Choose your methods, prepare their environment and inspect the results in the same scene.
Complete 48-second preview at 1.5× speed · Watch the full video (MP4, 1:12) · Website player
| Workflow | Methods and products |
|---|---|
| Input preparation | DICOM, NIfTI and NRRD/NHDR import; gradient checks, brain masking and optional DWI correction |
| Microstructure | DTI FA/MD/AD/RD; optional Free-water, NODDI, DKI and Python MK-Curve |
| Anatomical prior | DDSeg tissue labels, DDParcel regions, DDSurfer white/pial surfaces; optional cortical postprocessing |
| Tractography | DTI deterministic, UKF, CSD/ACT with SIFT2, and SAF short association fibres |
| Fiber bundles | Official WMQL queries, WMA atlas classification and TractCloud |
| Connectome | Streamline-count and scalar-weighted matrices; eligible SIFT2-weighted connectivity |
Key products load into Slicer as successful stages finish. Run-scoped loading reuses scene nodes, while logs, parameters and QC stay with each run. Optional regional analysis reuses completed maps, full tractograms and matrices for selected DDParcel regions. Search by region name or label ID for scalar/tissue summaries, cortical morphology, A-to-B streamline selection and regional connectivity. Detailed options stay collapsed; reports and cohort CSV templates are included.
Shared preparation and compatible cached outputs are reused. Independent microstructure models and separate subjects can run concurrently within the configured resource budget. See experiments and measured optimizations.
| Layer | Components | Role |
|---|---|---|
| Slicer interface | 3D Slicer, Qt/PythonQt, CTK, MRML | Product selection, native scene loading and result review |
| Scientific Python | Python, NumPy, SciPy, nibabel, SimpleITK | Images, geometry, numerical fitting and data exchange |
| Neural inference | PyTorch, DDSeg/DDParcel/DDSurfer models | Tissue, regional and surface reconstruction |
| Microstructure | DIPY, AMICO, Python MK-Curve | Tensor, free-water, neurite and kurtosis models |
| Diffusion tools | SlicerDMRI, optional UKFTractography, MRtrix3 and FSL | DTI preparation, tracking and selected correction routes |
| Optional backends | PNL CNN/ANTs, native FreeSurfer components, WMQL, WMA, TractCloud | Masking, cortical postprocessing and bundle identification |
| Automation | Python CLI, JSON run plans, batch runner, Agent Skill | Reproducible commands, parameter variants and cohort scheduling |
Dependencies follow the selected route. The default CSD/ACT route needs MRtrix3; a DTI-only route with a supplied mask avoids PNL, FSL and FreeSurfer. The explicit Slicer-native preset offers fewer external environments. See the capability/platform matrix.
Implementation origins: DDSeg uses converted Python/PyTorch models; SAF and MK-Curve are unofficial Python ports of author MATLAB methods. PNL CNN masking calls the author's existing Python backend. Optional surface postprocessing uses original FreeSurfer components and a personal activation file. Details: provenance · surface components.
Our install-and-use Agent Skill guides a local Agent through setup, analysis and result review.
| Task | What the Skill covers |
|---|---|
| Install and enable | Find Slicer, stage the module, verify activation and prepare selected dependencies |
| Plan and run | Prepare inputs, choose algorithms and tracking/bundle sources, review plans and run requested analyses or batch experiments |
| Review and reuse | Inspect outputs, logs and QC; reuse compatible results and preserve unrelated scene nodes |
Open the Skill · Agent usage guide · CLI templates · Algorithm Shell templates
Prompts link directly to SKILL.md, the Agent's entry point. To install the Skill
in an Agent, copy the complete slicerdspace directory, including its references,
scripts and templates.
Copy this prompt into your local Agent:
Read https://github.com/NeuroDMRI/SlicerDSpace/blob/main/.agents/skills/slicerdspace/SKILL.md.
Install and enable SlicerDSpace in my local 3D Slicer.
Set up the required dependencies and download the corresponding model weights.
The Agent checks storage space and existing resources, waits for your choice, and saves the selected path for GUI and CLI use. It downloads only the resources needed by your selected analyses. Repository access is required while it is private; you can provide an authorized local checkout if the Agent cannot open the URL. Confirm licenses and restarts when requested.
Use an existing installation. Replace the input and output paths in this example:
Read https://github.com/NeuroDMRI/SlicerDSpace/blob/main/.agents/skills/slicerdspace/SKILL.md.
Use SlicerDSpace to run DDParcel brain parcellation, CSD/ACT tractography and structural connectome construction for /path/to/subject; save results to /path/to/results.
Show me the plan and wait for confirmation before running. Afterwards, summarize the outputs and QC findings.
Change the requested methods to suit your study; the usage guide and CLI templates cover other routes and batch execution. The website guide bot provides navigation and curated answers; installation and analysis run through your own Agent.
Use an authorized checkout while the repository is private. This lightweight source installation omits the website and historical reports; a full checkout retains development tests and research materials.
git clone --filter=blob:none --no-checkout --depth 1 https://github.com/NeuroDMRI/SlicerDSpace.git
cd SlicerDSpace
git show HEAD:scripts/extension_runtime/runtime_checkout.txt | git sparse-checkout set --no-cone --stdin
git checkout
python3 scripts/stage_slicer_extension.py \
--install-root ~/SlicerDSpace-extension --slicer-version Slicer-5.10 \
--link-mode copy
For Slicer 5.10, add the expanded absolute path below in Edit > Application Settings > Modules > Additional module paths, then restart:
~/SlicerDSpace-extension/SlicerDSpace/lib/Slicer-5.10/qt-scripted-modules
Match --slicer-version to your installation. After a source update, restage
the extension and restart Slicer. More options: download and installation guide.
In the module, select products, then open Environment and installation > Prepare selected analysis environment. Confirm required tools and model terms; restart if requested and select Prepare again to continue. SlicerDMRI, PyTorch and the optional UKFTractography extension are prepared as needed.
Weights, templates and atlases live separately in SlicerDSpace-models. The setup checks SHA256, caches downloads and saves paths. Existing installations, offline models and repair are available under More options. See managed setup and resource terms.
For explicit CLI surface-model preparation:
python3 scripts/download_model_assets.py --profile surface \
--asset-root ~/SlicerDSpace-model-assets --source url \
--source-id slicerdsurfer_models_git
For all anatomical model groups, use scripts/download_model_assets.sh --profile core.
Other profiles and offline import are documented in model setup.
Prepared inputs use this layout:
sub-01/
input/
data.nii.gz
bvals
bvecs
nodif_brain_mask.nii.gz # optional; supply or generate
The mask shares the DWI voxel grid. Gradients match the DWI volume count; motion-corrected data use the corresponding rotated gradients. DICOM/NRRD import is under Advanced settings > Regions & input import. The first-workflow tutorial includes a synthetic installation check.
| Part | Default | Other choices |
|---|---|---|
| Missing brain mask | PNL diffusion CNN; valid supplied masks are reused | SynthStrip, MRtrix, DIPY median-Otsu, supplied mask only |
| Microstructure | DTI | Add Free-water, NODDI and/or DKI; select WLS/OLS or Python MK-Curve for DKI |
| Tractography | MRtrix3 CSD/ACT | DTI deterministic, UKF, SAF |
| Fiber bundles | Official WMQL multi-bundle queries | WMQL subset selection, WMA, TractCloud |
Use ... beside Microstructure, Tractography and Fiber bundles to select one or several methods. Advanced settings groups masking, model parameters, performance, regional analysis/input import and experiments. Environment installation remains separate.
UKF runs automatically through its installed extension and can feed WMA directly.
WMA supports --wma-atlas org|east-west|naba (default: org), with the same
selector in Advanced settings. Atlas selection and on-demand resources.
Multiple tracking methods produce separate <run>__<backend> variants.
The full quantitative tractogram is retained alongside a capped VTK display preview.
NODDI/DKI require eligible acquisitions. Inspect fit-validity masks, sparse fiber bundles, alignment and anatomical priors before accepting results. Method details: microstructure · UKF · WMQL.
Use Slicer's Python to check a prepared DTI route:
export SLICER="/path/to/Slicer"
"$SLICER" --launch PythonSlicer shared/run_subject_pipeline_cli.py \
--no-user-config --strict-environment \
--subject-root /path/to/sub-01 --subject-id sub-01 \
--output-root /path/to/analysis/sub-01/dti --run-name dti \
--targets validation,microstructure --microstructure-stages dti \
--brain-mask-backend provided --doctor
Keep the same arguments and replace --doctor with --plan to inspect the plan,
then --execute to run. This example expects an existing reviewed mask.
The CLI templates cover imports, masking, anatomical priors, all microstructure and tracking routes, explicit bundle sources, connectomes, PowerShell and reports. Experiments covers named parameter variants and concurrent subjects in both CLI and Advanced settings. Start with one concurrency level and budget combined RAM/VRAM use.
| Task | Guide |
|---|---|
| First analysis | Quick Start |
| Commands and batch experiments | CLI templates · Experiments · Example request |
| Dependencies and platforms | Support matrix · Linux · Windows · macOS |
| Models and offline resources | Assets · Resource policy |
| Results and selected regions | Result review · Regional analysis |
| Settings and output layout | Shared settings · |
| Area | Current scope |
|---|---|
| Reference environment | Linux and Slicer 5.10; Windows/macOS availability is route-specific |
| Validation | Recorded Linux SDK/CPack, GUI and selected real-data workflows; coverage is tied to the documented revision and inputs |
| Distribution | Private pre-release; Extension Index entry remains a Tier 1 proposal |
| Licensing | BSD-3-Clause project code; third-party source and model assets retain separate terms and release gates |
Execution status, automatic QC and human review are recorded or assessed separately. Review validation records, platform support and release readiness for scope and outstanding checks. The software is for research use, not clinical diagnosis.
Development checks require a full checkout:
make test-fast
python3 scripts/audit_slicer_extension_metadata.py --json
Validation is local during development. GitHub Actions and website publication remain manual-only.
Report the Slicer version, OS, selected methods, failure message and redacted logs. Remove subject identifiers and private paths before sharing. Use the result-review guide for run records and the managed-setup guide for dependency repair.
Cite the software version through CITATION.cff and the methods used in your analysis: DDSurfer, DDSeg and DDParcel. Additional integrated methods are listed in the website bibliography. The SlicerDSpace protocol manuscript is in preparation.
Project code: BSD-3-Clause, LICENSE.txt. Bundled components retain the terms in THIRD_PARTY_NOTICES.md. Weights, templates and subject data are governed separately; review asset permissions before redistribution.
| Developer and release guides | Repository layout · Extension readiness |