looking for *.astk example file
- Alessandro
- Topic Author
- Offline
- Premium Member
-
Less
More
- Posts: 108
- Thank you received: 0
16 years 2 months ago #2632
by Alessandro
looking for *.astk example file was created by Alessandro
I have installed Salome 4.1.4 and Code_aster 9.4 on a Madriva-2009-64bit distribution.
It seems that all is wormking properly: salome, code_aster, eficas and astk, but the integration beetwen salome and code_aster is missed (things are not so easy as in the current caelinux), so I have to use ASTK as interface to code-aster.
Since I have no idea how ASTk works, does anybody has an *astk file to share, just to study how is it done? It would be very nice to have the astk file and the related mesh and the comm file, to check if my code-aster really works.
Thank you in advance.
It seems that all is wormking properly: salome, code_aster, eficas and astk, but the integration beetwen salome and code_aster is missed (things are not so easy as in the current caelinux), so I have to use ASTK as interface to code-aster.
Since I have no idea how ASTk works, does anybody has an *astk file to share, just to study how is it done? It would be very nice to have the astk file and the related mesh and the comm file, to check if my code-aster really works.
Thank you in advance.
- Alessandro
- Topic Author
- Offline
- Premium Member
-
Less
More
- Posts: 108
- Thank you received: 0
- kwou
-
- Offline
- Moderator
-
16 years 2 months ago #2636
by kwou
Interest: structural mechanics, solar energy (picture at 'my location' shows too little pv panels)
--
kind regards - kees
Replied by kwou on topic Re:SOLVED
Hoi Alessandro
yes, I had the same problem. I still had Salome 3.2.9 where Code Aster is integrated in Salome and used an *.astk file and *.export file from that version. I hope in the next stable version of Salome Aster will be integrated again.
I also had some problems with Astk and ran Code Aster via the *.export file: .../ASTK_SERV/as_run *.export. I still donot known how the *.export and *.astk files are linked together exactly.
Kind regards - kees<br /><br />Post edited by: Kees Wouters, at: 2009/02/19 14:13
yes, I had the same problem. I still had Salome 3.2.9 where Code Aster is integrated in Salome and used an *.astk file and *.export file from that version. I hope in the next stable version of Salome Aster will be integrated again.
I also had some problems with Astk and ran Code Aster via the *.export file: .../ASTK_SERV/as_run *.export. I still donot known how the *.export and *.astk files are linked together exactly.
Kind regards - kees<br /><br />Post edited by: Kees Wouters, at: 2009/02/19 14:13
Interest: structural mechanics, solar energy (picture at 'my location' shows too little pv panels)
--
kind regards - kees
- Alessandro
- Topic Author
- Offline
- Premium Member
-
Less
More
- Posts: 108
- Thank you received: 0
16 years 2 months ago #2637
by Alessandro
Replied by Alessandro on topic Re:SOLVED
Kees, I attach a simple whole study. I created it in salome 3.2.9 using the "Cugnoni" wizard, then exported it to ASTK:
1) Switch to aster module
2) Right click on the code aster case in the tree in the right pane of salome
3) Export to ASTK
Now ASTK opens and it should complete itself. In this way, you can understand what you have to write in the fields of ASTK.
The normal workflow without wizard is:
1) Crate the mesh in Salome, defining all groups, submeshes if needed, etc
2) Create comm file with Eficas
3) Export the mesh as *.med file
4) Open ASTK and fill in the blank spaces with the files to be used
ASTK requires that:
a) you define a work directory where it look for input-files and where it writes results of calculation
2) IMPORTANT: It seems to me that all the files of the analysis needs to stay in the same work directory.
Pay attention to this:
input mesh has *.med extension but mmed type (unit:20)
result mesh has still *.med extension but rmed type (unit:80).
Hope this help.
In the attach file you don't find the *med meshes files, to reduce the weight of the attached file. You can build the input mesh by exporting from the hdf study, after the mesh has been re-computed..
1) Switch to aster module
2) Right click on the code aster case in the tree in the right pane of salome
3) Export to ASTK
Now ASTK opens and it should complete itself. In this way, you can understand what you have to write in the fields of ASTK.
The normal workflow without wizard is:
1) Crate the mesh in Salome, defining all groups, submeshes if needed, etc
2) Create comm file with Eficas
3) Export the mesh as *.med file
4) Open ASTK and fill in the blank spaces with the files to be used
ASTK requires that:
a) you define a work directory where it look for input-files and where it writes results of calculation
2) IMPORTANT: It seems to me that all the files of the analysis needs to stay in the same work directory.
Pay attention to this:
input mesh has *.med extension but mmed type (unit:20)
result mesh has still *.med extension but rmed type (unit:80).
Hope this help.
In the attach file you don't find the *med meshes files, to reduce the weight of the attached file. You can build the input mesh by exporting from the hdf study, after the mesh has been re-computed..
Attachment manubrio_esempio_ASTK.gz not found
Moderators: catux
Time to create page: 0.135 seconds