dke-questions > why the console window still reads "Sequence name must contain 'ep'"even though my data is based on EPI sequence and the file name is ep2d_diff_log2_iso20_free42_B1000_p2?
Showing 1-5 of 5 posts
Display:
Results per page:
Apr 26, 2018  09:04 AM | Xinman Liu
why the console window still reads "Sequence name must contain 'ep'"even though my data is based on EPI sequence and the file name is ep2d_diff_log2_iso20_free42_B1000_p2?
Hello, everyone.
I wonder if anyone come across the same kind of problems. My data is based on EPI sequence and the file name is ep2d_diff_log2_iso20_free42_B1000_p2. But when I begin to run DKE with the data, the console window reads as followings, 
% Thu Apr 26 10:53:05 AM
studydir = 'F:\P5';
subject_list = {''};
preprocess_options.format = 'dicom';
preprocess_options.navg = 1;
preprocess_options.extra_b0 = 0;
preprocess_options.coreg_flag = 1;
preprocess_options.series_description = {'ep2d_diff_log2_iso20_free42_B1000_p2'};
fn_img_prefix = 'rdki';
bval = [0 1000 2000];
ndir = 85;
idx_1st_img = 1;
Kmin = 0;
NKmax = 3;
Kmin_final = 0;
Kmax_final = 3;
T = 50;
find_brain_mask_flag = 1;
dki_method.no_tensor = 0;
dki_method.linear_weighting = 1;
dki_method.linear_constrained = 1;
dki_method.nonlinear = 0;
dki_method.linear_violations = 0;
dki_method.robust_option = 0;
dki_method.noise_tolerance = 0.09;
dti_method.dti_flag = 0;
dti_method.dti_only = 0;
dti_method.no_tensor = 0;
dti_method.linear_weighting = 1;
dti_method.b_value = 1e+003;
dti_method.directions{1} = [1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85];
dti_method.robust_option = 0;
dti_method.noise_tolerance = 0.09;
fn_noise = '';
fwhm_img = [3.375 3.375 3.375];
fwhm_noise = [0 0 0];
median_filter_method = 2;
map_interpolation_method.flag = 0;
map_interpolation_method.order = 1;
map_interpolation_method.resolution = 1;
fn_gradients = 'F:/Patient1/bvecnew.txt';
idx_gradients{1} = [1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85];
idx_gradients{2} = [1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85];

command line: dke DKEParameters.dat
Diffusional Kurtosis Estimator (DKE) version 2.6.0, February 2015
Start date and time: April 26, 2018 10:53:18
Diffusional Kurtosis Estimator (DKE) version 2.6.0
Converting input DICOM images to NIfTI... Error using spm_dicom_convert_series_description>nii_name (line 1186)
Invalid sequence name in DICOM header! Sequence name must contain 'ep'!
And my data is consist of altogether 86 DICOMs.
Anyone knows what is exactly wrong with the data? Or is it a bug of DKE software?
Could anyone please give me some suggestions? Thank you very much.
P.S the picture attached is how the whole process looks like on my computer.


Best regards,
Xinman


Attachment: ep exist.jpg
Apr 26, 2018  11:04 AM | Emilie McKinnon - MUSC
RE: why the console window still reads "Sequence name must contain 'ep'"even though my data is based on EPI sequence and the file name is ep2d_diff_log2_iso20_free42_B1000_p2?
Hi Xibman,

There is a difference between series description ( which obviously contains ep like you stated ) and sequence name. Can you use a dicom reader to check what is stored in the header field sequence name? This might help us get to the bottem of this. My gut feeling says you probably have an automatically generated fa map or ADC map in your series.

