Skip to content

Simulations & Solvers

FDTD, Low-Frequency, Neuron, Mode-Matching, Flow, Acoustics, etc...

251 Topics 759 Posts

Subcategories


  • FDTD, Low-Frequency, Neuron, Mode-Matching, Flow, Acoustics, etc...

    12 33
    12 Topics
    33 Posts
    brynB
    @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]).
  • How to simulate a DBS intervention

    1
    0 Votes
    1 Posts
    363 Views
    No one has replied
  • Simulation failed error - how to know what went wrong

    3
    0 Votes
    3 Posts
    1k Views
    M
    Hi, "bad allocation" usually refers to errors due to not enough memory. GPUs have limited on-board memory and if the simulation size exceeds this, it fails to run. I would advice to check your system memory status, and if the simulation is too heavy, using a coarse grid (less MCells) can help.
  • Define what GPU to use in a multi-GPU compute environment

    4
    0 Votes
    4 Posts
    954 Views
    T
    @Mélina This is close to what I want but not exactly. I still want ARES to say I can use both GPU's but I want to be able to say "for simulation 1 run on GPU0, for simulation 2 run on GPU1" . Is there anyway to do this? I tried messing around with the concurrent jobs number (setting it to 2 or 3 or 1) in ARES but I don't believe it's working correctly as I still am only running 1 simulation at a time in the queue.
  • range db simulation

    2
    0 Votes
    2 Posts
    526 Views
    T
    Try and do it programmatically in the python scripter. Set one figure up how you want it then right click on the final slice viewer in the explorer tab and click "to python". Then just look for the bounds there, save the script, and use that for all of your other figures.
  • Errors during voxeling

    2
    0 Votes
    2 Posts
    555 Views
    brynB
    Yes, bad alloc means the memory could not be allocated. Try to reduce grid size, and ensure your subgrid is substantially smaller than the total computational grid.
  • Exporting touchtone files

    5
    0 Votes
    5 Posts
    930 Views
    T
    Thank you Ofli for your quick response. That was very helpful!
  • How to get isometric or uniform grid?

    Unsolved grid isometric uniform emfdtd
    1
    0 Votes
    1 Posts
    646 Views
    No one has replied
  • Current field simulation

    4
    0 Votes
    4 Posts
    933 Views
    M
    Dear Liu, Yes, in order to see any losses, you need to set at least a conductivity different to 0. I would advice you to check if you set correct electric properties in the material settings. Best
  • CEM43 license

    1
    0 Votes
    1 Posts
    406 Views
    No one has replied
  • Frequency sweep using LF model

    1
    0 Votes
    1 Posts
    310 Views
    No one has replied
  • Loss tangent setting for user defined material

    1
    0 Votes
    1 Posts
    318 Views
    No one has replied
  • Analysis - Empty Coil - Grid Fail

    2
    0 Votes
    2 Posts
    474 Views
    M
    Hello, Do you have any error message appearing in the console? If a grid cannot be created, you have to carefully check the grid settings, and ensure that the number of cells is not the big (if so, you can reduce it by adjusting the padding, for example).
  • Pop-up Alert Stops Stimulation

    3
    0 Votes
    3 Posts
    681 Views
    G
    Dear @habib, Just to inform you that has been solved the bug which was causing this pop-up window to appear, and which stopped the script from continuing until the "Ok" button was pressed: [image: 1649688752403-bug.jpg] However, this bug was caused by the code line, which appears in the image: "analysis.RefreshViewers()" With the new S4L v7.0, this line caused this bug for some reason. After removing it, it was possible to avoid that pop-up window. Just to highlight that finding this bug costed 10+ hours, due to the new update. Best, Guillem
  • LF EQS solver diverged/failed

    divergence low-frequency
    1
    0 Votes
    1 Posts
    555 Views
    No one has replied
  • I'm modeling TEM cell, which is device for generating a electric field

    3
    0 Votes
    3 Posts
    657 Views
    R
    @ofli Thank you for texting. Yes. I set up the similar one. I adjusted the size to the edge of the TEMcell tho.
  • Can Acoustic solver works with Flow solver?

    2
    0 Votes
    2 Posts
    444 Views
    brynB
    I am not aware of any coupling implemented for this combination.
  • Programmatically set source settings (neuro)

    1
    1 Votes
    1 Posts
    272 Views
    No one has replied
  • How to use a script to automatically open an already run simulation

    3
    0 Votes
    3 Posts
    660 Views
    S
    @pyf Hi, This is what I found in the tutorial scripts for thermal simulations. Check the RunTutorial function. It may help. Best. def CreateModel(): ... def CreateEmFdtdSimulation(): ... return em_sim def CreateThermalSimulation(em_sim): ... return thermal_sim def AnalyzeEmAndThermalSimulation(em_sim,thermal_sim): # Create extractor for the two simulation output files em_results = em_sim.Results() thermal_results = thermal_sim.Results() # overall field sensors em_overall_field_sensor = em_results[ 'Overall Field' ] em_overall_field_sensor.Normalization.Normalize = True thermal_overall_field_sensor = thermal_results[ 'Overall Field' ] # Create a slice viewer for the SAR slice_field_viewer_sar = analysis.viewers.SliceFieldViewer() slice_field_viewer_sar.Visualization.Smooth = True slice_field_viewer_sar.Inputs[0].Connect( em_overall_field_sensor['SAR(x,y,z,f0)'] ) slice_field_viewer_sar.Update(0) slice_field_viewer_sar.GotoMaxSlice() document.AllAlgorithms.Add( slice_field_viewer_sar ) #THERMAL slice_field_viewer_t = analysis.viewers.SliceFieldViewer() slice_field_viewer_t.Visualization.Smooth = True slice_field_viewer_t.Inputs[0].Connect( thermal_overall_field_sensor['T(x,y,z,t)'] ) slice_field_viewer_t.Update(0) document.AllAlgorithms.Add( slice_field_viewer_t ) def RunTutorial( path ): document.New() CreateModel() em_sim = CreateEmFdtdSimulation() document.AllSimulations.Add(em_sim) em_sim.UpdateGrid() em_sim.CreateVoxels(path) thermal_sim = CreateThermalSimulation(em_sim) document.AllSimulations.Add(thermal_sim) thermal_sim.UpdateGrid() thermal_sim.CreateVoxels(path) em_sim.RunSimulation(wait=True) thermal_sim.RunSimulation(wait=True) AnalyzeEmAndThermalSimulation(em_sim,thermal_sim) if name == 'main': RunTutorial( project_path )
  • 0 Votes
    2 Posts
    462 Views
    S
    @mingjuan Hi, I recommend updating your driver (https://developer.nvidia.com/opengl-driver).
  • EM LF electro simulation

    1
    0 Votes
    1 Posts
    358 Views
    No one has replied