Code-Aster comm file for Hyper-Elastic Materials

I have just stumbled upon this wonderful software combination (Code-Aster + Salome) and am begining to learn it.

Has somebody used Code-Aster for the analysis of Hyper-Elastic Matrials? Since my knowledge of French is minimal (or poor) any help would be very much appreciated. I have trouble understanding some of the French documentation. If somebody could post an example of Non-Linear Stress Analysis of Hyper-Elastic Matrials that would be a big boon.

Thanks
JMB

Hey, sorry to say that I haven't performed any analysis of Elastics (not something I'm working with).

In the case of documentation, I intend to contribute to providing some English docs. Right now though I'm working on getting Eficas setup with i18n w/ gettext. This is my main focus for now, that and I was waiting on a reply to one of my posts from \"admin\" about providing the original documentation in *.doc or something similar. If anyone see's the doc's available please post a link.

Perhaps another user has something similar or at least can point you in the right direction.

-Jason

Jason,

Thanks for your reply. I just translated U42101h.pdf into a MS-Word format *.doc file using Google Translate Tools & OpenOffice 2.0. I will perhaps work on others based on how much French I can understand & time I have.

Would this work help you?

JMB

Hi,

I am sorry to say that at the present time, there are no Mooney-Rivlin hyperelastic law in Code-Aster.

So at the present time, there is no option for this kind of simulation in Aster, but as the code is open, I hope that someone will add this model in the future.

If you need this law, please try to ask for it on Code-Aster forums just to show that there is an interest for such addition to the code.

Yes, yes it would help!
Much like admin has said, the documentation needs some translation contributors.
So, the biggest hurdles that I see for non-French speaking people is

1 ) Eficas is hard to use due to no localization
2 ) Documentation is hard to understand due to no localization and \"broken translations\" from software based translators.

Granted, the software translators work great for getting the majority of the document/string/phrase/etc.. into your native language. But they obviously do not spit out perfect translations either. Hence, I propse using the translation software for moving the majority of the documents over, and then have a native speaker revise the grammar and such for that language.

Now the big question... how do we bring this all together?
Temporarily fork Eficas/Documentation to get everything localized and then dump it all back to the CA team?
Or do we join the CA team? (To be honest, I do not know how the CA team is put together, let alone if people are allowed to join with Dev access.)

Would a wiki be a good way to help move the documentation?

Eitherway, I think the community (apparently just 2-4 of us) that wants localized versions should come together with a common site/host/etc.
Perhaps CAELinux could be the place for this, as opposed to starting up something new.

Thoughts?

Great Idea: I will try to setup a wiki on CAElinux !!

For more details, see answer to this post (same topic...):
caelinux.com/CMS/index.php?option=com_si...tid=2&id=291#291

I don't know much about software translators but for this huge task, your proposition seems the most practical one, so let's try this way... and we will see how to improve the translations in a second step.

What is the exact procedure that you would propose, with which translation softwares and which file formats?