Welcome to the forums. Please post in English or French.

You are not logged in.

#1 Re: Code_Aster usage » State of Mortar Contact method in Code Aster » 2020-04-06 05:28:15

Hi,
Thanks for the reply.
3 years is too long. Is there a way to contribute to mortar friction method from me to speed up process? Is there any textual reference that can be used.

Regards
Anirudh Nehra

#2 Re: Code_Aster usage » State of Mortar Contact method in Code Aster » 2020-03-24 15:32:38

Hi,
Thanks for the reply. The CONTINUE LAC method is a mortar method but does not support friction.

Regards
Anirudh

#3 Code_Aster usage » State of Mortar Contact method in Code Aster » 2020-03-24 05:39:05

Anirudh
Replies: 4

Hi to all,
I would be really grateful to know if there are any plans to implement MORTAR CONTACT method with FRICTION in the coming releases of code aster. This method with friction has become quite standard with all FEA tools not just commercial ones but opensource tools as well like KRATOS multiphysics and MoFEM.
The current methods of contact in Code Aster-
1) penalisation contact method is sensitive to stiffness i.e. Contact stress changes with change of stiffness and penetration.
2) Augmented Lagrange Method for contact usually has problems with convergence with friction and curved geometry.
Although the above methods work really well, it would be great to have Mortar with FRICTION.
Hoping for inputs.

Thanks and Regards
Anirudh

#4 Re: Salome-Meca usage » Strange results with COQUE_3D model » 2020-01-04 14:31:34

Hi,
happy new year to Code_Aster vibrant community.
This is a very common issue working with Coque_3D models. Basically, you need to project back the results onto a quadratic mesh( right now the mesh is Biquadratic for Coque_3D) and the results will be fine.
You can search for forum and a post by KEESWOUTERS. Maybe this should help:
http: --/--/caelinux.org/wiki/index.php/Contrib:KeesWouters/shell/plotcoq3d

Regards
Anirudh

#5 Re: Salome-Meca usage » Bugs in Salome Meca 2019 » 2019-11-22 13:51:31

Hi,
I post the screen capture of a usual session in Salome 2019. This happens after every close up of a file. There are a lot of SIGSEGVs once I exit out of Salome 2019. It doesn't matter whether on closing I save the file or not. Please have a look.
https: / /ibb.co/PZF8ZHt

Regards
Anirudh

#6 Re: Code_Aster usage » Dynamic simulation with two meshes stacking together » 2019-10-22 09:34:21

Hi,
I think the problem arises because there are 3dofs for cable element but 6 dofs for shell elements.
I think liaison group does not work here. Also there are large displacements, so liaison group does not support them.
Better to do this :
Use Liaison_DDL between each coincident node. Use python to create a for loop to create Liaison_DDL for each node. That should work.
I have done this kind of dynamic simulation using Liaison_DDL. See here: https-- hmm/youtu.be/Gt23BHjQAAs
Regards
Anirudh

#7 Re: Salome-Meca usage » Bugs in Salome Meca 2019 » 2019-10-11 04:34:38

Hi,
I am using Debian 9 Stretch but I have enabled backports from current debian Sid. I had to update libc6, libstdc++ etc for the graphics card driver to work. These should have overwritten the default libraries that came with Stretch release. I don't know if these cause the error of libstdc++.

Regards
Anirudh

#8 Salome-Meca usage » Bugs in Salome Meca 2019 » 2019-10-09 14:09:19

Anirudh
Replies: 9

Hello,
I have installed salome 2019. It looks well all around but there are some serious bugs in functionality. I had the same libstdc++ error which I got around by

mv ~/salome2019/V2019_univ/prerequisites/debianForSalome/liblibstdc++.* ~/tmp