Thanks,
Emilie
Apr 26, 2018  01:04 PM | Xinman Liu
RE: why the console window still reads "Sequence name must contain 'ep'"even though my data is based on EPI sequence and the file name is ep2d_diff_log2_iso20_free42_B1000_p2?
Hello, Emilie, Thank you for your quick reply.  I'm somewhat desperate.
So I use Matlab to get the details, and I input info=dicominfo('filename');to get the results, and it reads as followings
Filename: 'F:\P6\1.3.12.2.1107.5.2.32.35420.2018010410543453162206454.dcm'
FileModDate: '04-1月-2018 11:40:12'
FileSize: 2210748
Format: 'DICOM'
FormatVersion: 3
Width: 1024
Height: 1024
BitDepth: 12
ColorType: 'grayscale'
FileMetaInformationGroupLength: 178
FileMetaInformationVersion: [2×1 uint8]
MediaStorageSOPClassUID: '1.2.840.10008.5.1.4.1.1.4'
MediaStorageSOPInstanceUID: '1.3.12.2.1107.5.2.32.35420.2018010410543453162206454'
TransferSyntaxUID: '1.2.840.10008.1.2.1'
ImplementationClassUID: '1.3.12.2.1107.5.2'
ImplementationVersionName: 'MR_VB17A'
SpecificCharacterSet: 'ISO_IR 100'
ImageType: 'ORIGINAL\PRIMARY\DIFFUSION\NONE\ND\NORM\MOSAIC'
InstanceCreationDate: '20180104'
InstanceCreationTime: '105434.953000'
SOPClassUID: '1.2.840.10008.5.1.4.1.1.4'
SOPInstanceUID: '1.3.12.2.1107.5.2.32.35420.2018010410543453162206454'
StudyDate: '20180104'
SeriesDate: '20180104'
AcquisitionDate: '20180104'
ContentDate: '20180104'
StudyTime: '100554.031000'
SeriesTime: '105434.937000'
AcquisitionTime: '105429.440000'
ContentTime: '105434.953000'
AccessionNumber: ''
Modality: 'MR'
Manufacturer: 'SIEMENS'

