site map | contact | login | Protection des données personnelles | Powered by FluxBB | réalisation artaban
You are not logged in.
- Topics: Active | Unanswered
#1 Re: Code_Aster usage » Convergence issue due to contact » 2021-09-06 09:15:23
Kindly email, all volumes mesh seperately as need to re-mesh all components.
#2 Re: Code_Aster usage » Convergence issue due to contact » 2021-09-01 07:36:46
Ok
you can directly sameer21101970@gmail.com .
#3 Re: Code_Aster usage » Convergence issue due to contact » 2021-08-31 13:36:34
send med file
#4 Re: Code_Aster usage » Dynamic harmonic parallel calculations » 2021-08-28 07:05:13
share your present .comm and .med files.
#5 Re: Code_Aster usage » [SOLVED] Error on complex curved sheet metal with shell elements » 2021-08-26 11:38:55
model = AFFE_MODELE(AFFE=_F(MODELISATION=('COQUE_3D', ),
PHENOMENE='MECANIQUE',
TOUT='OUI'),
MAILLAGE=mesh2D)
elemprop = AFFE_CARA_ELEM(COQUE=_F(ANGL_REP=(0.11, 0.22),
EPAIS=0.0015,
GROUP_MA=('Group_surf', )),
MODELE=model)
above changes will work without error
#6 Re: Code_Aster installation » CA 14.6 problem install whit OPENBLAS » 2021-07-30 14:00:45
w.code-aster.org/forum2/viewtopic.php?id=25201
above thread might help you.
#7 Re: Code_Aster usage » NoConvergenceError » 2021-07-17 08:51:59
attached .comm file converges
#8 Re: Code_Aster usage » Mesh sensitivity, convergence in code_aster and Ansys » 2021-06-25 12:42:40
run below .comm file and reply.
#9 Re: Code_Aster usage » CalculiX vs Code-Aster » 2021-06-16 11:46:55
Calculix in Highlighted Writing Says " We Don't Guarantee Accuracy of Analysis Results".
Only Time Passers will use Calculix.
#10 Re: Code_Aster usage » Dome analysis » 2021-05-26 14:40:21
below info will help you.
refer page 89,90,91,92,93 of code_asterbook-jp_aubry-20190129.pdf book
stat=CALC_CHAMP (
reuse =stat , RESULTAT=stat ,
CONTRAINTE = (
’SIEF_ELNO’ ,
’SIPO_ELNO’ ,
’SIPM_ELNO’ ,
’SIGM_ELNO’ ,
),
FORCE = ( ’REAC_NODA’ ) ,
);
refer page 89,90,91,92,93 of code_asterbook-jp_aubry-20190129.pdf book
#U4.85.01
stat2=POST_CHAMP (
RESULTAT=stat ,
GROUP_MA = ( ’panel’ , ) ,
EXTR_COQUE=_F (
NUME_COUCHE=1 ,
NIVE_COUCHE=’SUP’ ,
NOM_CHAM = ( ’SIGM_ELNO’ , ) ,
),
);
statsup=CALC_CHAMP (
RESULTAT=stat2 ,
GROUP_MA = ( ’panel’ , ) ,
CRITERES = ( ’SIEQ_ELNO’ , ’SIEQ_NOEU’ , ) ,
#11 Re: Code_Aster usage » three point beam bend nodal reac vs displacement error. » 2021-05-26 08:10:03
COMPORTEMENT=_F(DEFORMATION='GROT_GDEP',
GROUP_MA=('beam_full', ),
RELATION='ELAS'),
change above and converge
#12 Re: Salome-Meca installation » 2018 is working, Sigsev Fault on 2019 for Ubuntu 18.04 » 2021-05-25 07:39:41
# Choice of the version to patch
SMECA_VERSION=2020.0.1_universal_universal
XTLIBS_URL=https://www.code-aster.org/FICHIERS/sm2019VM/sm19_ubuntu18_xtlibs.tgz
LAUNCHER_URL=https://www.code-aster.org/FICHIERS/sm2019VM/salome
cd $HOME/salome_meca/appli_V${SMECA_VERSION//-1-univ/_univ}
wget $XTLIBS_URL --no-check-certificate -O xtlibs.tgz
tar xvf xtlibs.tgz
mv salome salome_gpu
wget $LAUNCHER_URL --no-check-certificate -O salome_mesa && chmod ugo+x salome_mesa
ln -s salome_mesa salome2
above command run in new terminal.
#13 Re: Salome-Meca installation » 2018 is working, Sigsev Fault on 2019 for Ubuntu 18.04 » 2021-05-22 12:56:10
/home/scaaas/salome20/run.sh
paste attached run.sh at above shown path....
open run.sh...edit path(folder name of salome installation,,, in my computer it is salome20) in line 8 according to your sm2020 installation
then do,
cd /home/scaaas/salome20
./run.sh
enter
it should work,,,keep active internet connection ON
restart computer open ./salome2 or double click on salome2 and execute in terminal
#14 Re: Code_Aster usage » [SOLVED] No Result File Created when Simulating Two Volumes in Contact » 2021-05-21 07:52:25
you refer liasion mail tutorial
#15 Re: Code_Aster usage » [SOLVED] No Result File Created when Simulating Two Volumes in Contact » 2021-05-19 13:00:01
ww.code-aster.org/forum2/viewtopic.php?id=16249
You are missing one command refer shell to volume liasion mail . hope my understanding to your application is correct.
#16 Re: Code_Aster usage » three point beam bend nodal reac vs displacement error. » 2021-05-19 12:40:06
INTERPOL=('LOG','LIN', ),
try above.
#17 Re: Code_Aster usage » Harmonic analysis - acceleration base excitation » 2021-05-07 07:58:57
POURSUITE(LANG='EN',
PAR_LOT='NON')
field = CALC_CHAR_SEISME(DIRECTION=(0.0, 0.0, 1.0),
MATR_MASS=MA,
MONO_APPUI='OUI')
resharm = DYNA_VIBRA(BASE_CALCUL='PHYS',
CHAM_MATER=fieldmat,
EXCIT=_F(FONC_MULT=func2d,
VECT_ASSE=field),
INCREMENT=_F(LIST_INST=listr),
MATR_MASS=MA,
MATR_RIGI=KA,
MODELE=model,
SCHEMA_TEMPS=_F(SCHEMA='NEWMARK'),
SOLVEUR=_F(METHODE='MUMPS',
RENUM='AUTO'),
TYPE_CALCUL='TRAN')
table = POST_RELEVE_T(ACTION=_F(GROUP_NO=('load', ),
INTITULE='dz',
NOM_CHAM='DEPL',
OPERATION=('EXTRACTION', ),
RESULTANTE=('DZ', ),
RESULTAT=resharm))
restran = REST_SPEC_TEMP(METHODE='PROL_ZERO',
NOM_CHAM=('DEPL', 'ACCE', 'VITE'),
RESULTAT=resharm,
TOUT_CHAM='OUI')
table1 = POST_RELEVE_T(ACTION=_F(GROUP_NO=('load', ),
INTITULE='dfft',
NOM_CHAM='ACCE',
OPERATION=('EXTRACTION', ),
RESULTANTE=('DZ', ),
RESULTAT=restran))
table0 = POST_RELEVE_T(ACTION=_F(GROUP_NO=('load', ),
INTITULE='displ',
NOM_CHAM='DEPL',
OPERATION=('EXTRACTION', ),
RESULTANTE=('DZ', ),
RESULTAT=restran))
table2 = POST_RELEVE_T(ACTION=_F(GROUP_NO=('load', ),
INTITULE='VELOCITY',
NOM_CHAM='VITE',
OPERATION=('EXTRACTION', ),
RESULTANTE=('DZ', ),
RESULTAT=restran))
table3 = POST_RELEVE_T(ACTION=_F(GROUP_NO=('load', ),
INTITULE='ACCER',
NOM_CHAM='ACCE',
OPERATION=('EXTRACTION', ),
RESULTANTE=('DZ', ),
RESULTAT=resharm))
table4 = POST_RELEVE_T(ACTION=_F(GROUP_NO=('load', ),
INTITULE='VELOCITY',
NOM_CHAM='VITE',
OPERATION=('EXTRACTION', ),
RESULTANTE=('DZ', ),
RESULTAT=resharm))
IMPR_RESU(FORMAT='MED',
RESU=_F(RESULTAT=resharm),
UNITE=80)
IMPR_TABLE(FORMAT='XMGRACE',
IMPR_FONCTION='OUI',
LEGENDE_X='TIME-SEC',
LEGENDE_Y='DISPLCEMENT',
MARQUEUR=0,
NOM_PARA=('INST', 'DZ'),
PILOTE='EPS',
STYLE=1,
TABLE=table,
TITRE='DISPL VS TIME',
UNITE=13)
IMPR_TABLE(FORMAT='XMGRACE',
LEGENDE_X='FREQUENCY',
LEGENDE_Y='AMPLITUDE',
MARQUEUR=0,
NOM_PARA=('FREQ', 'DZ'),
PILOTE='EPS',
STYLE=1,
TABLE=table1,
TITRE='ACCELERATION AS INPUT',
UNITE=29)
IMPR_TABLE(FORMAT='XMGRACE',
IMPR_FONCTION='OUI',
LEGENDE_X='FREQ',
LEGENDE_Y='AMPLITUDE',
MARQUEUR=0,
NOM_PARA=('FREQ', 'DX'),
PILOTE='EPS',
STYLE=1,
TABLE=table0,
TITRE='DISPLACEMENT AS INPUT',
UNITE=12)
IMPR_TABLE(FORMAT='XMGRACE',
IMPR_FONCTION='OUI',
LEGENDE_X='FREQ',
LEGENDE_Y='AMPLITUDE',
MARQUEUR=0,
NOM_PARA=('FREQ', 'DZ'),
PILOTE='EPS',
STYLE=1,
TABLE=table2,
TITRE='VELOCITY AS INPUT',
UNITE=10)
IMPR_TABLE(FORMAT='XMGRACE',
IMPR_FONCTION='OUI',
LEGENDE_X='TIME SEC',
LEGENDE_Y='ACCELERATION -MM/SEC2',
MARQUEUR=0,
NOM_PARA=('INST', 'DZ'),
PILOTE='EPS',
STYLE=1,
TABLE=table3,
TITRE='ACCELERATION VS TIME',
UNITE=11)
IMPR_TABLE(FORMAT='XMGRACE',
IMPR_FONCTION='OUI',
LEGENDE_X='TIME-SEC',
LEGENDE_Y='VELOCITY MM/SEC',
MARQUEUR=0,
NOM_PARA=('INST', 'DZ'),
PILOTE='EPS',
STYLE=1,
TABLE=table4,
TITRE='TIME VS VELOCITY',
UNITE=14)
FIN()
#18 Re: Code_Aster usage » Harmonic analysis - acceleration base excitation » 2021-05-07 07:56:56
Below .comm can give you idea.
DEBUT(LANG='EN')
mesh = LIRE_MAILLAGE(UNITE=20)
model = AFFE_MODELE(AFFE=_F(MODELISATION=('3D', ),
PHENOMENE='MECANIQUE',
TOUT='OUI'),
MAILLAGE=mesh)
mater = DEFI_MATERIAU(ELAS=_F(E=210000.0,
NU=0.3,
RHO=7.8e-09))
fieldmat = AFFE_MATERIAU(AFFE=_F(MATER=(mater, ),
TOUT='OUI'),
MODELE=model)
listR = DEFI_LIST_REEL(DEBUT=0.0,
INTERVALLE=_F(JUSQU_A=150.0,
PAS=0.1))
formula = FORMULE(NOM_PARA=('INST', ),
VALE='sin(2*pi*205.0*INST)')
func2d = CALC_FONC_INTERP(FONCTION=formula,
INTERPOL=('LIN', ),
LIST_PARA=listR,
PROL_DROITE='LINEAIRE',
PROL_GAUCHE='EXCLU')
load = AFFE_CHAR_MECA(MODELE=model,
PESANTEUR=_F(DIRECTION=(0.0, 0.0, -1.0),
GRAVITE=9850.0,
GROUP_MA=('vol', )))
load0 = AFFE_CHAR_MECA(DDL_IMPO=_F(GROUP_MA=('fix', ),
LIAISON='ENCASTRE'),
MODELE=model)
load3 = AFFE_CHAR_MECA(FORCE_FACE=_F(FZ=-10000.0,
GROUP_MA=('load', )),
MODELE=model)
ASSEMBLAGE(CHAM_MATER=fieldmat,
CHARGE=(load, load0),
MATR_ASSE=(_F(MATRICE=CO('ma'),
OPTION='MASS_MECA'),
_F(MATRICE=CO('ka'),
OPTION='RIGI_MECA')),
MODELE=model,
NUME_DDL=CO('nddl'),
VECT_ASSE=_F(CHARGE=(load3, ),
OPTION='CHAR_MECA',
VECTEUR=CO('fz')))
resharm0 = DYNA_VIBRA(BASE_CALCUL='PHYS',
CHAM_MATER=fieldmat,
EXCIT=_F(FONC_MULT=func2d,
VECT_ASSE=fz),
INCREMENT=_F(LIST_INST=listR),
MATR_MASS=ma,
MATR_RIGI=ka,
MODELE=model,
SCHEMA_TEMPS=_F(SCHEMA='NEWMARK'),
SOLVEUR=_F(METHODE='MUMPS',
NPREC=11,
PCENT_PIVOT=2000,
RENUM='AUTO'),
TYPE_CALCUL='TRAN')
restran = REST_SPEC_TEMP(METHODE='PROL_ZERO',
NOM_CHAM=('ACCE', ),
RESULTAT=resharm0,
SYMETRIE='OUI',
TOUT_CHAM='OUI')
table = POST_RELEVE_T(ACTION=_F(GROUP_NO=('load', ),
INTITULE='dfft',
NOM_CHAM='ACCE',
OPERATION=('EXTRACTION', ),
RESULTANTE=('DZ', ),
RESULTAT=restran),
TITRE='LISTR=1000')
table1 = POST_RELEVE_T(ACTION=_F(GROUP_NO=('load', ),
INTITULE='DISPLACEMENT',
NOM_CHAM='DEPL',
OPERATION=('EXTRACTION', ),
RESULTANTE=('DZ', ),
RESULTAT=resharm0))
IMPR_TABLE(FORMAT='XMGRACE',
IMPR_FONCTION='OUI',
LEGENDE_X='frequency',
LEGENDE_Y='amplitude',
NOM_PARA=('FREQ', 'DZ'),
PILOTE='EPS',
TABLE=table,
UNITE=29)
IMPR_TABLE(FORMAT='XMGRACE',
IMPR_FONCTION='OUI',
LEGENDE_X='TIME-SEC',
LEGENDE_Y='DISPL-MM',
MARQUEUR=0,
NOM_PARA=('INST', 'DZ'),
PILOTE='EPS',
STYLE=1,
TABLE=table1,
UNITE=10)
FIN()
#19 Re: Code_Aster usage » Singularity error when trying to simulate 3D 3 point Bending. » 2021-04-26 10:01:48
the attached .comm is working. first make simple load steps then tune .comm to complexity.
you can modify on attach .comm file.
#20 Re: Code_Aster usage » Singularity error when trying to simulate 3D 3 point Bending. » 2021-04-24 08:42:05
ADD Below steps as well as per your contact groups, It should work or re-send .comm file after making changes
mesh = MODI_MAILLAGE(reuse=mesh,
MAILLAGE=mesh,
ORIE_PEAU_3D=_F(GROUP_MA=('pincont', 'rackcon')))
mesh = DEFI_GROUP(reuse=mesh,
CREA_GROUP_MA=_F(NOM='tout',
TOUT='OUI'),
CREA_GROUP_NO=_F(GROUP_MA=('tout', )),
MAILLAGE=mesh)
mesh0 = CREA_MAILLAGE(CREA_POI1=_F(GROUP_NO=('tout', ),
NOM_GROUP_MA=('ressorts', )),
MAILLAGE=mesh)
model = AFFE_MODELE(AFFE=(_F(MODELISATION=('3D', ),
PHENOMENE='MECANIQUE',
TOUT='OUI'),
_F(GROUP_MA=('ressorts', ),
MODELISATION=('DIS_T', ),
PHENOMENE='MECANIQUE')),
MAILLAGE=mesh0)
elemprop = AFFE_CARA_ELEM(DISCRET=_F(CARA='K_T_D_N',
GROUP_MA=('ressorts', ),
VALE=(0.1, 0.1, 0.1)),
MODELE=model)
#21 Re: Code_Aster usage » CALC_FATIGUE - with mean stress » 2021-04-13 14:31:11
download tar.gz as given above, it has steps giiven
#22 Re: Code_Aster usage » CALC_FATIGUE - with mean stress » 2021-04-12 13:49:30
though the post is old, but very much important.
the changes as suggested in CA14.6 programme is not yet made.
Though i would like to know, the below ffigures shows damage in some unit meter or mm for particular selected node.
No correction POST: 2.275e-06
No correction CALC: 1.806e-06
Goodman POST: 2.480e-06
Goodman CALC: 2.165e-06
Gerber POST: 2.324e-06
Gerber CALC: 1.891e-6
I am intrested to find Gerber Factor of Safety & Goodman Factor of Safety Values. IS it possible with CA14.6 . Can anybody guide.
#23 Re: Code_Aster usage » OPENTURNS - Error in Non Stat Linear Analysis » 2021-04-07 18:47:31
I will try your suggestion.
#24 Re: Code_Aster usage » Sheet shearing process » 2021-04-03 07:59:40
Great work Miib.
#25 Re: Salome-Meca usage » [SOLVED]le GROUP_MA massN ne fait pas partie de maillage mesh » 2021-04-02 09:08:16
elempro1 = AFFE_CARA_ELEM(DISCRET=(_F(CARA='K_T_D_N',
GROUP_MA=('massN', ),
REPERE='GLOBAL',
VALE=(0.1, 0.1, 0.1)),
_F()),
MODELE=model)
Make above change and re-run.
Board footer