I would request the administrator to make it a sticky post so everyone is updated to the issues coming up in Salome 2019.
What I have found until now:
1> in Preferences of Asterstudy, If I select" use external editor to edit files", and then right click the command file, A pop up error is received with a python traceback. Interestingly, no such error is visible when clicking the "message" file in the CASE VIEW which also used the option " Use external editor to view message files".
Also, I can't use sublime text which is happily located under /usr/bin/subl in "external editor selection" field. When I do that, it always opens an empty file(be it comm or mess file)
2> opening an hdf file with a successful run and an .rmed file(which shows up in Data Files summary tab) and right clicking on it with "post-process" in Data Files Summary tab of CASE View does not work.
3> I can't see an option to warp by vector in post-process window. Also, in an opened post pro window which has some results, i double clicked another field, and salome just crashed.
4> Loading big med files with lots of groups is a pain in asterstudy. If you clicked by chance "select groups from center" during picking up a group, a lot of time is spent and software hangs. Also, selecting a 2D group after selecting 3D big groups, causes Salome to crash without any warning.
5> Open in Paravis can crash salome sometimes.
6> If something goes wrong, there is a flurry of SIGSEGVs.


I hope developers take a look.

Thanks a lot
Anirudh

EDIT: I found the warp by vector tool and it's working very well. Really great user interface for Post Pro. The export animation into video tool is pretty awesome. Great job overall.

#10 Re: Code_Aster usage » Diagnostic Job: <S>_ERROR » 2019-08-14 11:20:34

ChadGouws wrote:

The mesh file is too big, even when zipped to place upload.

Hi,
You can upload it somewhere, such as Dropbox and share the link here.

#11 Re: Code_Aster usage » [SOLVED] Contact converges based on load multiplier definition » 2019-08-06 13:15:31

Hi,
You could use paraview to do that. Paraview packs a lot of functionality. You may want to check this tutorial here https: / / \youtu.be/c0w3U5nzo0s
What you want to do is covered somewhere around 19 minutes. You could select any result instead of ID to display it graphically on the geometry.

Regards
Anirudh

#12 Re: Code_Aster usage » SOLVED If i have accelerometer data which are the analysis i can run ? » 2019-08-05 11:31:21

Hi,
In version 13 it used to be DYNA_VIBRA. It may have been changed to DYNA_LINE in version 14.
Also you could do modal analysis, frequency response, transient response and random vibration response.
You can check here to see some types. https: / \www.youtube.com/\watch?v=Ddc3Kr6GDgI

Regards
Anirudh

#13 Re: Code_Aster usage » SOLVED If i have accelerometer data which are the analysis i can run ? » 2019-08-04 12:42:55

Hi,
I don't have much experience to say but you could do Linear Dynamics and Harmonic analyses. Assigning measured data to nodes means applying velocities, accelerations etc to nodes. I think you can do that with CREA_CHAMP and some python coding.

Regards

#14 Re: Salome-Meca usage » Thermal Problem With Two Materials. » 2019-08-01 09:10:43

Hi,
If your intent is to see evolving temperature of two bodies in contact with different thermal conductivities and RhoCp, its very simple to do.
Also, it's unclear to me why you want to post process both bodies separately. Usually what you get out of thermal analysis is temperature and flux at each node/element. These can be viewed together for each body. If you still want them separately, use IMPR_RESU((FORMAT='MED',RESU=_F(RESULTAT = THER_RESULT, GROUP_MA='FIRSTBODY',) UNITE = 80)
Ofcourse you can use just 1 mesh for 2 bodies. Just create two groups of faces(if 2D analysis) or volumes(if 3D analysis) and assign different materials to both.

Regards
Anirudh

#15 Code_Aster usage » Resume calculation with MPI without base » 2019-08-01 08:31:14

Anirudh
Replies: 0

Hi & bonjour,
I was running a parallel run and the system was unplugged, consequently it shut down instantly. I was running a
resnonl = STAT_NON_LINE()
and it converged till 0.7s out of 1s. It had mpi_nbcpu=4 processors and ncpus=1. I attach the export file and command file.
My base and message file was not saved.
I got only these folders in work directory as set in export file.
main("/home/anirudh/Desktop/mpiruns"):
pic1.png
global:
pic3.png
proc0:
pic2.png

I want to POURSUITE the calculation from last converged step like below:
resnonl = STAT_NON_LINE(reuse=resnonl,....)
When I tried a new command file having only the above command with unit=2(using changed export file), and P rep_trav = "/home/anirudh/Desktop/mpiruns/"
It gave the error that bases do not exist.
When I tried with the same command file(with unit 1) and export file(with P rep_trav = "/home/anirudh/Desktop/mpiruns/")
I think it overwrote the original folders with fresh global and proc0, proc1, proc2 and proc3

How can I make this happen?

Thanks a lot.
Anirudh

#16 Re: Code_Aster usage » How to switch off the log file writing on disk » 2019-07-31 22:45:29

Hi,
To turn off alarms that you are definitely sure of, just include this statement in the DEBUT() command at the top of comm file:
DEBUT(IGNORE_ALARME=("SUPERVIS_25","DISCRETE_26" ...etc..) )


Anirudh

#17 Re: Code_Aster usage » [SOLVED] Erreur à la relecture du fichier de maillage » 2019-07-27 02:55:26

Hi,
My first observation is that maybe code aster needs the node numbers in an ascending order.
Of all the nodes that form the first tetra10 element E93251, the node number N202526 on line 887721 is the smallest number. Aster may want it as the first node. So place this node besides E93251 on line 88718. Thus, try reordering all nodes according to their magnitude in ascending order on the same line as element.

Edit: Nice observation, 11 nodes for tetra10
Regards
Anirudh

#18 Re: Code_Aster usage » [Solve]MPI Code_aster 14.2 processes are not killed on Clean interrupt » 2019-07-25 16:23:11

Hi,
I solved above error with this command below.

pids=$(pgrep aster) && kill -s USR1 $pids

and to solve the second problem, I first need to cd into the directory containing export file.

Regards
Anirudh

#19 Re: Code_Aster usage » [Solve]MPI Code_aster 14.2 processes are not killed on Clean interrupt » 2019-07-25 16:18:49

Hi,
When i try to run an export file using

/home/anirudh/code_aster/bin/as_run 1.export

I get this error below:

<F>_PROFILE_COPY   error during copying 1.export to /tmp/astk_anirudh/anirudh-anirudh-profil_astk_5443
message : cp: cannot stat '1.export': No such file or directory

If someone can tell whats wrong?


Thanks
Anirudh

#20 Code_Aster usage » [Solve]MPI Code_aster 14.2 processes are not killed on Clean interrupt » 2019-07-24 11:41:29

Anirudh
Replies: 2

Hi to all,
I am using MPI version of CA14.2.
However, when I have to cancel a run, I try to use clean interrupt from ASTK. When I do that, the XTERM window is still always open and neither the processors are discharged. I have to manually kill XTERM window and kill aster processes from terminal using PID.
In the previous version(13.4), even when I cancelled XTERM window only, all the processes were killed automatically and the cpus were discharged.
What to do?

Thanks.

#21 Re: Salome-Meca usage » salome meca fails on resuming closed study » 2019-07-18 04:10:32

Hello,
This error seems to be resolved after resetting the preferences to Default in salome preference dialog box.

Anirudh

#22 Salome-Meca usage » salome meca fails on resuming closed study » 2019-07-17 14:04:32

Anirudh
Replies: 1

Hi,
I use Salome meca for various design work. The issue is sometimes when I open a saved study(that may or may not have errors),
it shows an error dialog box and I can't click any of the buttons on it. Neither can I click YES, NO or CANCEL. All I can do is close it from the top left X button, then again another one opens, and this time I can't even close it from there. All I can do is just kill salome meca from system monitor/terminal using PID.
Please how can I get rid of this error.
One other issue is that when I dump study that contains Asterstudy component, and load that dumped script, it hangs again.
If the asterstudy version is set to default so that no dialog box opens to ask the version of asterstudy, its ok, but If this option is set to ask in Preferences, it hangs in loading script.
I attach these errors in a video capture here.
hang-salome-asterstudy.gif
Thanks a lot.
Anirudh

#23 Re: Code_Aster usage » use python loop to parse values in ORIENTATION concept » 2019-07-17 13:06:12

Hi,
I tried various groups in many ways. But the results are random.
Sometimes it works, sometimes doesn't. Looks like it has more problems around curved geometry. Attaching a run mess file. I created a new group of nodes=g1, which is just a group of consecutive nodes near the beginning.
Group of nodes=post(which I believe is same as post_reduced in test1.comm) does not work either.
Comm file:

DEBUT(PAR_LOT='NON')


#i had to disable all that as i do not have the file /tmp/beam
# import sys
# sys.path.insert(0,"/tmp/beam")
# import lists
# print lists.list_orien
# print lists.group_spr
# orie=[];


mesh_all = LIRE_MAILLAGE(FORMAT='MED',UNITE=2)

mesh_all=DEFI_GROUP(
    reuse =mesh_all,
    MAILLAGE=mesh_all,
    #next we create some groups of node
    CREA_GROUP_NO=(
    	#in a ordered manner
		#_F(
		#	NOM='post',
		#	GROUP_MA='all_beams',
		#	OPTION='NOEUD_ORDO',
		#	NOEUD_ORIG='N27',
		#	NOEUD_EXTR='N31',
		#),
		#should be the same as 'post'
		_F(
			NOM='post',
			NOEUD=('N4','N6','N8','N10','N12','N14','N16','N18','N20','N22','N172','N174','N176','N178','N180','N182','N184','N440','N442','N444','N446','N448','N450','N452','N454','N456','N458','N716','N718','N720','N722','N724','N726','N728','N730','N734','N1144','N1145','N1146','N1147','N1148','N1149','N1150','N1151','N1152','N1153','N1154','N1155','N1156','N1157','N1158','N1159','N1160','N1161','N1162','N1163','N1164','N1165','N1166','N1167','N1168','N1169','N1170','N1171','N1172','N1173','N1174','N1175','N1176','N1177','N1178','N1179','N1180'),
		),
	),
);

model = AFFE_MODELE(AFFE=(_F(MODELISATION=('POU_D_E', ),
                             PHENOMENE='MECANIQUE',
                             TOUT='OUI'),
                          _F(GROUP_MA=('all_springs'),
                             MODELISATION=('DIS_T', ),
                             PHENOMENE='MECANIQUE')),
                    MAILLAGE=mesh_all)
                    
# for i in range (0,len(lists.list_orien)):
	# orie.append( _F(GROUP_MA=lists.group_spr[i],CARA='ANGL_VRIL',VALE=lists.list_orien[i]),);
# print orie

elemprop = AFFE_CARA_ELEM(
	MODELE=model,
	DISCRET=_F(
		CARA='K_T_D_L',
		GROUP_MA=('all_springs'),
		REPERE='LOCAL',
		VALE=(1.5e8, 1e9, 5000.0),
	       ),
        ORIENTATION=_F(GROUP_MA='all_beams',CARA='VECT_Y',VALE=(0.0,0.0,1.0),), 
	#and the discrete with local Y in global Y
	#ORIENTATION=orie,
	POUTRE=_F(
		CARA=('EP', 'H'),
		GROUP_MA=('all_beams', ),
		SECTION='RECTANGLE',
		VALE=(0.04, 0.1),
	),
);
IMPR_RESU(CONCEPT=_F(CARA_ELEM=elemprop,
                     MODELE=model,
                     REPERE_LOCAL='ELNO'),
          UNITE=3)

#FIN()


mater = DEFI_MATERIAU(ELAS=_F(E=2e+11,
                              NU=0.33,
                              RHO=8000.0))

fieldmat = AFFE_MATERIAU(AFFE=_F(MATER=(mater, ),
                                 TOUT='OUI'),
                                 MODELE=model)

load0 = AFFE_CHAR_CINE(MECA_IMPO=(_F(DRX=0.0,
                                    DRY=0.0,
                                    DRZ=0.0,
                                    DX=0.0,
                                    DY=0.0,
                                    DZ=0.0,
                                    GROUP_NO=('start_vertex','end_vertex'),),
                                    _F(
                                    #DRX=0.0,
                                    #DRY=0.0,
                                    #DRZ=0.0,
                                    DX=0.0,
                                    DY=0.0,
                                    DZ=0.0,
                                    GROUP_NO=('all_bottom_fixed_points'),),),
                                MODELE=model)

