CEUS Feature Request: B Mode/CEUS Image toggle

[Yuanshan-Wu]

---

name: General Issue
about: Report bugs, request features, or ask questions
title: ''
labels: ''
assignees: ''

Issue Type

• Bug Report
• Feature Request
• Installation Issue
• Question/Help
• Documentation
• Other

Description

The Current CEUS Quantus GUI cannot load B mode and CEUS images at the same time. The old GUI has a button to toggle between CEUS and B mode images for users to draw ROI

Environment (for bugs/installation issues)

• OS:
• Python Version:
• Package Version:
• Installation Method:

Additional Context

For example there is a button to switch between CEUS and B Mode image

[HybridEcho]

Instead of a toggle inbetween i would suggest an overlay with an adaptable transparency. Something similar has been implemented for Clarius, see also: #13

[Yuanshan-Wu]

@OmidChaghaneh @davidspector67 @HybridEcho

I just updated the the transparency slide bar for showing B mode image on top of the CEUS image in branch https://github.com/QuantUS-OpenSource/QuantUS/tree/28-Bmode-CEUS-Image-Toggle based on the #3 branch that Omid used to work on.

Now it looks like something like below:

CEUS base + 0.25*Bmode:

CEUS base + 0.9*Bmode:

The only issue is that the post-processing is only applied to the CEUS image rather than B mode images. Please let me know if you have any suggestions. If no more suggestions, I could create a PR.

[OmidChaghaneh]

Hi Yuanshan,

Nice work. I tested the latest changes and saw that both files are now loading correctly. However, when navigating to the next menu, I noticed the same performance issue we had before.

When comparing it with the last commit of branch #3 (which you created your branch from), this issue does not occur there. I just wanted to report this problem.

Thanks,
Omid

[davidspector67]

Yuanshan, the slider feature looks nice. A UI nitpick would be to center the slider itself on the GUI, but outside of that everything looks good from first glance. Once branch #3 is merged to main, I think you can make a PR.

Omid, can you confirm the specific performance issue you're mentioning?

Thanks,
David

[Yuanshan-Wu]

I notice this performance issue also. I think Omid refers to if we load both B mode and CEUS image, the frame selection bar turns out to be relative laggy between frames. @davidspector67 did you also notice that?

@OmidChaghaneh do you guys have any recommendation to solve this issue?

[OmidChaghaneh]

@davidspector67: that's the same issue which Yuanshan also mentioned it on the next comment.
@Yuanshan-Wu: So far, I have no clue.

[Yuanshan-Wu]

@OmidChaghaneh and @davidspector67 I think the issue is due to the data size. If I load the data with shallower depth, the performance issue is gone.

I suspect the issue is from the post-processing pipeline which post process the entire volume when toggled to different frame.

[OmidChaghaneh]

@Yuanshan-Wu Now I remember... I think it’s also worth taking a look at how the data shape is being handled in this case. As you remember, when loading single files there was also a performance problem, but it was solved by setting the correct data shape for each navigation point. It could be that, because we have loaded two files, it is trying to process or monitor the data shape twice.

[Yuanshan-Wu]

@OmidChaghaneh Thank you for guiding me about that! I have been trying to figure out the performance issue but I still couldn't figure out the issue. May I ask specifically where did you find out the data shape is incorrect?

Is it in the draw_voi_widget?

[Yuanshan-Wu]

I just made a new commit to solve the performance issue. Can you guys try it out once you are free?