Skip to content
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

Inference time for automatic GM segmentation #11

Open
Nilser3 opened this issue Feb 13, 2025 · 1 comment
Open

Inference time for automatic GM segmentation #11

Nilser3 opened this issue Feb 13, 2025 · 1 comment

Comments

@Nilser3
Copy link
Collaborator

Nilser3 commented Feb 13, 2025

Description

This issue to explore the inference time taken by GM segmentation models.

Models to test

  1. sct_deepseg_gm SCT v. 6.5
  2. seg_gm_contrast_agnostic release: r20250204
  • The seg_gm_contrast_agnostic inference was performed through sct_deepseg (SCT branch : nlm/add_gm_contrast_agnostic_model , commit : 311307e24ae4f9bebd98574569294ab93f45ebd3) and not through nnUNetv2_predict

Dataset to test

The split test contains 233 volumes, 7 contrasts, at different dimensions and from different sites (see: #2 (comment))

Computer resource

The tests were performed on a CPU : Intel(R) Xeon(R) CPU E5-2640 v4 @ 2.40GHz , 10 Cores using codes/compute_inference_time.sh script.

Results

Image

  • Since both methods are 2D segmentation models, it was convenient to make a figure showing the inference time according to the number of 2D slices of each volume.
  • It is observed that sct_deepseg_gm is in general 5 times faster than seg_gm_contrast_agnostic, and that for volume with a large number of 2D axial slices (i.e. marseille-7T-MP2RAGE), the segmentation can take up to more than one minute per volume.

Related issues

#2

@jcohenadad
Copy link
Member

Great figure Nilser!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants