Problem Running Aster Analysis [SOLVED]

  • Michael
  • Topic Author
  • Offline
  • New Member
  • New Member
More
7 years 8 months ago - 7 years 8 months ago #8724 by Michael
-- New CAELinux User -- -- Novice Linux User --

I'm not getting any results from an Aster analysis run, when trying out some basic tutorials. I can create the geometry and the mesh no problem, including .med, .hdf, and .comm files.

When I run the Aster analysis in Salome-Meca, I do not get any terminals windows popping up, no results in the Object Browser, no .mess files that I can see. Everything else seems to be going fine up to this point. I've tried at least three different tutorials with my being stopped in my tracks at this point. Once, when running the Aster analysis I did get an error on .comm file I modified, incorrectly. Once I fixed the error, it went back to usual.

I also had this problem when running CAELinux 2013 virtually, before the full install. My hope was that this would fix it.

Any ideas?


My platform is a Lenovo 4446 with a Pentium(R) Dual-Core CPU (X86_64), running non-updated CAELinux 2013 installed on my computer. I log in with a user other than root.
Last edit: 7 years 8 months ago by Michael.

Please Log in or Create an account to join the conversation.

  • Michael
  • Topic Author
  • Offline
  • New Member
  • New Member
More
7 years 8 months ago #8725 by Michael
I did create an .med, .mmed, .hdf, .export, and .comm file on my last attempt to run a static linear analysis on a cube. Being that I can't seem to attach the files, I've posted the .export and .comm file below if anyone cares to look them over. Is there anything else I could look at that would be insightful?

Thanks.

P uclient michael
P mclient uno
P follow_output yes
P display uno:0.0
P actions make_etude
P version STA10
P nomjob linear-static
P debug nodebug
P mode interactif
P ncpus 1
P memjob 262144.0
A memjeveux 32.0
P tpsjob 2
A tpmax 120
P username michael
P serveur localhost
P aster_root /opt/SALOME-MECA-2013.1/SALOME-MECA-2013.1-LGPL/tools/Code_aster_standalone_20131_public
P protocol_exec asrun.plugins.server.SSHServer
P protocol_copyto asrun.plugins.server.SCPServer
P protocol_copyfrom asrun.plugins.server.SCPServer
P proxy_dir /tmp
P consbtc oui
P soumbtc oui
P origine salomemeca_asrun 1.10.0
F comm /home/michael/Documents/Test Files/example_aster/cube_compression1.comm D 1
F mmed /home/michael/Documents/Test Files/example_aster/linear-static.mmed D 20
F mess /home/michael/Documents/Test Files/example_aster/linear-static.mess R 6
F resu /home/michael/Documents/Test Files/example_aster/linear-static.resu R 8
F rmed /home/michael/Documents/Test Files/example_aster/linear-static.rmed R 80
R base /home/michael/Documents/Test Files/example_aster/linear-static.base RC 0

DEBUT();

MA=DEFI_MATERIAU(ELAS=_F(E=210000000000.0,
NU=0.3,),);

MAIL=LIRE_MAILLAGE(FORMAT='MED',);

MAIL=MODI_MAILLAGE(reuse=MAIL,
MAILLAGE=MAIL,
ORIE_PEAU_3D=_F(GROUP_MA=('Top',),),
);

MODE=AFFE_MODELE(MAILLAGE=MAIL,
AFFE=_F(TOUT='OUI',
PHENOMENE='MECANIQUE',
MODELISATION='3D',),);

MATE=AFFE_MATERIAU(MAILLAGE=MAIL,
AFFE=_F(TOUT='OUI',
MATER=MA,),);

CHAR=AFFE_CHAR_MECA(MODELE=MODE,
DDL_IMPO=(
_F(GROUP_MA='bottom',
DX=0.0,
DY=0.0,
DZ=0.0,),
_F(GROUP_MA='faces_nx',
DX=0.0,),
_F(GROUP_MA='Top',
DY=0.0,),
),
PRES_REP=(
_F(GROUP_MA='Top',
PRES=1.0,),
),
);

RESU=MECA_STATIQUE(MODELE=MODE,
CHAM_MATER=MATE,
EXCIT=_F(CHARGE=CHAR,),);

RESU=CALC_ELEM(reuse=RESU,
MODELE=MODE,
CHAM_MATER=MATE,
RESULTAT=RESU,
OPTION=('SIGM_ELNO','SIEQ_ELNO',),
EXCIT=_F(
CHARGE=CHAR,),);

RESU=CALC_NO(reuse=RESU,
RESULTAT=RESU,
OPTION=('SIGM_NOEU', 'SIEQ_NOEU', ),);

IMPR_RESU(FORMAT='MED',
UNITE=80,
RESU=_F(MAILLAGE=MAIL,
RESULTAT=RESU,
NOM_CHAM=('SIGM_NOEU','SIEQ_NOEU','DEPL',),),);

FIN();

Please Log in or Create an account to join the conversation.

  • Michael
  • Topic Author
  • Offline
  • New Member
  • New Member
More
7 years 8 months ago #8726 by Michael
Well, I figured it out. It was the space in the directory path for my files, "./Test Files/." I had a feeling it was something simple, yet critical, as that. Syntax is always the silent killer.

I'm looking forward to getting past the basics and onto the good stuff!

Please Log in or Create an account to join the conversation.

Moderators: catux
Time to create page: 0.122 seconds
Powered by Kunena Forum