Drive the input signals « k-Wave User Forum

k-Wave User Forum » General Acoustics » Ultrasound Simulations

Drive the input signals

(11 posts) (3 voices)

Started 9 years ago by gigi
Latest reply from JOKEjoe

gigi

Member
Joined: Oct '14
Posts: 12

Hi All, Hi Dr. Cox and Dr. Treeby,

The example "example_us_b_mode_linear_transducer",

% ...illustrates how k-Wave can be used for the simulation of
% B-mode ultrasound images (including tissue harmonic imaging) analogous to
% those produced by a modern diagnostic ultrasound scanner. It builds on
% the Defining An Ultrasound Transducer, Simulating Ultrasound Beam
% Patterns, and Using An Ultrasound Transducer As A Sensor examples.

just to use the same words of the authors :-)

The script in the RUN SIMULATION session is principally constituted by a loop on the number of scan lines (in this case 96), inside it is performed the generation of a phantom and contextually it is applied the
scan_lines method;

At the input of kspaceFirstOrder3D function we have as source and as output the same transducer object

kspaceFirstOrder3D(kgrid, medium, transducer, transducer, input_args{:});

For what concern the output we have a sensor_data matrix of nxm elements
Now my question, every one single signal received it is generated by only one active element at a time?
I understand that the simulation is performed as below.
If we have 32 active elements, the first one element release the input pulse and register the returned pulse, after this, in sequence, the second element release the input pulse and register the returned pulse, the third element release the input pulse and register the returned pulse and so on...
until all 32 signals were recorded, it is true?

I would like to change the things in way to register with all 32 elements the signal that come from only one element, and choosing from time to time which element or which group of elements will be active in input.
At the limit it could have the received signal for each combination of the elements transmitters and receivers (openings full scan), where it will sequentially for each transmitting element all the receiving elements are illuminated. That is, if I for example, an array of 32 elements, for each of them which emits a pulse, it will have 32 that receive up to cover all combinations to have a total of 1024 combinations.

I think that it will be possible to do this putting the
kspaceFirstOrder3D inside a inner loop (32 or different number_of_active_elements iterations) after defining a new object transducer ie using a transducer_input (that will change inside at the loop) as input and a transducer_output object as output,
it will be something like this:

for i=1:step:number_of_elements

transducer1.mask(i) = 1;

sensor_data = kspaceFirstOrder3D(kgrid, medium, transducer_input(i), transducer_output, input_args{:}).

end

but maybe there is a solution more smart than this mine...

How can I do it?

I hope that my questions are clear.

thanks a lot

Gg

Posted 9 years ago #
gigi

Member
Joined: Oct '14
Posts: 12

I apologize but I forget to tell that

what are N and M in the NxM matrix:

N is the number of active elements and M is the number of samples

thanks a lot.

Gg

Posted 9 years ago #
gigi

Member
Joined: Oct '14
Posts: 12

I apologize,
but I wrote transducer1.mask(i) = 1; but was transducer_input.mask

thanks a lot.

Gg

Posted 9 years ago #

gigi

Member
Joined: Oct '14
Posts: 12

Dear All,

below there is the code that I wrote,
that has some problem because my output (sensor_data) is full of NAN....

for scan_line_index = 1:number_scan_lines

        % update the command line status
        disp('');
        disp(['Computing scan line ' num2str(scan_line_index) ' of ' num2str(number_scan_lines)]);

        % load the current section of the medium
        medium.sound_speed = sound_speed_map(:, medium_position:medium_position + Ny - 1, :);
        medium.density = density_map(:, medium_position:medium_position + Ny - 1, :);

        % run the simulation
	    for index_active_element=1:transducer.number_elements

            transducer1.active_elements(index_active_element) = 1;

            sensor_data = kspaceFirstOrder3D(kgrid, medium, transducer1, transducer, input_args{:});

            if save_mat_files
               file_name = sprintf('examples_us_pre_beamforming_sensor_data_full_scan_aperture_%s_tr_%s', num2str(scan_line_index), num2str(index_active_element));
               cmd=['save ',file_name,'.mat sensor_data'];
               disp(cmd)
               eval(cmd);
            end

            transducer1.active_elements(index_active_element) = 0;
	    end                

