System error for Flux 3D simulation
Hi,
I am try to solved a 3D model with second order mesh element and it seems have some techinical issue given it give a warning said below where the part said the stateManager is not synchronous is kind of weird for me to understand.
Moreover, this happen after I tried to solved it, besides the flux3D wont solved it, it crash when I tried to reopen the file.
Warning : the StateManager is not synchronous with the application.
Initial state : ExecutingAlgoExecutingBoxWaitDialogState: lockBDProject,executedAlgo.
Required transaction : closedProjectRequest
The detail of error are showed below:
executeAlgo_c => failed
stdcom.error.SoftwareFortranException: executeAlgo_c : Execution failed.
Failed execution
at cad.core.common.error.ErrorManager.createFortranException(ErrorManager.java:170)
at cad.flux.kernel.dbmanager.FGCProjectDbWrapper.executeAlgo(Native Method)
at cad.flux.kernel.dbmanager.FGCProjectDbAdapter.executeAlgo(FGCProjectDbAdapter.java:918)
at cad.flux.kernel.dbmanager.FGCDbManager.executeAlgo(FGCDbManager.java:151)
at cad.flux.kernel.FGSupervisor.executeNativeCommand(FGSupervisor.java:2216)
at cad.flux.kernel.actions.implementation.algo.project.KSolveScenarioAction.doAction(KSolveScenarioAction.java:83)
at cad.core.common.dynamic.actions.UIActionManager.postAction(UIActionManager.java:146)
at cad.core.kernel.KernelCommon.postAction(KernelCommon.java:347)
at cad.core.kernel.Supervisor.executeJavaCommand(Supervisor.java:2913)
at cad.core.kernel.Supervisor.executeCommand(Supervisor.java:2091)
at cad.core.kernel.Supervisor.executeMethod(Supervisor.java:2210)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.python.core.PyReflectedFunction.__call__(PyReflectedFunction.java:188)
at org.python.core.PyReflectedFunction.__call__(PyReflectedFunction.java:206)
at org.python.core.PyObject.__call__(PyObject.java:545)
at org.python.core.PyObject.__call__(PyObject.java:551)
at org.python.core.PyMethod.__call__(PyMethod.java:171)
at pydb$py.executeMethod$209(pydb.py:1673)
at pydb$py.call_function(pydb.py)
at org.python.core.PyTableCode.call(PyTableCode.java:171)
at org.python.core.PyBaseCode.call(PyBaseCode.java:171)
at org.python.core.PyFunction.__call__(PyFunction.java:434)
at org.python.core.PyMethod.__call__(PyMethod.java:156)
at pydb$py.__call__$176(pydb.py:1444)
at pydb$py.call_function(pydb.py)
at org.python.core.PyTableCode.call(PyTableCode.java:171)
at org.python.core.PyBaseCode.call(PyBaseCode.java:308)
at org.python.core.PyBaseCode.call(PyBaseCode.java:199)
at org.python.core.PyFunction.__call__(PyFunction.java:482)
at org.python.core.PyMethod.instancemethod___call__(PyMethod.java:237)
at org.python.core.PyMethod.__call__(PyMethod.java:228)
at org.python.core.PyMethod.__call__(PyMethod.java:223)
at org.python.core.PyObject.invoke(PyObject.java:3715)
at org.python.core.PyInstance.instance___call__(PyInstance.java:377)
at org.python.core.PyInstance.__call__(PyInstance.java:372)
at org.python.core.PyObject.__call__(PyObject.java:424)
at org.python.pycode._pyx32.f$0(<input>:1)
at org.python.pycode._pyx32.call_function(<input>)
at org.python.core.PyTableCode.call(PyTableCode.java:171)
at org.python.core.PyCode.call(PyCode.java:18)
at org.python.core.Py.runCode(Py.java:1625)
at org.python.core.Py.exec(Py.java:1669)
at org.python.util.PythonInterpreter.exec(PythonInterpreter.java:276)
at cad.core.kernel.components.PythonWrapper.runCode(PythonWrapper.java:649)
at cad.core.kernel.components.PythonWrapper.runsource(PythonWrapper.java:644)
at cad.core.kernel.components.PythonWrapper.runsource(PythonWrapper.java:619)
at cad.core.kernel.components.PythonWrapper.runsource(PythonWrapper.java:614)
at cad.core.kernel.components.PythonWrapper.execute(PythonWrapper.java:659)
at cad.core.kernel.components.PythonWrapper.executeFunction(PythonWrapper.java:727)
at cad.core.kernel.encoder.CommandServerRequestsInputPlug.executeCommand(CommandServerRequestsInputPlug.java:79)
at stdcom.protocole.commandserverrequests.CommandServerRequestsRouter.executeCommand(CommandServerRequestsRouter.java:70)
at stdcom.protocole.commandserverrequests.CommandServerRequestsOutputPlug.executeCommand(CommandServerRequestsOutputPlug.java:111)
at cad.core.frontal.decoder.FrontalDecoder.executeCommand(FrontalDecoder.java:692)
at cad.core.frontal.actions.implementation.GeneralAction.executeBox(GeneralAction.java:286)
at cad.flux.frontal.actions.implementation.algo.project.FAbstractSaveAsAction.executeBox(FAbstractSaveAsAction.java:93)
at cad.core.frontal.actions.implementation.GeneralAction.postAct(GeneralAction.java:254)
at cad.core.frontal.actions.implementation.GeneralAction.interpret(GeneralAction.java:315)
at cad.core.frontal.components.box.frontaldialog.FrontalDescriptorDialogBox.internalRun(FrontalDescriptorDialogBox.java:296)
at cad.core.frontal.frontalthread.WorkerThread.executeImplementer(WorkerThread.java:226)
at cad.core.frontal.frontalthread.WorkerThread.run(WorkerThread.java:274)
Best Answer
-
Hi Haoyu,
Your issue is related to the value of numerical memory, 4096 MB is enough, in your case, for 1 order mesh but not enough for 2 order mesh (1033412 nodes).
You need to increase the value of the numerical memory or use the dynamic allocation.
If you cannot increase it and used a direct solver, you can try solving with an iterative solver for the linear system solver and for the linear system solver for Pre-Computations or use a coarse mesh(increase the values of the mesh) for 1-order and then generate the 2 order.
Best regards,
Alexandru
0
Answers
-
Besides, the issue only happen when the 2nd order mesh element was introduced.
I tried run the very same model with 1st order mesh element which have no problem at all.
Please let me know whether just generate 2rd order mesh element inside mesh menu is not enough? and I need setting something else?
Kind Regards
Haoyu
0 -
Haoyu Liu said:
Besides, the issue only happen when the 2nd order mesh element was introduced.
I tried run the very same model with 1st order mesh element which have no problem at all.
Please let me know whether just generate 2rd order mesh element inside mesh menu is not enough? and I need setting something else?
Kind Regards
Haoyu
Hello Haoyu,
Can you share the Flux3D report file generated when you simulated the model with second order mesh?
Thank you,
Lavanya
0 -
Lavanya Vadamodala_20519 said:
Hello Haoyu,
Can you share the Flux3D report file generated when you simulated the model with second order mesh?
Thank you,
Lavanya
Hi,
I think the report file is not accepted to be upload, therefore I have upload the log file and resave the report file into txt format so I can upload it
Please check the attachmet.
Kind Regards
Haoyu
0 -
Hi Haoyu,
Your issue is related to the value of numerical memory, 4096 MB is enough, in your case, for 1 order mesh but not enough for 2 order mesh (1033412 nodes).
You need to increase the value of the numerical memory or use the dynamic allocation.
If you cannot increase it and used a direct solver, you can try solving with an iterative solver for the linear system solver and for the linear system solver for Pre-Computations or use a coarse mesh(increase the values of the mesh) for 1-order and then generate the 2 order.
Best regards,
Alexandru
0 -
Haoyu Liu said:
Hi,
I think the report file is not accepted to be upload, therefore I have upload the log file and resave the report file into txt format so I can upload it
Please check the attachmet.
Kind Regards
Haoyu
Hello Haoyu,
While solving, the numerical memory available is not enough for Flux to solve your model. This is the reason for the error.
Usually, 2nd order mesh elements need more memory compared to 1st order elements to solve.
I recommend you to use dynamic memory option. With dynamic memory management, Flux will dynamically use memory depending of data to be stored and commands to be executed.
Whereas in User memory, the allocated memory is entirely reserved from start of Flux and execution
Let me know, if you still have difficulty in solving the model.
Thank you,
Lavanya
0 -
Hi Haoyu,
Your issue is related to the value of numerical memory, 4096 MB is enough, in your case, for 1 order mesh but not enough for 2 order mesh (1033412 nodes).
You need to increase the value of the numerical memory or use the dynamic allocation.
If you cannot increase it and used a direct solver, you can try solving with an iterative solver for the linear system solver and for the linear system solver for Pre-Computations or use a coarse mesh(increase the values of the mesh) for 1-order and then generate the 2 order.
Best regards,
Alexandru
Hi Alexandru,
Much thanks for your help and by changing to the dynanmic memory allocation, the simulation is currently running while I am waiting for the result (it takes about 30 hours on my machine to finished the simulation).
I will update to you if there are any further issue.
Kind Regards
Haoyu
0
Altair Employee