Welcome to the forums. Please post in English or French.

You are not logged in.

#1 2011-03-02 16:54:29

gildas_68
Member
Registered: 2011-03-02
Posts: 1

éléments finis de coque composites en thermoélasticité et grandes défo

Aujourd'hui j'utilise un éléments finis de coques composites, élément S8RT d'Abaqus. Cet élément me permet de résoudre des analyses thermiques et mécaniques entièrement couplées, dans le cadre des grandes transformation, et plus particulièrement en grand déplacement. Les particularité de ces analyses sont

"Assignement" de repère matériaux qui suivent la déformée de la structure (prise en compte de l'évolution des directions d'anisotropie)
Utilisation dans l'équation de conservation de l'énergie d'un terme de production volumique de chaleur, terme qui peut être assigné de manière différente à chacune des couche du composite et qui est traité grâce à une subroutine utilisateur


Au travers de la documentation j'ai eu du mal a trouver ces informations et les possibilités offertes par les différents éléments de coques

J'aimerais donc avoir une aide en ce sens notamment sur la faisabilité ou non de ce type d'analyse avec code-aster

par avance merci

Gildas

Offline

#2 2011-03-02 23:23:55

todd_alan_martin
Member
Registered: 2008-03-06
Posts: 131

Re: éléments finis de coque composites en thermoélasticité et grandes défo

Hi Gildas

Given the general level of interest in composite shells demonstrated by the EDF team so far, I would guess you will be waiting a long time for this functionality!

Todd

Offline

#3 2011-03-03 17:47:05

Johannes_ACKVA
Member
From: Ingenieurbüro für Mechanik, DE
Registered: 2009-11-04
Posts: 756
Website

Re: éléments finis de coque composites en thermoélasticité et grandes défo

Todd, is this a critics? I think this is not adequate and not fair. What is given in this forum is given without pay and from volunteers!!! In my opinion this forum has high quality, even if not all question are answered. Consider that even by a commerial software company not all problems would by solved!

Regards,
Johannes Ackva

______________________________________________________________________
Ingenieurbüro für Mechanik
Dr.-Ing. Johannes Ackva
Markgrafenstr. 21
D 91717 Wassertrüdingen

*** Next Introduction Course  to Salome and Code-Aster: Wednesd 13 to Saturd.16 of April  in Wassertrüdingen ***


Ingenieurbüro für Mechanik
D 91717 Wassertrüdingen / Germany

www.code-aster.de                                                Training & Support for NASTRAN and CODE-ASTER

Offline

#4 2011-03-04 03:31:46

todd_alan_martin
Member
Registered: 2008-03-06
Posts: 131

Re: éléments finis de coque composites en thermoélasticité et grandes défo

Boo hoo. My comment was slightly inaccurate. I should have said a VERY long time.

Offline

#5 2011-03-04 19:45:33

JMB365
Member
Registered: 2008-01-19
Posts: 781

Re: éléments finis de coque composites en thermoélasticité et grandes défo

Johannes_ACKVA wrote:

What is given in this forum is given without pay and from volunteers!!! In my opinion this forum has high quality, even if not all question are answered. Consider that even by a commerial software company not all problems would by solved!
Johannes Ackva

Hello Johannes,

I have seen many open source projects in my association with the Linux world over the decades, but none so opaque as the CodeAster / Salome projects.  The lack of a pubic bug tracker and reporting process shows a DISREGARD for the end user's bug reporting process.  I request you to examine and compare this to many other Open Source Software (OSS) projects vis-a-vis this sub-par level of public bug reporting/documentation/assignment/closure process.  We are not expecting all problems to be SOLVED, just asking to make the bug reporting/documentation/assignment/closure process VISIBLE !!!

Yes there are many OSS projects that are worse and languishing, but there are also those that exemplify and shine!  In the OSS universe much is done by volunteers and WITHOUT pay!  Let us use the better ones to benchmark and improve CA, not compare it to those that are worse; in order to sing its praises.

Regards,
JMB

Last edited by JMB365 (2011-03-04 20:46:13)


SalomeMeca 2021
Ubuntu 20.04, 22.04

Offline

#6 2011-03-04 22:12:52

AsterO'dactyle
Administrator
Registered: 2007-11-29
Posts: 421

Re: éléments finis de coque composites en thermoélasticité et grandes défo

We take care of all comments and every bug's report.


Code_Asterの開発者

Offline

#7 2011-03-04 22:14:23

AsterO'dactyle
Administrator
Registered: 2007-11-29
Posts: 421

Re: éléments finis de coque composites en thermoélasticité et grandes défo

todd_alan_martin wrote:

Hi Gildas

Given the general level of interest in composite shells demonstrated by the EDF team so far, I would guess you will be waiting a long time for this functionality!

Todd

Sure !


Code_Asterの開発者

Offline

#8 2011-03-05 01:01:38

todd_alan_martin
Member
Registered: 2008-03-06
Posts: 131

Re: éléments finis de coque composites en thermoélasticité et grandes défo

AsterO'dactyle wrote:

We take care of all comments and every bug's report.

But the problem is there is no transparency! Every comment and bug reported simply disappears into a black hole.

How about this bug then? Submitted in December last year. http://www.code-aster.org/forum2/viewtopic.php?id=14683
I haven't heard anything more about it. Has it been assigned to anyone? Is anyone actively working on it? How would I know?

