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

fieldmap-free distortion correction #111

Closed
h-w-k opened this issue Jun 12, 2020 · 4 comments · Fixed by #153
Closed

fieldmap-free distortion correction #111

h-w-k opened this issue Jun 12, 2020 · 4 comments · Fixed by #153
Labels
depends: SDCFlows effort: high This task will probably require many person-hours impact: high This contribution/idea will help a lot of people
Milestone

Comments

@h-w-k
Copy link

h-w-k commented Jun 12, 2020

  • dmriprep version: 0.2.2
  • Python version: 2.7.15
  • Operating System: centos 6

Dear all,
I am writing to seek your expertise and advices on fieldmap-less distortion correction in DMRIPREP.

I executed the following commandline.
“singularity run --cleanenv -B /home/BIDS_output:/work -B /home/DMRIPREP_output:/output -B /home:/main /home/dmriprep-0.2.2.simg /work /output participant --participant_label sub-2475376 --fs-license-file /main/license.txt --use-syn-sdc -skip-bids-validation -w /main/WORK”

It seems no processing in the distortion correction as shown in the report.html

“Errors
No errors to report!”

“Diffusion
Average b=0 that serves for reference in early preprocessing steps.”

Then no more steps and no dwi folder is generated.

May i know how to make it successfully run?

In addition, the following remark is shown in the log throughout the whole processing.

“200608-08:24:28,893 nipype.utils WARNING:
Could not check for version updates:
Connection to server could not be made”

Would it affect the products? How to fix it?

Thank you very much.

Best regards,
Winky

@oesteban
Copy link
Member

Hi Winky, currently we're a bit far from being able to run any sort of fieldmap-less distortion correction. We'll work on a better SDC integration as soon as possible.

@h-w-k
Copy link
Author

h-w-k commented Jun 12, 2020

Hi Oesteban, thank you very much for your reply and all the effort from the development team.

I am working on the project that does not include reversed DTI for distortion correction. Now, I try to go through the fieldmap-less distortion correction in DTI (using ANTs and T1w image) stated in the following paper before DMRIPREP is enriched. Do you have any suggestions or advices?

Evaluation of Field Map and Nonlinear Registration Methods for Correction of Susceptibility Artifacts in Diffusion MRI, available at
https://www.frontiersin.org/articles/10.3389/fninf.2017.00017/full

@oesteban oesteban added this to the 20.0.0 milestone Oct 13, 2020
@effigies
Copy link
Member

@oesteban I see some syn-related parameters in the config. Is this enabled?

@oesteban
Copy link
Member

Unfortunately, it is not.

@oesteban oesteban modified the milestones: 20.0.0, 0.5.0 Dec 10, 2020
@oesteban oesteban added effort: high This task will probably require many person-hours impact: high This contribution/idea will help a lot of people depends: SDCFlows labels Jan 27, 2021
oesteban added a commit that referenced this issue Jan 27, 2021
Currently, this is blocked by the absence of a general solution to the
reference generation issue (see nipreps/niworkflows#600).

Once adequate DWI references are connected to the estimation workflow,
this feature should work out.
We can test the new feature with ds000206.

Resolves: #111.
oesteban added a commit that referenced this issue Jan 27, 2021
Currently, this is blocked by the absence of a general solution to the
reference generation issue (see nipreps/niworkflows#600).

Once adequate DWI references are connected to the estimation workflow,
this feature should work out.
We can test the new feature with ds000206.

Resolves: #111.
oesteban added a commit that referenced this issue Jan 27, 2021
Currently, this is blocked by the absence of a general solution to the
reference generation issue (see nipreps/niworkflows#600).

Once adequate DWI references are connected to the estimation workflow,
this feature should work out.
We can test the new feature with ds000206.

Resolves: #111.
oesteban added a commit that referenced this issue Jan 27, 2021
Currently, this is blocked by the absence of a general solution to the
reference generation issue (see nipreps/niworkflows#601).

Once adequate DWI references are connected to the estimation workflow,
this feature should work out.
We can test the new feature with ds000206.

Resolves: #111.
oesteban added a commit that referenced this issue Feb 8, 2021
Currently, this is blocked by the absence of a general solution to the
reference generation issue (see nipreps/niworkflows#601).

Once adequate DWI references are connected to the estimation workflow,
this feature should work out.
We can test the new feature with ds000206.

Resolves: #111.
oesteban added a commit that referenced this issue Feb 8, 2021
Currently, this is blocked by the absence of a general solution to the
reference generation issue (see nipreps/niworkflows#601).

Once adequate DWI references are connected to the estimation workflow,
this feature should work out.
We can test the new feature with ds000206.

Resolves: #111.
oesteban added a commit that referenced this issue Mar 11, 2021
Currently, this is blocked by the absence of a general solution to the
reference generation issue (see nipreps/niworkflows#601).

Once adequate DWI references are connected to the estimation workflow,
this feature should work out.
We can test the new feature with ds000206.

Resolves: #111.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
depends: SDCFlows effort: high This task will probably require many person-hours impact: high This contribution/idea will help a lot of people
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants