Resource Menu

posted by Aldo at Jun 23, 2018 4:06 AM
  1. once encountered this kind of errors when my geometry was "too close" to the borders, so a "large" mesh would deform nearby the boundaries of the experiment.
It got better once I made the computational volume larger or the mesh less coarse. Kind of "try and error".

Hope it helps.

posted by Benedek Prágai at Jun 20, 2018 7:22 PM
Hi, I have a problem with creating new projects, and I think it's about the mesh. So I try to make project with the same geometry, but with different meshes. I change the mesh density only on one surface (I tried with multiple surface, and I got the same error), and above a certain density (to be exact under 0.1 meter characteristhic length) I got the following error when I hit "Finalize run configuration and save project":

" Ooops! There was an error while initializing the numerical kernel. Please report it to the development team or on SPIS bug tracker. Do not forget to include the debug.txt file at the root of the software. Stacktrace: java.lang.ArrayIndexOutOfBoundsException: -1 at spis.Solver.Poisson.PoissonInit.interpolatePotential( at spis.Solver.Poisson.ConjGrad3DUnstructPoissonSolver.interpolatePotential( at spis.Surf.SurfInteract.DustySurfacesInteractor.computeForce( at spis.Surf.SurfInteract.DustySurfacesInteractor.computeSample( at spis.Surf.SurfInteract.DustySurfacesInteractor.computeInteraction( at spis.Top.SC.InteractSC.computeInteraction( at spis.Top.SC.InteractSC.computeInteraction( at spis.Top.Simulation.SimulationFromUIParams.init( at spis.Top.Simulation.SimulationFromUIParams.<init>( at spis.Top.Top.NumTopFromUI.<init>( at org.spis.ui.spis.num.numerical.core.implementation.NumericalCore.<init>( at org.spis.ui.ui2num.util.Ui2Num.buildNumTopFromUI( at at at org.keridwen.core.messaging.AbstractCommand.execute( at org.keridwen.core.messaging.DefaultBundleController$ at at java.util.concurrent.ThreadPoolExecutor.runWorker( at java.util.concurrent.ThreadPoolExecutor$ at "

If I increase one characteristic length and decrease the other to keep the mesh element number on the same level, I still get the error. Can you help me what can cause this problem? OS: Ubuntu, Spis: Spis-Dust 5.2.4, gmsh: 3.0.6 (I tried gmsh 2 too)

Thank you for helping me, Benedek Prágai