kschan0214 / sepia

Matlab GUI pipeline application for quantitative susceptibility mapping (QSM)
MIT License
50 stars 10 forks source link

STI-Algorithms used in SEPIA = STISuite results ? #20

Closed zoelir729 closed 3 years ago

zoelir729 commented 3 years ago

I have read the closed issue (SEPIA results != STISuite results #4) similar to this one. However, I haven't found a solution and reason like him. Below were my steps. 【single echo】 image

Left was the results obtained by using Sepia (choose STISuite algorithms). The right was performed in STISuite v3.0. The two results were very similar, but I found the Right (STISuite) one was smoother and the left one showed a more coarse appearance. image image

The Infos showed a difference in Intensity Range and others. image

Is there a reason or an error in my operation? (Plus: In terms of the difference in intensity, I think the masks used were not the main reason.)

kschan0214 commented 3 years ago

Hi Zoe,

The closed issue #4 you referred is related to the user defined pipeline (involved data transferring between python and matlab) instead of the issue on the SEPIA's side. So I didn't take a second look on the STI suite implementation in SEPIA as the user reported the final results are identical after fixing his issue.

As SEPIA using the methods from the toolbox directly, I would expect given the same input images/maps, the resulting maps would also be the same. However, there are some intermediate steps in SEPIA that may not presented in the STI suite pipeline. These differences could also make impacts on the final QSM map.

I will try to test this and coming back to you. In the meantime, if you would like to investigate where the differences coming from, I suggest you breaking down the full pipeline into separate steps. By using the same input images (including the signal mask) on each step for both SEPIA and STI suite, and also switch off the utility function (change the 'Removal residual B1' to 'None'), this could give you a better idea where the differences coming from.

P.S. It seems to me you are running QSM processing on high-passed filtered phase. As some of the phase information is lost after the high-pass filtered processing, please be cautious if you intend to use the resulting map for quantitative analysis.

zoelir729 commented 3 years ago

For high-passed filtered phase. Sorry for lacking the basics of SWI. You mean SMV size (mm) ? 12 is large? image

And if I want to perform VSHARP algorithm like this: The variable-kernels sophisticated harmonic artifact reduction for phase data (V-SHARP) algorithm was used for background field removal with spherical kernel radii from 0.75 to 30 mm/maximum radii between 0.75 and 30 mm. ‘VSHARP’ could be set like the below pic. image How to set the same parameter in 'VSHARP (STI suite)' ?

kschan0214 commented 3 years ago

Hi Zoe,

In my test below I couldn't find any significant differences between the results from STI Suite and SEPIA. You can try the attached script as a template for the test on your data.

Left panel: results from STI Suite; right panel: differences between STI suite script vs STI suite in SEPIA STISuite_vs_SEPIA

sepia_vs_STIsuite_template.m.zip

kschan0214 commented 3 years ago

The attached image (assumed to be QSM map) is lack of strong susceptibility contrast in the basal ganglia (see below, red arrows). This is usually an indicator suggesting the input phase image is already high-pass filtered. (For more typical QSM maps you can check on Figure 1 or 5 in https://doi.org/10.1016/j.neuroimage.2020.117611.

126646967-404c58f3-99b4-40ab-82ae-c43e6c99b1d0