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

-f '%p' not working #563

Closed
weberam2 opened this issue Nov 24, 2021 · 2 comments
Closed

-f '%p' not working #563

weberam2 opened this issue Nov 24, 2021 · 2 comments

Comments

@weberam2
Copy link

Describe the bug

Hi Chris,

I have noticed that between versions 2018 Nov 22nd and 2021 Oct 6th, if I run the following on GE dicom files (GE Discovery 750)

dcm2niix -o tmp_dcm2bids/helper -b y -ba y -z y -f '%3s_%f_%p_%t' sourcedata/test6/

I get:

2018:
006_test6_B0map_20190503130133
vs
2021:
006_test6_RESEARCH_-_REGTRJ_20190503130133

So it seems like somewhere the %p option stopped working for these dicom files with the latest?

I am on Ubuntu 20.04

@neurolabusc
Copy link
Collaborator

See the v1.0.20210317 release notes:

File naming behavior of the current stable version is here.

In brief, the current version of dcm2niix has consistent behavior regardless of vendor:

  • %d=description (from 0008,103E)
  • %p=protocol name (from 0018,1030)
  • %z=sequence name (from 0018,0024)

While dcm2niix's behavior is now consistent regardless of manufacturer, be aware that the vendor usage is not. For most manufacturers, a user can edit the protocol name (%p) on the console. However, for GE MRI the protocol name is locked, and the user can only specify the description (%d).

@weberam2
Copy link
Author

THANK YOU!
This will fix my issue, using %d instead of %p :)

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