Notice

The forum is in read only mode.

Time-history analisys

Jay Cloud
Topic Author
Offline
New Member

11 years 1 month ago - 11 years 1 month ago #7461 by Jay Cloud

Time-history analisys was created by Jay Cloud

Hello,

I've been using Salome & Code_Aster for just a few weeks and I'm not very familiar with them (mainly Code_Aster).
Right now, I need to do an "experiment" with a cylindrical specimen, and first of all I need to perform a time-history analysis of this specimen. I read documentation about this topic (Module 3 : Dynamic analysis here ) and also followed this contribution dynamicload by Kees Wouters, which covers almost everything I need for this first analysis.

But, I can't make it work. Not even using the same files provided in the contribution site (I had to change a few things in the COMM file, I guess because of the version of EFICAS or something).

I have these problems:
- Every time I try to use ASTK (which I have to say I was never able to run successfully), an "Infor: Warning" window appears (see infor_warning.png in the attachment). Then, when I make it run, it does nothing (see astk_log in the attachment).
- If I do not use ASTK and run Aster within Salome (Aster Module > Run), the MESS file gives this error message:

<EXCEPTION> <DVP_97>  
Erreur signalée dans la bibliothèque MED
nom de l'utilitaire : MFCOOL
code retour : -217

(see MESS file in the attachment for further output). I found similar error messages in the forum but it did not help me to solve it.

I also tried both using the python script in the downloaded files and creating my own geometry&mesh (the same as the one provided in the script). Did not work either (not sure if this would make any difference though).
I don't know what else to do.

Thanks in advance for any help.
Regards,

Jay

EDIT: I just realized I posted in the wrong place. Maybe it should be in "Finite Element Modelling - Code_Aster". But I don't know how to delete the entire topic, so please any moderator deletes/moves it. Thanks.

Last edit: 11 years 1 month ago by Jay Cloud.

Claus
Offline
Moderator

11 years 1 month ago #7462 by Claus

Replied by Claus on topic Re: Time-history analisys

Helloo

You have given the wrong UNITE for the mmed file - .comm file says 20, but ASTK says 21. See where that takes you.

As for the ASTK warning; that's because there's a file with a white space in it's name in the folder you access. It doesn't matter for the launch or run of the computation, but can be annoying as hell.

/C

Code_Aster release : STA11.4 on OpenSUSE 12.3 64 bits - EDF/Intel version

kwou
Offline
Moderator

11 years 1 month ago - 11 years 1 month ago #7463 by kwou

Replied by kwou on topic Re: Time-history analisys

Hoi JayJay

you have to make the mesh file (type mmed, cylload.mail.med) readable (D) in ASTK, not writable (R). Check the first column (D) in the ASTK GUI instead of the second (R).

In the mess file:
meshinit cannot be read because of this setting.
See www.caelinux.org/wiki/index.php/Contrib:...rs/shell/static/astk and Claus' remark above (he added his remark while I was making up this - once again beaten by /C, sorry Claus).

And I know I have to update these files again. Code Aster changed a lot since the days I wrote the tutorial. So if you run into problems, please let me know and I will try to update it.
Eg.

meshmod=CREA_MAILLAGE(MAILLAGE=meshinit,
                      MODI_MAILLE=(_F(TOUT='OUI',
                                      OPTION='QUAD8_9',),
                                   _F(TOUT='OUI',
                                      OPTION='TRIA6_7',),),);

