GithubHelp home page GithubHelp logo

Comments (7)

francopestilli avatar francopestilli commented on July 4, 2024

Hi Paolo.
Andrew and I are working on this. We understand the first portion of the issue. But we are trying to understand what we need to practically to address the following: "The init_tracking* and init_dissection* script should refer to these images in such a way also the tractograms will be in the radiological orientation."

Does this simply mean that:
(1) the same (current) script will seemingly work this way? They will be able to use the new files?
(2) we need to changes something also in the ini_tracking_* and init_dissection_* scripts so that the scripts become compatible with the orientation of the new nifti files?

Thanks for clarifying.
Franco

@andnp @Paolopost

from o3d-code.

andnp avatar andnp commented on July 4, 2024

Started first part with commit 7185db6

from o3d-code.

Paolopost avatar Paolopost commented on July 4, 2024

The scripts to generate the tracking and dissection from the 'fe' structure need to refer the anatomy. We need to be sure that the anatomy file are the one with the proper orientation, it means the one already included in the o3d tree and not the source file of anatomy recovered from the filesystem.

from o3d-code.

francopestilli avatar francopestilli commented on July 4, 2024

Hi Paolo. Thanks for the clarification.
(1) This simply means that we need to change the init_tracking and init_dissection scripts. Correct?

(2) Do you think I need to recreate the FE structures because of this? The FE structures contain the tractograms and the coordinate frames. So I fear that after this change in orientation the FE structures might become out of synch with the anatomy files.

from o3d-code.

francopestilli avatar francopestilli commented on July 4, 2024

Hi @Paolopost is this last question clear to you?

from o3d-code.

Paolopost avatar Paolopost commented on July 4, 2024

I apologize the late reply.

(1) The init_tracking and init_dissection scripts generates "trk" files. "trk" files are embed info on reference anatomy, the association is established at run time with a given anatomy (not necessarily the original one). In this case the revision of the scripts should only take care that the nifti files given in argument as reference anatomy are those "flipped".

(2) The answer to this point is tricky. I'm not 100% sure that we don't need to recompute the FE structures. I believe that independently from this question it would be helpful to define a policy for the sanity check of the orientation of tractography.

from o3d-code.

andnp avatar andnp commented on July 4, 2024

As for (1) the init_tracking and init_dissection scripts do currently grab the reference anatomy from the output of the preprocessing pipeline. So no changes need to be made there.

from o3d-code.

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.