%       extract the scan line from the sensor data
%       scan_lines(scan_line_index, :) = transducer.scan_line(sensor_data);

        % update medium position
        medium_position = medium_position + transducer.element_width;

    end

Posted 9 years ago #

Bradley Treeby

Developer
Joined: Mar '10
Posts: 1,640

Hi Gg,

To answer your first question, the simulation is performed a little differently than how you describe. All 32 elements are switched on at once for both transmit and receive, and are used to form a single scan line. There is a detailed explanation of how this works in the html help for the example in MATLAB (you can also access this online). If you want to transmit and receive on different numbers or configurations of elements, then you need to define two different objects of the kWaveTransducer class.

Hope that helps,

Brad.

Posted 9 years ago #
gigi

Member
Joined: Oct '14
Posts: 12

Hi Brad,

Thanks a lot for you answer,
but for me is not clear if the output signal registered by one element is the result of the superposition of 32 signals that come from 32 transmitting elements at once or no.
Can you explain me this ?

To change the transmit and receive configuration I defined two different objects of the kWaveTransducer, I posted the code before your answer, but I have a lot of NAN, I do not understand why. I used a step of one element.
Please, any suggestion is welcome.

Gg

Posted 9 years ago #
Bradley Treeby

Developer
Joined: Mar '10
Posts: 1,640

Hi Gg,

When an object of the kWaveTransducer class is used as a sensor, the output signals are those received by the individual elements. No beamforming is performed unless you explicitly call the scan_line method. For example, if you run the same simulation with 32 active elements or 1 active element, the signal received by the 1 active element would be the same in both cases.

I am not sure about the NaN. If you post your full code, I will try to run it and see what the problem is.

Brad.

Posted 9 years ago #
gigi

Member
Joined: Oct '14
Posts: 12

Hi Brad,

thank you, but if I had 32 transmitting elements and one receiving how is the received signal? it is the result of a sort of superposition?

It is possible to download the example_us_bmode_linear_transducer_modified.m from here:
https://www.dropbox.com/s/v5bfybo4i3n36f5/example_us_bmode_linear_transducer_modified.m?dl=0

I did not change many things..

thank you so much.

Gg

Posted 9 years ago #
JOKEjoe

Member
Joined: Jan '15
Posts: 3

HI,
If my understanding to the question is accurate,maybe i face the same question.i am a college student,and i have a homework recendly:i kown the simple use of k-wave 3D,and my goal is use the tool to achieve two point communicate with one receiver,the receiver can receive the two signal at the same time,but the k-wave only support one transducer communicate with one receiver,i try to define two different transducer(different coordinate,transduce different signal),then maybe i should run kspaceFirstOrder3D,now i do not kown how to make the two transducer work in the same kgrid.later,i want to use frequency demodulator to separate the two signal.It puzzle me for a long time.
Please, any suggestion is welcome.
THX

Posted 9 years ago #
Bradley Treeby

Developer
Joined: Mar '10
Posts: 1,640

Hi JOKEjoe,

If you want to use multiple source transducers in the same simulation, you will need to define these individually using source.p_mask and source.p (rather than using the kWaveTransducer class). Essentially, you define the position and shape of the transducers using the source mask, and then assign the time-varying signals used to drive the grid points within the source mask to source.p. There is a lot more information on how to get started in the Time Varying Source Problems examples (these are accessible in the MATLAB help browser), and in the k-Wave manual.

Brad.

Posted 9 years ago #
JOKEjoe

Member
Joined: Jan '15
Posts: 3

Hi Brad ,

thanks for your answer.

joe

Posted 9 years ago #

RSS feed for this topic

Reply

You must log in to post.

k-Wave

A MATLAB toolbox for the time-domain simulation of acoustic wave fields

Drive the input signals

Reply

A MATLAB toolbox for the time-domain
simulation of acoustic wave fields