How to calculate Temporal Resolution without DICOM header?
How can I calculate the Temporal Resolution of MRI sequence if it's not written in DICOM header?
What other DICOM information can I use to calculate out the temporal resolution?
It might worth mentioning that it's a 3D sequence. I have 20 slices and each slice 99 time points.
image-processing dicom
edited Nov 24 '18 at 11:59
Amit Joshi
5,49252652
asked Nov 20 '18 at 9:42
user161260user161260
112
add a comment |
How can I calculate the Temporal Resolution of MRI sequence if it's not written in DICOM header?
What other DICOM information can I use to calculate out the temporal resolution?
It might worth mentioning that it's a 3D sequence. I have 20 slices and each slice 99 time points.
image-processing dicom
edited Nov 24 '18 at 11:59
Amit Joshi
5,49252652
asked Nov 20 '18 at 9:42
user161260user161260
112
Short answer: not at all. Long answer: If you could post a DICOM dump of the MRI dataset (one slice is sufficient), we could have a closer look at it.
– kritzel_sw
Nov 20 '18 at 11:27
I attahed a screenshot of the DICOM
– user161260
Nov 20 '18 at 14:35
Your did not post the whole dump. If the slices are not temporarily related, the time attributes are not mandatory. So if you do not find any attributes like Content Time (0008,0033) or Acquisition Time (0008, 0022), I do not see a chance to determine the temporal resolution. Unfortunately your screenshots do not include the group 0008 elements so I cannot tell from the information provided.
– kritzel_sw
Nov 20 '18 at 15:33
I attached the information you asked for. Is temporal resolution = acquisition time / number of slices
– user161260
Nov 20 '18 at 15:39
I have edited your question. Your title was contradicting with your question body. Please verify the edit. Removed close-vote and up-voted. Please refer SO help for how to write good question.
– Amit Joshi
Nov 24 '18 at 12:01
add a comment |
How can I calculate the Temporal Resolution of MRI sequence if it's not written in DICOM header?
What other DICOM information can I use to calculate out the temporal resolution?
It might worth mentioning that it's a 3D sequence. I have 20 slices and each slice 99 time points.
image-processing dicom
edited Nov 24 '18 at 11:59
Amit Joshi
5,49252652
asked Nov 20 '18 at 9:42
user161260user161260
112
How can I calculate the Temporal Resolution of MRI sequence if it's not written in DICOM header?
What other DICOM information can I use to calculate out the temporal resolution?
It might worth mentioning that it's a 3D sequence. I have 20 slices and each slice 99 time points.
image-processing dicom
image-processing dicom
edited Nov 24 '18 at 11:59
Amit Joshi
5,49252652
asked Nov 20 '18 at 9:42
user161260user161260
112
edited Nov 24 '18 at 11:59
Amit Joshi
5,49252652
asked Nov 20 '18 at 9:42
user161260user161260
112
edited Nov 24 '18 at 11:59
Amit Joshi
5,49252652
edited Nov 24 '18 at 11:59
Amit Joshi
5,49252652
edited Nov 24 '18 at 11:59
Amit Joshi
5,49252652
5,49252652
asked Nov 20 '18 at 9:42
user161260user161260
112
asked Nov 20 '18 at 9:42
user161260user161260
112
asked Nov 20 '18 at 9:42
user161260user161260
112
112
Short answer: not at all. Long answer: If you could post a DICOM dump of the MRI dataset (one slice is sufficient), we could have a closer look at it.
– kritzel_sw
Nov 20 '18 at 11:27
I attahed a screenshot of the DICOM
– user161260
Nov 20 '18 at 14:35
Your did not post the whole dump. If the slices are not temporarily related, the time attributes are not mandatory. So if you do not find any attributes like Content Time (0008,0033) or Acquisition Time (0008, 0022), I do not see a chance to determine the temporal resolution. Unfortunately your screenshots do not include the group 0008 elements so I cannot tell from the information provided.
– kritzel_sw
Nov 20 '18 at 15:33
I attached the information you asked for. Is temporal resolution = acquisition time / number of slices
– user161260
Nov 20 '18 at 15:39
I have edited your question. Your title was contradicting with your question body. Please verify the edit. Removed close-vote and up-voted. Please refer SO help for how to write good question.
– Amit Joshi
Nov 24 '18 at 12:01
add a comment |
Short answer: not at all. Long answer: If you could post a DICOM dump of the MRI dataset (one slice is sufficient), we could have a closer look at it.
– kritzel_sw
Nov 20 '18 at 11:27
I attahed a screenshot of the DICOM
– user161260
Nov 20 '18 at 14:35
Your did not post the whole dump. If the slices are not temporarily related, the time attributes are not mandatory. So if you do not find any attributes like Content Time (0008,0033) or Acquisition Time (0008, 0022), I do not see a chance to determine the temporal resolution. Unfortunately your screenshots do not include the group 0008 elements so I cannot tell from the information provided.
– kritzel_sw
Nov 20 '18 at 15:33
I attached the information you asked for. Is temporal resolution = acquisition time / number of slices
– user161260
Nov 20 '18 at 15:39
I have edited your question. Your title was contradicting with your question body. Please verify the edit. Removed close-vote and up-voted. Please refer SO help for how to write good question.
– Amit Joshi
Nov 24 '18 at 12:01
Short answer: not at all. Long answer: If you could post a DICOM dump of the MRI dataset (one slice is sufficient), we could have a closer look at it.
– kritzel_sw
Nov 20 '18 at 11:27
Short answer: not at all. Long answer: If you could post a DICOM dump of the MRI dataset (one slice is sufficient), we could have a closer look at it.
– kritzel_sw
Nov 20 '18 at 11:27
I attahed a screenshot of the DICOM
– user161260
Nov 20 '18 at 14:35
I attahed a screenshot of the DICOM
– user161260
Nov 20 '18 at 14:35
Your did not post the whole dump. If the slices are not temporarily related, the time attributes are not mandatory. So if you do not find any attributes like Content Time (0008,0033) or Acquisition Time (0008, 0022), I do not see a chance to determine the temporal resolution. Unfortunately your screenshots do not include the group 0008 elements so I cannot tell from the information provided.
– kritzel_sw
Nov 20 '18 at 15:33
Your did not post the whole dump. If the slices are not temporarily related, the time attributes are not mandatory. So if you do not find any attributes like Content Time (0008,0033) or Acquisition Time (0008, 0022), I do not see a chance to determine the temporal resolution. Unfortunately your screenshots do not include the group 0008 elements so I cannot tell from the information provided.
– kritzel_sw
Nov 20 '18 at 15:33
I attached the information you asked for. Is temporal resolution = acquisition time / number of slices
– user161260
Nov 20 '18 at 15:39
I attached the information you asked for. Is temporal resolution = acquisition time / number of slices
– user161260
Nov 20 '18 at 15:39
I have edited your question. Your title was contradicting with your question body. Please verify the edit. Removed close-vote and up-voted. Please refer SO help for how to write good question.
– Amit Joshi
Nov 24 '18 at 12:01
I have edited your question. Your title was contradicting with your question body. Please verify the edit. Removed close-vote and up-voted. Please refer SO help for how to write good question.
– Amit Joshi
Nov 24 '18 at 12:01
add a comment |
1 Answer
1
active
oldest
votes
First: The encoding of the time values looks more than weird. It does not conform to DICOM encoding rules. See: PS3.5, Table Table 6.2-1. DICOM Value Representations
This may either be a wrong encoding in the DICOM file or by an issue in the dump tool you are using. The values should read:
HH.MM.SS.FFFFFF where HH is hours, MM is minutes, SS is seconds and FFFFFF the microsecond fraction. Parts of it may be omitted, so HH.MM would also be valid but a value of "69481.000" does not match this pattern at all.
In general, the Acquisition Time (0008, 0032) is the attribute I would recommend to consider since it is "The time the acquisition of data that resulted in this image started".
How the "temporal resolution" should be calculated very much depends on what you would define the "temporal resolution" as. If you want to know the temporal distance between two adjacent slices, I would recommend to sort the images along their Slice Location (0020,1041) and calculate the difference between their Acquisition Times.
If you want to average out rounding errors, it might be worth consideration to calculate the difference of Acquisition Time between the first and the last slice and divide it by the number of slices.
answered Nov 21 '18 at 6:48
kritzel_swkritzel_sw
2,315722
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53390131%2fhow-to-calculate-temporal-resolution-without-dicom-header%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
First: The encoding of the time values looks more than weird. It does not conform to DICOM encoding rules. See: PS3.5, Table Table 6.2-1. DICOM Value Representations
This may either be a wrong encoding in the DICOM file or by an issue in the dump tool you are using. The values should read:
HH.MM.SS.FFFFFF where HH is hours, MM is minutes, SS is seconds and FFFFFF the microsecond fraction. Parts of it may be omitted, so HH.MM would also be valid but a value of "69481.000" does not match this pattern at all.
In general, the Acquisition Time (0008, 0032) is the attribute I would recommend to consider since it is "The time the acquisition of data that resulted in this image started".
How the "temporal resolution" should be calculated very much depends on what you would define the "temporal resolution" as. If you want to know the temporal distance between two adjacent slices, I would recommend to sort the images along their Slice Location (0020,1041) and calculate the difference between their Acquisition Times.
If you want to average out rounding errors, it might be worth consideration to calculate the difference of Acquisition Time between the first and the last slice and divide it by the number of slices.
answered Nov 21 '18 at 6:48
kritzel_swkritzel_sw
2,315722
add a comment |
First: The encoding of the time values looks more than weird. It does not conform to DICOM encoding rules. See: PS3.5, Table Table 6.2-1. DICOM Value Representations
This may either be a wrong encoding in the DICOM file or by an issue in the dump tool you are using. The values should read:
HH.MM.SS.FFFFFF where HH is hours, MM is minutes, SS is seconds and FFFFFF the microsecond fraction. Parts of it may be omitted, so HH.MM would also be valid but a value of "69481.000" does not match this pattern at all.
In general, the Acquisition Time (0008, 0032) is the attribute I would recommend to consider since it is "The time the acquisition of data that resulted in this image started".
How the "temporal resolution" should be calculated very much depends on what you would define the "temporal resolution" as. If you want to know the temporal distance between two adjacent slices, I would recommend to sort the images along their Slice Location (0020,1041) and calculate the difference between their Acquisition Times.
If you want to average out rounding errors, it might be worth consideration to calculate the difference of Acquisition Time between the first and the last slice and divide it by the number of slices.
answered Nov 21 '18 at 6:48
kritzel_swkritzel_sw
2,315722
add a comment |
First: The encoding of the time values looks more than weird. It does not conform to DICOM encoding rules. See: PS3.5, Table Table 6.2-1. DICOM Value Representations
This may either be a wrong encoding in the DICOM file or by an issue in the dump tool you are using. The values should read:
HH.MM.SS.FFFFFF where HH is hours, MM is minutes, SS is seconds and FFFFFF the microsecond fraction. Parts of it may be omitted, so HH.MM would also be valid but a value of "69481.000" does not match this pattern at all.
In general, the Acquisition Time (0008, 0032) is the attribute I would recommend to consider since it is "The time the acquisition of data that resulted in this image started".
How the "temporal resolution" should be calculated very much depends on what you would define the "temporal resolution" as. If you want to know the temporal distance between two adjacent slices, I would recommend to sort the images along their Slice Location (0020,1041) and calculate the difference between their Acquisition Times.
If you want to average out rounding errors, it might be worth consideration to calculate the difference of Acquisition Time between the first and the last slice and divide it by the number of slices.
answered Nov 21 '18 at 6:48
kritzel_swkritzel_sw
2,315722
First: The encoding of the time values looks more than weird. It does not conform to DICOM encoding rules. See: PS3.5, Table Table 6.2-1. DICOM Value Representations
This may either be a wrong encoding in the DICOM file or by an issue in the dump tool you are using. The values should read:
HH.MM.SS.FFFFFF where HH is hours, MM is minutes, SS is seconds and FFFFFF the microsecond fraction. Parts of it may be omitted, so HH.MM would also be valid but a value of "69481.000" does not match this pattern at all.
In general, the Acquisition Time (0008, 0032) is the attribute I would recommend to consider since it is "The time the acquisition of data that resulted in this image started".
How the "temporal resolution" should be calculated very much depends on what you would define the "temporal resolution" as. If you want to know the temporal distance between two adjacent slices, I would recommend to sort the images along their Slice Location (0020,1041) and calculate the difference between their Acquisition Times.
If you want to average out rounding errors, it might be worth consideration to calculate the difference of Acquisition Time between the first and the last slice and divide it by the number of slices.
answered Nov 21 '18 at 6:48
kritzel_swkritzel_sw
2,315722
answered Nov 21 '18 at 6:48
kritzel_swkritzel_sw
2,315722
answered Nov 21 '18 at 6:48
kritzel_swkritzel_sw
2,315722
answered Nov 21 '18 at 6:48
kritzel_swkritzel_sw
2,315722
2,315722
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53390131%2fhow-to-calculate-temporal-resolution-without-dicom-header%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Short answer: not at all. Long answer: If you could post a DICOM dump of the MRI dataset (one slice is sufficient), we could have a closer look at it.
– kritzel_sw
Nov 20 '18 at 11:27
I attahed a screenshot of the DICOM
– user161260
Nov 20 '18 at 14:35
Your did not post the whole dump. If the slices are not temporarily related, the time attributes are not mandatory. So if you do not find any attributes like Content Time (0008,0033) or Acquisition Time (0008, 0022), I do not see a chance to determine the temporal resolution. Unfortunately your screenshots do not include the group 0008 elements so I cannot tell from the information provided.
– kritzel_sw
Nov 20 '18 at 15:33
I attached the information you asked for. Is temporal resolution = acquisition time / number of slices
– user161260
Nov 20 '18 at 15:39
I have edited your question. Your title was contradicting with your question body. Please verify the edit. Removed close-vote and up-voted. Please refer SO help for how to write good question.
– Amit Joshi
Nov 24 '18 at 12:01