ReferringPhysicianName: [1×1 struct]
StationName: 'MEDPC'
StudyDescription: 'NCH^Study'
SeriesDescription: 'ep2d_diff_log2_iso20_free42_B1000_p2'
InstitutionalDepartmentName: 'Department'
PerformingPhysicianName: [1×1 struct]
OperatorName: [1×1 struct]
ManufacturerModelName: 'TrioTim'
ReferencedImageSequence: [1×1 struct]
PatientName: [1×1 struct]
PatientID: 'NCH_PROGLIO_001'
PatientBirthDate: '19720101'
PatientSex: 'M'
PatientAge: '046Y'
PatientSize: 1.8600
PatientWeight: 85
ScanningSequence: 'EP'
SequenceVariant: 'SK\SP'
ScanOptions: 'PFP\FS'
MRAcquisitionType: '2D'
SequenceName: 'js_b0'
AngioFlag: 'N'
SliceThickness: 2
RepetitionTime: 8700
EchoTime: 104
NumberOfAverages: 1
ImagingFrequency: 123.2122
ImagedNucleus: '1H'
EchoNumber: 1
MagneticFieldStrength: 3
SpacingBetweenSlices: 2.0000
NumberOfPhaseEncodingSteps: 102
EchoTrainLength: 1
PercentSampling: 100
PercentPhaseFieldOfView: 100
PixelBandwidth: 1502
DeviceSerialNumber: '35420'
SoftwareVersion: 'syngo MR B17'
ProtocolName: 'ep2d_diff_log2_iso20_free42_B1000_p2'
TransmitCoilName: 'Body'
AcquisitionMatrix: [4×1 uint16]
InPlanePhaseEncodingDirection: 'COL'
FlipAngle: 90
VariableFlipAngleFlag: 'N'
SAR: 0.2206
dBdt: 0
PatientPosition: 'HFS'
Private_0019_10xx_Creator: 'SIEMENS MR HEADER'
Private_0019_1008: 'IMAGE NUM 4'
Private_0019_1009: '1.0'
Private_0019_100a: 60
Private_0019_100b: 37.5000
Private_0019_100c: 0
Private_0019_100d: 'DIRECTIONAL'
Private_0019_100f: 'Fast'
Private_0019_1011: 'No'
Private_0019_1012: [3×1 int32]
Private_0019_1013: [3×1 int32]
Private_0019_1014: [3×1 double]
Private_0019_1015: [3×1 double]
Private_0019_1016: 4.3675
Private_0019_1017: 1
Private_0019_1018: 2600
Private_0019_1028: 20.8330
Private_0019_1029: [60×1 double]
StudyInstanceUID: '1.3.12.2.1107.5.2.32.35420.30000018010409051256200000005'
SeriesInstanceUID: '1.3.12.2.1107.5.2.32.35420.2018010410535497958406125.0.0.0'
StudyID: '1'
SeriesNumber: 9
AcquisitionNumber: 1
InstanceNumber: 1
ImagePositionPatient: [3×1 double]
ImageOrientationPatient: [6×1 double]
FrameOfReferenceUID: '1.3.12.2.1107.5.2.32.35420.1.20180104101902734.0.0.0'
PositionReferenceIndicator: ''
SliceLocation: -42.0469
SamplesPerPixel: 1
PhotometricInterpretation: 'MONOCHROME2'
Rows: 1024
Columns: 1024
PixelSpacing: [2×1 double]
BitsAllocated: 16
BitsStored: 12
HighBit: 11
PixelRepresentation: 0
SmallestImagePixelValue: 0
LargestImagePixelValue: 4074
WindowCenter: 524
WindowWidth: 1143
WindowCenterWidthExplanation: 'Algo1'
Private_0029_10xx_Creator: 'SIEMENS CSA HEADER'
Private_0029_11xx_Creator: 'SIEMENS MEDCOM HEADER2'
Private_0029_1008: 'IMAGE NUM 4'
Private_0029_1009: '20180104'
Private_0029_1010: [11940×1 uint8]
Private_0029_1018: 'MR'
Private_0029_1019: '20180104'
Private_0029_1020: [92828×1 uint8]
Private_0029_1160: 'com'
RequestedProcedureDescription: 'NCH Study'
PerformedProcedureStepStartDate: '20180104'
PerformedProcedureStepStartTime: '100554.093000'
PerformedProcedureStepID: 'MR20180104100554'
PerformedProcedureStepDescription: 'NCH^Study'
Private_0051_10xx_Creator: 'SIEMENS MR HEADER'
Private_0051_1008: 'IMAGE NUM 4'
Private_0051_1009: '1.0'
Private_0051_100a: 'TA 00.03'
Private_0051_100b: '128p*128'
Private_0051_100c: 'FoV 2048*2048'
Private_0051_100e: 'Tra>Cor(1.9)>Sag(0.6)'
Private_0051_100f: 'T:HEA;HEP'
Private_0051_1011: 'p2'
Private_0051_1012: 'TP 0'
Private_0051_1013: '+LPH'
Private_0051_1016: 'p2 DIFFUSION/NONE/ND/NORM'
Private_0051_1017: 'SL 2.0'
Private_0051_1019: 'A1/PFP/FS'
StorageMediaFileSetUID: '1.3.12.2.1107.5.2.32.35420.30010018010409384693700000001'
IconImageSequence: [1×1 struct]

So I have to say, I'm not sure about what exactly header field sequence is. If the information above did not help, could you please tell me in what way can I get the name of it? I use RadiAnt as DICOM reader. And I search a little bit but didn't get much hope about how can I get the name of header field sequence.

Best regards,
Xinman
Apr 26, 2018  02:04 PM | Emilie McKinnon - MUSC
RE: why the console window still reads "Sequence name must contain 'ep'"even though my data is based on EPI sequence and the file name is ep2d_diff_log2_iso20_free42_B1000_p2?
Hi Xinman, 

Your sequence name is : SequenceName: 'js_b0'. See how this does not include "ep", this is what is causing the error. I see you have a timtrio, who created that sequence?  Compare this dicom info with one of the other data sets that you have and where DKE runs just fine. 

Hope this helps, 
Emilie
Apr 27, 2018  05:04 AM | Xinman Liu
RE: why the console window still reads "Sequence name must contain 'ep'"even though my data is based on EPI sequence and the file name is ep2d_diff_log2_iso20_free42_B1000_p2?
Hello, Emilie. 
You are right. So I check the previous data, with which I successfully run DKE. And the sequence name is SequenceName: '*ep_b0'.
Actually the technician of our hospital create the sequence, but I don't know exactly who. But has timtrio anything to do with the problem? 
And do I need to rescan the patient? Or are there any ways that I can change the sequence name so that I can use the data?
Could you please give me some suggestions?
Best regards,
Xinman