search

trustimaging / stride

A modelling and optimisation framework for medical ultrasound
https://www.stride.codes
GNU Affero General Public License v3.0
89 stars 16 forks source link

Poor inversion results when using linear transducers. #65

Closed haoopan closed 4 months ago

haoopan commented 11 months ago

Dear author， Stride is a great piece of work, and I'm following it. First, when I use the transducers with the default elliptical geometry, problem.plot() looks like this: problem1 And the corresponding inversion result is as follows: result1 It looks like the inversion result is good! However, when I changed the transducer geometry to a linear arrangement, problem.plot() looks like this: problem2 And the corresponding inversion result is as follows: result2 You can see that the result is very poor at this point, and it is almost impossible to get any sound velocity distribution. Do you know the reason for this result, and how to make the linear transducer also get a correct inversion result? I'm looking forward your reply!

Yours Sincerely

oscarbates commented 9 months ago

Hi hoopan, we're glad you like the library and thanks for you comment.

Unfortunately, this is not a bug or issue with stride. Reflection sound speed imaging is very difficult and I recommend a literature review if you want to understand this in full