Hi, most likely you have some other boundary conditions that are affecting the solution. Please share a screenshot of your boundary condition settings, maybe there is a clue there.

How can I get the download code of neuro solver?

Hello, Could you please explain a bit more what you mean by two operations and different results. Please provide any data or screenshots that you think would help us understand the problem.

@christos1996 when I reach into the "Sensors" setting at Simulation Settings (Neuron)], the option "Point "Sensor Tool" is not available to click into. I am sure I have load the model. So have you solved this problem? how to solve ? hope you can reply me .

What do you mean with 'it is a real struggle' to calculate the phase? I used a python script for this. Would this be an acceptable solution? The idea is this (all in Python): Have a list of points indicating the coordinates of the base of the tranducer (can also be automated via Python) Interpolate the field values (complex values) of the reverse simulation at these points Calculate the phase of the complex value and conjugate it Create new simulation and add these phase values to the different sources of the transducer

I didn't do Python scripts yet so it is only when using the GUI. But I don't know which action because I realized after quite a time that the error was there, I could run the script anyways :)

Additionally, check the Boundary Settings on the Outside (your first Boundary Settings). Seems you set the potential of the spheres to the same value as the outside boundary of your domain and that's why it's constant outside the spheres and at the domain walls as well (hard to make sense of the problem with the dimensions you mentioned and what's displayed in the plots). Also, when setting Voltage (Dirichlet) boundary conditions, make sure to set a 'reference' (Ground: 0V) voltage somewhere

@hitina please see my answer here

Ok, we could set up a call for this ... The Mida model won't really work since it's based on MRI images which doesn't have good contrast for Bone. The typical approach utilizes CT images (known acoustic property maps use CT data as well)

@gbgbha you are right.thanks you very much.

@montanaro Thanks for your clarification.

@sylvain I learned your before reply.I want to know how to set the voltage of electrode to the desired value or frequency.how to set the expression(sin(2pi*2000t)) in siM4life? best wishes

hi, regarding padding: as a general rule, if you are not sure whether a numerical parameter will affect your simulation results, the best course of action is to just "try and see". Change parameter -> see if it affects the results significantly. For the padding, you should try to increase it and check that your simulation results are not affected by spurious "boundary effects". as for tutorials: yes, in principle you should obtain the same results as shown in the manual. If you do not, please check carefully that you followed the steps faithfully (pay attention, for example, to the Normalization settings in the Analysis/postprocessing part, after extracting the field sensors - forgetting to tick this box would often lead to orders of magnitude difference in the results).

@Sylvain thanks for your reply! I did check with my supervisor and it is true that our license does not include that solver as our project does not need it.

Yes I did mean wavelength, not period .. That's the drawback of running high frequency simulations in FDTD, they require a lot of voxels ... If appropriate, try running it at 500 kHz and then update the automatic grid settings ... The auto grid settings is based on the material in your domain that has the lowest speed of sound, please remove air from the simulation domain if appropriate ... One of my previous comments tells you how to calculate the wavelength, the units and magnitude seem wrong in yours, remember that you're not using the speed of light to calculate the wavelength, you use the speed of sound in the medium (around 1500m/s)

What is the error message indicated by the red triangle? Maybe the flux is negative. Did you try adjusting the limits on the colorbar?

Hi, this typically happens if some material that is voxeled is not found. If I had to guess, I'd say that you have a source and no corresponding material (the source element should be in the Sources and Materials)