ZMT zurich med tech

Yes I'm aware of what you're referring to but there is no readily available template available in Sim4Life. With some work it could be easily generated via a Python script (by creating spheres and disks and using boolean operators to intersect or subtract them) or perhaps you can maybe email the S4L support team to ask if they can provide you with a model for you to import?

You're welcome! If you haven't found it already, you may also check this post: https://forum.zmt.swiss/topic/8/how-to-calculate-the-inductance-of-a-simple-coil It has useful information for computing the inductances...

Great to hear! Keep in min that you can use the same Ares and allow it to use multiple versions of the solvers. It will then automatically select the correct one depending on the version of the GUI you are submitting the simulation from. It is always recommended to use the latest version of Ares, but there are no restrictions on the versions and the number of solvers it can use.

Oh that worked! Thank you :)

@bryn Great! Thank you very much!

Thanks for the help, but I just found the auto-assign button in the Assign material tool... My day is saved.

Thanks for the answer, it works! I hadn't seen the feature Stretch.

That is exactly same as I suffered before. Check the "neurons4l" folder is installed in Sim4Life folder. For example, "C:\Program Files\Sim4Life_6.0.0.3176\neurons4l"

@lj I have followed the yoon-sun arm stimulation tutorial, but I don’t understand the meaning of the results obtained. I don’t know the relationship between these results and tactile feedback, nor can I understand how to get information about tactile sensation and nerve fiber potential. Information link.

Hi Matthew, thanks for the additional information. If I understand correctly, there are mainly 3 steps at play here, each of which repeated a certain number of times: Posing the anatomical model to the desired posture Moving the model to the desired position inside the coil Running the simulation What I would do for a workflow like this is: a) Pose the model to the desired posture [in the GUI] b) "Clone As Static" the desired posture [in the GUI] c) Export the posed model to a .sab file [using a script in the GUI, but clicking buttons could also do] a) Starting from scratch, load the coil and load the posed model [using a script] b) Move the model to the desired position [using a script] c) Setup the simulation [using a script] Run the simulation [using a script] (4). Postprocess the simulation [using a script] So to answer your initial question: I still don't know how to Clone As Static from a script, but since I also don't know how to use the POSER from a script I would anyway still have to use the GUI to create each posture (and then the "Clone as static" is only one click away...). Let me know if I misunderstood your workflow, or if you find a better way to achieve it than what I suggested.

How can I get the download code of neuro solver?

@habib Hi, Thank you for your reply. I can understand that if you enable the titration, the software keeps on scaling the field till sees a stimulation. But it also gives us a number for the scaling field. In this case, I am seeing that number to be 0.13. Doesn't it mean that the field has been scaled down to a factor of 0.13 to create the minimum field for stimulation - I was hoping that number to be orders of magnitude higher. Please correct me if I am wrong. Thanks for looking into this.

@rose your simulations are most likely done with a 1V voltage at the excitation source (that's the default setting). This is perfectly fine from a numerical point of view, but in practice (e.g., if you wanted to compare with measurements) you probably want to normalize your results. In the Far Field Sensor, for example, you can normalize to a Total Available power of 1W (say). This way, you will be comparing apples to apples. That will not change the value for the Gain, though (since it is a power ratio, independent of scaling). This must come from either a difference in some aspect ratio of your dipole, or simply that you did not change the dimensions in the same proportion (1/10th) as you changed the frequency.

@rose, you write "it was a bit different from the theoretical result", but unfortunately I don't fully understand what you did, what you are trying to do, and what you are comparing your results to. Perhaps if you describe (with e.g. screenshots and equations) both what you did and what the "theoretical results" I can try and find why they do not match.

That's great to hear! Thank you so much for sharing your experience. I'll explore the option of implementing something similar for EM simulation.

@hitina please see my answer here

Assuming 'sim' is the acoustic simulation you're interested in and that 'elements' is a list of the elements (gotten from entities = model.AllEntities()) and that 'amp' and 'phase' are numpy arrays with the amplitude, phase values you're interested in assigning: # Print current simulation name print(sim.Name) # Remove all sources before adding them to_del = [] for s in sim.AllSettings: if isinstance(s,acoustic.SourceSettings): to_del.append(s) for d in to_del: sim.Remove(d) # Add sources with correct element and parameters for source_idx in np.arange(len(elements)): source_settings = acoustic.SourceSettings() source_settings.Amplitude = amp[source_idx] source_settings.Phase = phases[source_idx] sim.Add(source_settings, rings[source_idx]) print(rings[source_idx].Name, amp[source_idx], phases[source_idx]) Sorry I'm not providing a full example. Easiest way to do that would be to manually create the whole simulation without the sources (just make all sources as materials), then right click on simulation and select 'To Python...' and then add the lines above to your code You could do something like this to get the elements as a list: src_ents = [] entities = model.AllEntities() for e in entities: if 'Element' in e.Name: src_ents.append(e) Careful, I have no idea how the elements will be sorted in that case but you could use a fixed size numerical suffix and then sort them.

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

Thank you @bryn! I will adapt this to my needs.