ZMT zurich med tech

can you supply some code example ? thanks

License issue?

@MSJ the modify button is probably hidden on the top right, if you click the triangle where you see the three dots (...).

This is windows configuartion related issue. You might not have access to log counter data, try logging in as an administrator. Later you can add user to the Performance Logs User Group. Look at this page for more details: https://learn.microsoft.com/en-us/windows/win32/perfctrs/limited-user-access-support

@brown Thank you, I will check these things. Additionally, there are some warning messages which may help: [image: 1714906840653-7427af6d-b388-4d9a-b629-2678e1872293-image-resized.png] Is the mesh division not precise enough？

@bryn Thank you again for your reply and the posture file!

Thank you, I could obtain the same also using this: analysis.exporters.MatlabExporter.ExportTo(matlab_exporter,matlab_exporter.FileName) Do you think it is a good solution as well?

This is in an older version of sim4life 8.0, maybe the problem has already been fixed. Otherwise I think this was a multiport simulation but I forget now... Maybe that could be a strange bug where it works for multi but not single or vise versa.

Hi, Sorry to bother You. IN ATTACHED VIDEO SHOWS WHAT HAPPENS AFTER CLICKING THE OPTION "CREATE PLOT" AND THE SYSTEM CRASHES. The workstation and memory have been tested, all without errors. Can one of the service engineers help? Kind regards, Thank you, Andrei Andrei Churakov MD,PhD, Associate Professor of the Department of Electronic Engineering and Technology BSUIR E-mail: anchurakov@bsuir.by

So my problem was solved for the simple phantom a sphere. It can be voxeled. I am having a discussion with chatgpt about how to load Duke into the simulation section because currently it wont be voxeled. Is there a simple few lines of code that loads Duke and all the default tissue electrical properties or is it necessary to assign each tissue type in a loop or via thousands lines of code (as I have seen elsewhere)....

Hi @cbenj33 we are aware of the inconsistencies (we have changed the position of the nerve and electrode, which will be part of the next release happening soon). For now, I am emailing you the pdf version of this tutorial documentation and explanations regarding the errors.

@viniltc, the error looks like you do not have a simulation called "Simple ES" (the returned simulation is None). Please double-check the name, including white-spaces. You can also access by index (document.AllSimulations[0]).

OK, I will share it. Thanks

Dear, @AntoninoMC Thank you very much for your detailed clarification. I now understand the fundamental difference between the Ohmic solver and the QS solver, and I have also tried some test runs with the QS solver, which helped me to grasp the impact of frequency dependence more clearly. In my current application, I am applying a voltage to the human body and measuring the potential difference between two points on the head. I am particularly interested in how the measured potential difference changes with the frequency of the applied current. The frequency range I am considering is typically from about 10 kHz up to 100 kHz, but I am also exploring much lower frequencies, down to around 100 Hz. If you could kindly point me to relevant references or scientific literature that discuss similar applications or provide guidance on which dielectric properties are most suitable in this frequency range, it would be extremely helpful. Thank you again for your support.

@bryn Thank you very much for your reply. Both the visualization of the electric field in the nerve region and the extraction of the field data as a .mat file have been successfully resolved. I really appreciate your kind support and clear explanations.

@halder Thanks do much, the call was really very useful.

thanks so much, appreciate it!

sorry, I gave you some code for the Simulation Combiner, not the Field Combiner... This is how you can use the GetWeights and SetWeights functions for the field combiner: >>> field_combiner.GetWeights() ((1+0j), (1+0j)) >>> field_combiner.SetWeights( ( (2+0j), (-3+0j) ) )

@pcrespo By the way. Converting to Solid (using either method) only works well when a) the mesh resolution is not too high (else it will take forever and use huge amounts of memory) b) the surface mesh is manifold and has no self-intersections. these defects can be identified and often fixed using the Mesh Doctor ("Automatically Fix"). [image: 1525763911163-d38bb2c1-efd5-4038-b84a-605be284dda1-image.png] [image: 1525763920888-3d828313-84bb-4410-9be9-d584b6318823-image-resized.png]

If there is a message such as "Job Finished", this probably means that the job is not really "stuck" at 0% but that it simply failed, for some reason. You might get additional information by looking at the Console (View -> Console) or by looking at the log file from the solver itself (this is a file ending with _Input.log in the Results folder of the project). The latter is also visible from within Sim4Life using the Task Manager (click at the bottom right of Sim4Life to open it).