can now be omitted and the centre nodes can be added in Salome7.3.0 (but if you use quadratic elements the command file should still work as is.

The infowarning message is more annoying than an error. It means you have an 'incorrect' character in your path name, eg space as indicated by the info.

If you have more problems, pls let us know.

Interest: structural mechanics, solar energy (picture at 'my location' shows too little pv panels)

--
kind regards - kees

Last edit: 11 years 1 month ago by kwou.

Jay Cloud
Topic Author
Offline
New Member

11 years 1 month ago - 11 years 1 month ago #7470 by Jay Cloud

Replied by Jay Cloud on topic Re: Time-history analisys

Hello,

claws wrote: You have given the wrong UNITE for the mmed file - .comm file says 20, but ASTK says 21. See where that takes you.

I think I understand what you mean, but reading the COMM file I'm not so sure:

COMM FILE

meshinit=LIRE_MAILLAGE(FORMAT='MED',
                       INFO=1,);

....

IMPR_RESU(FORMAT='MED',
          UNITE=21,
          RESU=_F(MAILLAGE=meshinit,
                  RESULTAT=SALmodes,
                  NOM_CHAM='DEPL',),);

Where does the COMM file say UNITE=20 for the mmed (mmed is not med(maillage) file, right?) file? Am I looking at the wrong part of the file? The complete COMM file is attached.
Maybe I have a completely wrong idea of the terms med, mmed... and that's why I don't know what you mean. :unsure:

claws wrote: As for the ASTK warning; that's because there's a file with a white space in it's name in the folder you access. It doesn't matter for the launch or run of the computation, but can be annoying as hell.

Reading the <INFO> warning message I supposed it was because of a white space in the name of a file/folder. But there is no file/folder with a white space in the path I use actually (/user/Desktop/ usually), so I don't know what to do. And yes, it's annoying as hell...

Thank you very much for your help.

keeswouters wrote: you have to make the mesh file (type mmed, cylload.mail.med) readable (D) in ASTK, not writable (R). Check the first column (D) in the ASTK GUI instead of the second (R).

I changed this. Still does not run (the MESS file gives the same error -attached-).

   meshinit=LIRE_MAILLAGE(INFO=1,
                         INFO_MED=1,
                         VERI_MAIL=_F(APLAT=1.E-3,
                                      VERIF='OUI'),
                         UNITE=201,
                         FORMAT='MED',
                         );

   <EXCEPTION> <DVP_97> 
                                                         
Erreur signalée dans la bibliothèque MED 
nom de l'utilitaire : MFCOOL                    
code retour : -217                                  

 Il y a probablement une erreur dans la programmation. 
Veuillez contacter votre assistance technique.

Also, I read the ASTK configuration in your link. I have all settings set correctly (same as those you recommend).

I have another problem (related with the ASTK configuration I guess). Many times when I'm using the ASTK GUI to open an ASTK file for example, the FILE BROWSER does not show all the folders that I have in my computer. I usually have folders in /Desktop/folder_name, and when I try to look for files within that folder, the browser shows no folder in the Desktop.

As for the COMM files, that's right, the syntax in Code_Aster has changed a lot in the last versions. However, using EFICAS to open COMM files lets you know when there are commands not understood by Eficas itself (it shows an error message with the incorrect command and the line in the COMM file where it is). So it has not been a big deal for me to "adapt" comm files for my Code_Aster version.

Thank you very much as well.

Regards,
Jay

Last edit: 11 years 1 month ago by Jay Cloud.

Claus
Offline
Moderator

11 years 1 month ago #7476 by Claus

Replied by Claus on topic Re: Time-history analisys

From you ASTK screenshot I can see that the 'mmed' file is set as 21. Since no UNITE is given in the .comm file, it defaults to 20.That's the discrepancy.
When I you look in the mess file where Code_Aster begin to parse the file, it fills in the blanks that it needs, so this portion gives more information when troubleshooting.

'mmed' is the MED file format for input mesh, so you should select 'mmed' as D (for data) and 'rmed' as R (result) for your OUTPUT file - i.e. the file you write to in the IMPR_RESU function.

These are usually tow different files.

--

As for folders not showing up, that's also because of white spaces in files names. Create a folder just for your calculations and make sure there are no white spaces in there. That will solve your problem.

/C

Code_Aster release : STA11.4 on OpenSUSE 12.3 64 bits - EDF/Intel version

Jay Cloud
Topic Author
Offline
New Member

11 years 1 month ago #7477 by Jay Cloud

Replied by Jay Cloud on topic Re: Time-history analisys

Hello again,

So I was wrong with the meaning of mmed in ASTK. That's why I thought UNITE=20 was not set anywhere.
Sorry for being so annoying, but it still does not run.

mmed is the imput MED file, so it should be LU=20 in ASTK.

rmed is set to LU=80 by default. If it is the output file used in the IMPR_RESU function, it is given UNITE=21 in the .comm file.

IMPR_RESU(FORMAT='MED',
          UNITE=21,
          RESU=_F(MAILLAGE=meshinit,
                  RESULTAT=SALmodes,
                  NOM_CHAM='DEPL',),);

I tried both LU=80 and LU=21.

I don't know what mast is ("kept for reason of compatibility" is the description given in [U1.04.00] Interface d’accès à Code_Aster : astk). I don't know what to do with it, so I just left it by default.

erre, mess, resu & base types are set by default. Do I have to change any of them?

The screenshot attached shows the ASTK GUI, and the four files at the left of the image are the files within the folder used for calculations (.comm, .astk & .med files; also the .py file used for geometry).

And I don¡t know what to do. What's wrong??

Thank you very much again.
Regards,
Jay

Moderators: catux

Time to create page: 0.151 seconds

Notice

Time-history analisys

Attachments:

Attachments:

Attachments:

Main Menu

Forum

Login Form