New Operator DEFI_CONT

IV_CoAs

Hello,
In new version are new interesting operators, "MECA_NON_LINE" and "DEFI_CONT".

I have compiled from Gitlab version 17.4.18 and it works, except it gives error "DEFI_CONT" not found.

My question, is something other commands needed to activate "DEFI_CONT".

In source code I found it from /MacroCommands directory, but was missing from /Cata/Commands and /CodeCommands directories.

Messages from solver: "
KONTTI = DEFI_CONT(MODELE=MALLI,
^^^^^^^^^
NameError: name 'DEFI_CONT' is not defined
Traceback (most recent call last):
File "<frozen runpy>", line 198, in _run_module_as_main
File "<frozen runpy>", line 88, in _run_code
File "/opt/aster/install/20251026/gcc12-openblas-ompi4/mpi4py-3.1.6/lib/python3.11/site-packages/mpi4py/main.py", line 7, in <module>
main()
File "/opt/aster/install/20251026/gcc12-openblas-ompi4/mpi4py-3.1.6/lib/python3.11/site-packages/mpi4py/run.py", line 230, in main
run_command_line(args)
File "/opt/aster/install/20251026/gcc12-openblas-ompi4/mpi4py-3.1.6/lib/python3.11/site-packages/mpi4py/run.py", line 47, in run_command_line
run_path(sys.argv[0], run_name='main')
File "<frozen runpy>", line 291, in run_path
File "<frozen runpy>", line 98, in _run_module_code
File "<frozen runpy>", line 88, in _run_code
File "Test_2.comm.changed.py", line 84, in <module>
KONTTI = DEFI_CONT(MODELE=MALLI,
^^^^^^^^^
NameError: name 'DEFI_CONT' is not defined. Did you mean: 'DEFI_CONTACT'?
"
I repeat, in V17 documentation is this DEFI_CONT, but my compiled from GitLab I receive this error.

Best Regards
Ilkka

AsterO'dactyle

Sorry ! The command is not yet "official". To use it:

from code_aster.MacroCommands.defi_cont import DEFI_CONT

IV_CoAs

Kiitos/Merci!

Ilkka

AsterO'dactyle

Finland ?
Nice !

vishwas

Hello,
I try to use DEFI_CONT and MECA_NON_LINE but always get this error:

║ <EXCEPTION> <JEVEUX_62> ║ ║ ║ ║ Erreur lors de l'allocation dynamique. Il n'a pas été possible d'allouer ║ ║ une zone mémoire de longueur 3710 Mo, on dépasse la limite maximum ║ ║ fixée à 4150 Mo et on occupe déjà 975 Mo. ║ ║ La dernière opération de libération mémoire a permis de récupérer 202 Mo. ║ ║

Setting MPI_NBCPU to 1 or 2 or any value, I get the above error. ALso, even if I increase the memory the error persists. What should be done?

Regards
Anirudh

vishwas

Hello,
In docker v18.1.0, I got the above error.
In singularity 18.0.19 compiled version, nothing happens. There is no response from terminal after reading .comm file.
EdIT
I could make it run but results are not saved if MECA_NON_LINE fails after a few converged steps., even though I used
try:
evolu_noli = MECA_NON_LINE(...)

except:
pass
I get following error:
[1,1]<stdout>: NameError: name 'evolu_noli' is not defined [1,5]<stdout>: NameError: name 'evolu_noli' is not defined [1,1]<stdout>: [1,1]<stdout>: Exception: Trying to close the database after an uncaught exception... [1,1]<stdout>: [1,1]<stdout>: [1,1]<stdout>: Publishing the result of the current command MECA_NON_LINE... [1,1]<stdout>: [1,5]<stdout>: [1,5]<stdout>: Exception: Trying to close the database after an uncaught exception... [1,5]<stdout>: [1,5]<stdout>: [1,5]<stdout>: Publishing the result of the current command MECA_NON_LINE... [1,5]<stdout>: [1,2]<stdout>: Objects not saved on processor #2 [1,4]<stdout>: Objects not saved on processor #4 [1,3]<stdout>: Objects not saved on processor #3 [1,1]<stdout>: Objects not saved on processor #1 [1,5]<stdout>: Objects not saved on processor #5 [1,1]<stdout>: No database in results, objects not saved on processor #1 [1,3]<stdout>: No database in results, objects not saved on processor #3 [1,4]<stdout>: No database in results, objects not saved on processor #4 [1,2]<stdout>: No database in results, objects not saved on processor #2
Even bases are not saved.

Regards
Anirudh

IV_CoAs

Hello,
ALGO_CONT='PENALISATION' works, only porblem is, that I don't know how to check penetration etc contact results.

I tried to use ALGO_CONT='NITSCHE', but it fails at least in myself compiled version 17.5.2. Below error message:
Instant de calcul: 1.000000000000e-01
[1,4]<stdout>:
[1,4]<stdout>:-------------------------------------------------------------------------------------------------------
[1,4]<stdout>😐 NEWTON | RESIDU | RESIDU | RESIDU | RESIDU | OPTION |
[1,4]<stdout>😐 | RELATIF | ABSOLU | REFERENCE | GEOMETRIQUE | ASSEMBLAGE |
[1,4]<stdout>😐 | RESI_GLOB_RELA | RESI_GLOB_MAXI | RESI_REFE_RELA | RESI_GEOM | |
[1,4]<stdout>:-------------------------------------------------------------------------------------------------------
[1,5]<stdout>😃EBUG: ContactPairing.cxx #356: DEBUG: ContactPairing.cxx #356: Assertion failed: cellIndx != -1
[1,5]<stdout>😃EBUG: ContactPairing.cxx #356: ABORT - exit code 17
[1,5]<stdout>:Fatal Python error: Aborted
[1,5]<stdout>:
[1,5]<stdout>:Current thread 0x0000722e6504f740 (most recent call first):
[1,5]<stdout>: File "/opt/aster/install/PAR_17_5_2/lib64/aster/code_aster/Solvers/Main/contact_manager.py", line 63 in pairing
[1,5]<stdout>: File "/opt/aster/install/PAR_17_5_2/lib64/aster/code_aster/Utilities/statistics_manager.py", line 54 in wrapper
[1,5]<stdout>: File "/opt/aster/install/PAR_17_5_2/lib64/aster/code_aster/Solvers/IterationSolver/newton_solver.py", line 166 in solve_iteration
[1,5]<stdout>: File "/opt/aster/install/PAR_17_5_2/lib64/aster/code_aster/Utilities/statistics_manager.py", line 54 in wrapper
[1,5]<stdout>: File "/opt/aster/install/PAR_17_5_2/lib64/aster/code_aster/Solvers/IterationSolver/newton_solver.py", line 122 in solve
[1,5]<stdout>: File "/opt/aster/install/PAR_17_5_2/lib64/aster/code_aster/Utilities/statistics_manager.py", line 54 in wrapper
[1,5]<stdout>: File "/opt/aster/install/PAR_17_5_2/lib64/aster/code_aster/Solvers/StepSolvers/meca_stat_step_solver.py", line 55 in solve
[1,5]<stdout>: File "/opt/aster/install/PAR_17_5_2/lib64/aster/code_aster/Utilities/statistics_manager.py[1,5]<stdout>:", line 54 in wrapper
[1,5]<stdout>: File "/opt/aster/install/PAR_17_5_2/lib64/aster/code_aster/Solvers/Main/non_linear_operator.py", line 425 in run[1,5]<stdout>:
[1,5]<stdout>: File "/opt/aster/install/PAR_17_5_2/lib64/aster/code_aster/Utilities/statistics_manager.py", line 54 in wrapper
[1,5]<stdout>: File "/opt/aster/install/PAR_17_5_2/lib64/aster/code_aster/Solvers/Main/non_linear_operator.py", line 388 in run
[1,5]<stdout>: File "/opt/aster/install/PAR_17_5_2/lib64/aster/code_aster/MacroCommands/meca_non_line_ops.py", line 129 in meca_non_line_ops
[1,5]<stdout>: File "/opt/aster/install/PAR_17_5_2/lib64/aster/code_aster/Supervis/ExecuteCommand.py", line 742 in exec
[1,5]<stdout>: File "/opt/aster/install/PAR_17_5_2/lib64/aster/code_aster/Supervis/ExecuteCommand.py", line 226 in run_
[1,5]<stdout>: File "/opt/aster/install/PAR_17_5_2/lib64/aster/code_aster/Supervis/ExecuteCommand.py", line 183 in run

I hope this helps developers.

Best Regards
Ilkka

basile-simvia

Hi,

Thanks for the report! Just to let you know, to my knowledge the NITSCHE method is currently only implemented for 2D cases in code_aster — this is likely why it crashes in your 3D setup. PENALISATION remains the way to go for 3D contact for now.

Regards