GithubHelp home page GithubHelp logo

Comments (6)

dbouget avatar dbouget commented on June 12, 2024 2

Hi @remogg, which pipeline were you trying to run and for which tumor type?

If you can try to use the test data provided in Raidionics, and run either Preoperative reporting or Preoperative segmentation from the Actions tab and select glioblastoma as tumor type?

From the error message, it looks like a T1-w MR image is expected for timestamp 0 (which is assumed to be preoperatively), but hasn't been provided. It is unlikely an issue with DICOM headers, as long as you can see all the images you've loaded into Raidionics appearing inside the right-hand side, each tagged with the proper sequence type.

from raidionics.

andreped avatar andreped commented on June 12, 2024

Hello, @remogg!

I noticed that you closed the Issue. Did you mean to do that? If yes, could you report how you solved the issue, as it might be of interest to others.

Do you have an MRI in NIfTI format we could get access to in order to reproduce the issue?

Regardless, @dbouget should be able to assist you further.

from raidionics.

remogg avatar remogg commented on June 12, 2024

Hello @andreped,
i accidentally opened 2 tickets with the same content so decided to close this one.

"Do you have an MRI in NIfTI format we could get access to in order to reproduce the issue?" - yes, i could send you an example.

from raidionics.

andreped avatar andreped commented on June 12, 2024

i accidentally opened 2 tickets with the same content so decided to close this one.

Oh, OK. In that case, to keep the conversation, I closed the other one and reopened this one :)

"Do you have an MRI in NIfTI format we could get access to in order to reproduce the issue?" - yes, i could send you an example.

You can see my email from my GitHub user profile if you wish to send me a NIfTI file over email. If it is a public dataset, you could upload it to a google drive and give us access through a URL here. That way @dbouget who likely will debug this further, can get access directly. Otherwise, I can redirect the sample file to him.


EDIT: Perhaps @dbouget can follow this up.

from raidionics.

remogg avatar remogg commented on June 12, 2024

Thank you for the fast reply @dbouget.

From the error message, it looks like a T1-w MR image is expected for timestamp 0 [...].

I provided T1w, T2w, FLAIR, T1ce. All Sequences were recognized correctly, except the T1ce, so I selected the correct sequence type manually for it. Then i ran preopreative reporting and selected Gliobloastoma.

If you can try to use the test data provided in Raidionics, and run either Preoperative reporting or Preoperative segmentation from the Actions tab and select glioblastoma as tumor type?

When trying to run the test data provided i get error message 2 with ValueError: No radiological volume for {'timestamp': 0, 'sequence': 'T1-w', 'labels': None, 'space': {'timestamp': 0, 'sequence': 'T1-w'}}.

This is the same error message i get when using my DICOM-data converted into niftii using mricron.

from raidionics.

dbouget avatar dbouget commented on June 12, 2024

Tumor sub-compartments segmentation

I am assuming that you are trying to get the segmentation for the tumor sub-compartments (i.e., tumor, necrosis, and edema), which is the reason why you would need to provide a T1w MRI as input, right? So you have selected Tumor, Necrosis, Edema as Output classes in the Settings under Settings > Preferences > Processing - Segmentation?

As it stands right now, and as I might have hastily released a new version of the software to support the segmentation of sub-compartments, the reporting pipeline should be executed only when running a model that segments just the tumor (i.e., Output classes settings set as Tumor).

That being said, the glioblastoma segmentation that you attempted with your own data should have worked, and it seems that the issue is being triggered during the co-registration of the T1-w MR scan to the T1-CE MR scan. I will look into this issue further as I have so far used only data that were already co-registered, which is a bit lazy of me!

Running the test data

The provided test data are just compatible with the tumor segmentation only models, hence the lack of all four input MR sequences, which explains the error message when trying to run a tumor sub-compartments segmentation model.
I have made a new tutorial video showcasing how to use the test data to generate a glioblastoma segmentation, which assumes that the Output classes settings is set as Tumor.

from raidionics.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.