[Archive] error while initializing the numerical kernel

Message by Gregorio Suino:
Happy New Year to all,
I am working with SPIS 5.1.4, I encountered this error diring “finalize configuration and save project operations”:
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.
java.lang.ArrayIndexOutOfBoundsException: 3178
at com.artenum.penelope.field.data.IntDataArray.get(IntDataArray.java:106)
at com.artenum.penelope.field.data.IntDataArray.get(IntDataArray.java:28)
at org.spis.ui.ui2num.util.Ui2Num.buildMeshElementIdsFlagArray(Ui2Num.java:382)
at org.spis.ui.ui2num.util.Ui2Num.buildNumTopFromUI(Ui2Num.java:204)
at org.spis.ui.ui2num.command.NumTopFromUICommand.run(NumTopFromUICommand.java:162)
at org.spis.ui.ui2num.command.NumTopFromUICommand.run(NumTopFromUICommand.java:52)
at org.keridwen.core.messaging.AbstractCommand.execute(AbstractCommand.java:200)
at org.keridwen.core.messaging.DefaultBundleController$CallableCommand.call(DefaultBundleController.java:259)
at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Is there someone who can help me?
Thank you very much.

Message by Christian Imhof:
Hi Gregorio,
this error message is most likely linked to an error/discrepancy in your GMSH CAD model. Please try to ensure that you have no mesh cells inside your original satellite. So, it is important in the GMSH interface when you are defining the simulation volume, that you add the satellite and any part of it as hole in the volume. By doing this you ensure that the interior of the satellite is not meshed. If you have defined the satellite as hole in your volume and still are facing this problem it can be the case that your satellite model is not closed. Can be the case if you have not defined all surfaces on the satellite (can easily happen for complicated models). Another reason is that some of the satellite surfaces have no physical group assigned.
Especially for the last two problems it can be time consuming to identify the source of the error, unfortunately.
Hope this helps. Good luck with your sims.

Message by Gregorio Suino:
Hi Christian,
tank you,
As you suggested i solved the problem changing some parts of the Gmsh code.
Have a nice day.