load1 = AFFE_CHAR_MECA(PESANTEUR=_F(DIRECTION=(0.0, 0.0, -1.0),
                                    GRAVITE=9.81),
                                    MODELE=model)

reslin = MECA_STATIQUE(CHAM_MATER=fieldmat,
                        MODELE=model,
                        CARA_ELEM=elemprop,
                       
                       EXCIT=(_F(CHARGE=load0),
                              _F(CHARGE=load1)),
                       OPTION='SIEF_ELGA')

#this table seems to write ok
tableg = POST_RELEVE_T(
	ACTION=_F(
		GROUP_NO=('g1', ),
          #NOEUD=('N4','N6','N8','N10','N12','N14','N16','N18','N20','N22','N172','N174','N176','N178','N180','N182','N184','N440','N442','N444','N446','N448','N450','N452','N454','N456','N458','N716','N718','N720','N722','N724','N726','N728','N730','N734','N1144','N1145','N1146','N1147','N1148','N1149','N1150','N1151','N1152','N1153','N1154','N1155','N1156','N1157','N1158','N1159','N1160','N1161','N1162','N1163','N1164','N1165','N1166','N1167','N1168','N1169','N1170','N1171','N1172','N1173','N1174','N1175','N1176','N1177','N1178','N1179','N1180'), 
		#NOEUD=('N27','N32','N33','N34','N20','N35','N36','N37','N18','N38',),  
		INTITULE='displacement', 
		#MOYE_NOEUD='OUI', 
		NOM_CHAM='DEPL', 
		NOM_CMP=('DX', 'DY', 'DZ',), 
		OPERATION=('EXTRACTION', ), 
		REPERE='LOCAL', 
		RESULTAT=reslin,
		#MOYE_NOEUD='NON',
          VECT_Y=(0.0, 0.0, 1.0),
	)
)
IMPR_TABLE(FORMAT='TABLEAU',TABLE=tableg,UNITE=92);
IMPR_RESU(FORMAT='MED',RESU=_F(RESULTAT=reslin),UNITE=80);
#try the various option in this
FIN()

Thanks
Anirudh

#24 Re: Code_Aster usage » use python loop to parse values in ORIENTATION concept » 2019-07-16 20:01:46

Hi,
I again recieved the same error saying Node too far from the norm of the segment.
Then, I tried plugging directly the node numbers for nodes which did not have above error which I found to be N27 and N28
So, I tried this:

 table1 = POST_RELEVE_T(ACTION=_F(INTITULE='displacement',
                                   RESULTAT=RESU1,
                                   OPERATION=('EXTRACTION', ),
                                   NOEUD=('N27', 'N28'),
                                   VECT_Y=(0.0, 0.0, 1.0),
                                   NOM_CMP=('DX', 'DY', 'DZ'),
                                   MOYE_NOEUD='OUI',                       #averaged or not, same error
                                   REPERE='LOCAL',
                                   NOM_CHAM='DEPL',
                                   PRECISION=1.E-06,
                                   CRITERE='RELATIF',
                                   FORMAT_C='MODULE',),
                         INFO=1,)

The execution stopped with a red and I got this error:

 <I>_EXIT_CODE = 136

Attaching mess file.

Thanks
Anirudh

#25 Re: Code_Aster usage » ERROR in documentation » 2019-07-16 14:43:31

Hello,
There seems to be a typographic error in AFFE_CARA_ELEM documentation(u4.42.01) Page 31.
The error is under Opérande CARA = ’ANGL_VRIL’.
The text is , "...transformant ( P , x3, x 2, x2 ) en ( P , x3, y3, z3)"...
whereas it should be "...transformant ( P , x3, y2, z2 ) en ( P , x3, y3, z3)..."


Regards
Anirudh