ZMT zurich med tech

Something must be wrong in your simulation setup. It is unlikely to be due to the fact that it is a multiport simulation (since under the hood a multiport simulation is just a bunch of "single" FDTD simulations). I would suggest you check the voxels of your simulation (View Voxels) and ensure that they accurately represent what you are trying to simulate. Pay special attention to the sources and the connectivity between the sources and the various PEC elements.

I've solved the issue. The sweep works if I set the source for the QS solver to a coil (wire current settings) instead of linking in that data from the SV solver (vector potential settings).

Hi,

How do you ensure they are in xy,yz or xz plane. Visually they are but I still face the error?

Hi Anna, I see that nobody answered to your question. Were you able to run this type of simulation? I would like to to a phototermal therapy as well using metallic nanoparticles with a laser. I am not sure if with sim4life this type of simulation can be done or not. If you could tell your experience on this, it would be great.
Thanks in advance for your time and help,
All the best,
@AnnaGol

Hi Michael,

I think you are talking about project files (.smash), and not about simulations.

One project file can have multiple simulations in it.

Your solution can be to use s4l_v1.document.SaveAs( "FileName" ). This will change the name of the current file from default to something you choose.

Best,
Habib

Hi Michael,

Yes, this sounds reasonable. You define the frequency in the Setup settings of the simulation, and you define three boundary conditions, -1, +1, and 0V.

Best,
Habib

Hi Michael,

What type of simulation/solver you are running?

If I understand correct, all the simulations are of the same size, but the output files are of different sizes? This should not be the case.

Unless simulations have larger grids, more sensors recorded, more frequency snapshots, etc, the output file size must not change.

Best,
Habib

Hi Vasilis,

The Hyperthermia Optimizer and Template are licensed products that are not part of the Sim4Life light student version.

Best,
Habib

Hi Gia,

There is no tool that computes the scalar product for the J-fields from two sensors/simulation. However, you can try to access the fields from Python and compute the product yourself.

You can extract the J-field in the UI, and then right-click the lowers algorithm in your Analysis tree and select ToPython. This will help you with writing a script to extract certain quantities.

Best,
Habib

Hi Marcus,

This doesn't appear to be related to Windows Defender.

However, from the log you pasted, it is not exactly the tutorial of TMS. The grid is different than what is described in the tutorial, and there is an additional object in the simulation "Reference_Plane".

Something in your setup is not correct anymore and cause the solver to fail. With the amount of information I have here, I cannot suggest a solution.

Please try to run the tutorial as it is (maybe open the project file and run it, instead of building it from scratch), and see if this one fails too.

Best,
Habib

J(x,y,z,f0) is the volume current density:

081c7de2-7f8f-4450-8e4c-bd69ad8a8ec7-image.png

So integrating it's flux across a surface, one gets A/m^2 m^2, which simplifies as A. The unit shown in the table viewer unfortunately does not do the simplification...

I have managed to solve this. The function below seems to work

def DiscretizeAxonModel(Axon_name, Diameter, type,folder): axon_entity = model.AllEntities()[Axon_name] if type=='motor': model_properties=model.MotorMrgNeuronProperties() elif type=='sensory': model_properties=model.SensoryMrgNeuronProperties() else: model_properties=model.MotorNeuronProperties() model_properties.AxonDiameter=Diameter discretized_axon = model.CreateAxonNeuron(axon_entity,model_properties) discretized_axon.Name = Axon_name +'_neuron' folder.Add(discretized_axon)

Hi @VigneshYork

Please carefully check that the voxels of the edge sources are correctly generated. You can use the "Connectivity" mode under in Voxel Viewer to check that the edge sources are correctly connected. If that is not the case, you need to work on the grid to fix the issue.

Hi @wouterverhelst

This error can appear with simulations having a non-optimal grid with at least one very small cell leading to a very small step size. Could you please inspect the grid in your simulation and see if it can be improved? Please use "Connectivity" option in voxel view to make sure that the source is connected. If possible, please share more info, for example, parts of the log file where you can see min grid step, time step and initialization of source(s):

[INFO]: Number of cells: … [INFO]: Number of cells including PML: … [INFO]: X: Range [.. ... .. ] with minimal .. and maximal step .. [m] [INFO]: Y: Range [.. ... .. ] with minimal .. and maximal step .. [m] [INFO]: Y: Range [.. ... .. ] with minimal .. and maximal step .. [m] … [INFO]: Simulation Time Step: … sec … [INFO]: Sources: [INFO]: Initializing edge source Lines 1 (Sources) … …

That worked- thanks a lot!

Hi,

I decreased the max step of the dielectric material in the coaxial cable, but still got the same warning. I have two questions:

Is there are formula which can be used to determine the cross-section? How does the warning affect the result?

Thanks

Hi,

I would like to power the two waveports with an input which is 180 degree phase apart between each other. The antennas are constructed in a differential manner to increase penetration. I am not sure how to provide the power input to the waveport guide

Thanks