There is no road map for future developments. There is no facility to log requests for new features or see other user's requests. There is no opportunity to communicate with anyone who actually has knowledge in a particular area, because EDF manage the code-aster project behind an iron curtain.

So am I critical? Yes!

Todd.

Last edited by todd_alan_martin (2011-03-05 01:06:25)

Offline

#9 2011-03-07 13:26:56

Christophe Durand
Nuclear Fuel Division
From: EDF
Registered: 2007-11-22
Posts: 145
Website

Re: éléments finis de coque composites en thermoélasticité et grandes défo

Hi to all,

Thanks for yout input on the matter of the Code_Aster development process. Here is the EDF's point of view regarding this argument.

Indeed, what we call our inner « bug-tracker » is private and we do not plan to open it. Several companies or academic entities (other than EDF) have access to it but it is strictly framed by co-development agreements, with legal duties for the both parts.

What are the reasons for keeping EDF's bug-tracker private ?
- Most of the time, a bug report shows more or less of the study in object (attachments for bug replay). Showing EDF's computations, especially the ones connected to nuclear studies, cannot be considered.
- Our bug-tracker is also our tool for managing all the Code_Aster improvements. It is EDF's privilege to keep private the development plan of Code_Aster, our current subjects of technical interest and so on.
- Fixing the bugs related to EDF's engineering version of Code_Aster is a very strict duty for us, framed within a specific process. In spite of the great attention we pay to feedbacks from the open-source community, we cannot manage these bug alerts indistinctly from those coming from our engineering departments.

Does EDF takes care of the feedbacks ?
Yes, of course ! Most of the time and in spite of Todd-Alan counter-example of december :
- people who post a description of a bug are warmly thanked,
- someone of the core-team spends the time to analyse the problem, validate or not the existence of the bug, transfer it in our (private) bug-tracker.
- a message in the thread warns the community when the bug is fixed.
I do not pretend that this organization is flawless but I cannot let people doubting of the willingness of the core-team (see for instance the following id threads on the forum : 18506, 13526, 13581, 13539, 13675, 13560, 14558, 13290, 13292, 24736, 24720, 14670).

Is it a shame for Code_Aster not to have a public bug-tracker ?
We do not think so. Numerous OSS projects do not. For instance one of the public libraries we use for algebric solving : MUMPS. And the question is biased because the forum acts as a  bug-tracker, as disconfortable as it can be.
On the contrary, please give us credit for opening a lot of things you will rarely see elsewhere : our huge documentation (including the reference documentation, a very important part of EDF's intellectual patrimony concerning mechanics), the weekly releases.

What could we do for helping the community ?
I agree with you concerning the awkwardness of using the forum threads as a vehicle for bug reports. A real opened bug-tracker would be more convenient. We are thinking about it. This is not a promise but the question will be examined with all the attention it deserves . Please note that this opened bug-tracker will be allways strictly distinct from the EDF's one for the reasons given above. You can see it as a displacement of a part of the forum towards a more convenient tool.

About EDF's interest in the composite models :
Well. Code_Aster, and the mechanical models it contains, is an image of EDF's subjects of interest, related to materials and structure that EDF has to deal with (nuclear powerplants, dams, turbine shafts ... ). So, in spite of being an all-purpose software in mechanics, Code_Aster has numerous forces (behaviours for steel and concrete, damage, contact ... ) and also weaknesses (including composites which are pretty rare in nuclear plants). As an open-source code, all the goodwills for improving or developping efficient finite elements for composites are obviously welcome.

Offline

#10 2011-03-08 19:10:23

JMB365
Member
Registered: 2008-01-19
Posts: 781

Re: éléments finis de coque composites en thermoélasticité et grandes défo

Hello Christophe Durant,

Thank you for the detailed explanation and reasons for the stance adopted by EDF vis-s-vis the private "bug tracker".  It is (and has been) clearly understood and acceptable to me that there are contractual and business reasons for keeping certain technological aspects of CodeAster private.  This modus operandi is very evident from the list of documents available on the website.  But I wish EDF could use its own model and adopt it for the opening up of the bugtracker!  Just as the entire list of documents is available, but certain ones are marked "access restricted" for the general public, so can a bug tracker be made semi-open.  Just list the problems that are being worked on, keeping the details of the private ones hidden from the general public.  I am sure in this century it is well within the realm of database coding or querying capabilities.

My other peeve: Permitting the general public access to the source documentation (*.doc, *.odt) instead of ONLY the *.pdf would assist the non-French user community in being able to translate the documents more easily into other languages.  I have repeatedly brought this to the attention of the CodeAster team; but I have seen no action in the past 4 years!  On occasion, I have manged to obtain a document here and there due to the kindness of some CodeAster member, but these are more like scraps of table food being tossed out the birds rather than a concerted, cohesive effort to allow usage of CodeAster in a language other than French.  There was some talk of automatically translated documents being made available last year.  Then something about it happening in April of this year.  Now I don't know if is even going to happen.

Which brings me to my third peeve.  There is no roadmap on the website.  If CodeAster were to publish a list of future enhancements with tentative milestones that would aid in the general public being more informed of what to look forward to.  A dedicated webpage to list them is one possibility I can suggest.

Please consider these requests once again with some gravity and seriousness too.  Thank you.

Regards, JMB

PS: If anybody feels that the main topic of this thread has been hijacked or led astray - my apologies.  I will gladly open a new topic for discussion instead.

Last edited by JMB365 (2011-03-08 19:13:24)


SalomeMeca 2021
Ubuntu 20.04, 22.04

Offline