[CCPPETMR/SIRF] examples/Python/MR/acquisition_data.py (#166)

0 views
Skip to first unread message

David Atkinson

unread,
May 6, 2018, 8:29:30 AM5/6/18
to CCPPETMR/SIRF, Subscribed

Incorrect script name in the Usage comment.

Also, where is the default for the range set, and why the choice of (254, 258)?

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Kris Thielemans

unread,
May 9, 2018, 11:04:25 AM5/9/18
to CCPPETMR/SIRF, Subscribed

@ckolbPTB, can you comment?

evgueni-ovtchinnikov

unread,
May 10, 2018, 5:21:28 AM5/10/18
to CCPPETMR/SIRF, Subscribed

to show the boundary between repetitions - say, for the range (250,254) all data would be zeros except encoding - not very illuminative
docstrings corrected

evgueni-ovtchinnikov

unread,
May 10, 2018, 5:21:29 AM5/10/18
to CCPPETMR/SIRF, Subscribed

Closed #166.

David Atkinson

unread,
May 10, 2018, 5:41:38 AM5/10/18
to CCPPETMR/SIRF, Subscribed

This range sets the variable 'where' which then affects a number of print statements but not any numerical output?
At first sight the docstring is confusing - to me it implies the range of phase encode lines (readouts) will be restricted which would result in junk images.

evgueni-ovtchinnikov

unread,
May 10, 2018, 5:51:53 AM5/10/18
to CCPPETMR/SIRF, Subscribed

Yes, you are right, no data is affected.
To remind you, the docstring says:
-r , --range= range of readouts to examine as string '(a,b)'
If you find 'readouts to examine' not clear enough, please suggest a better wording (I was after a concise one).

Reply all
Reply to author
Forward
0 new messages