Bridge between Mecway and Code-Aster

KundertdeWitKundertdeWit
Hi all,

I have been long time looking for a nice GUI for Code-Aster. I have been using Salome-Meca, but always find it too tedious to use. In the first half of this year I established the working principle of a bridge between Mecway as pre-/post processor and Code-Aster as a solver. That structure proved to work. After that I didn’t have time to spent on it until last week. My son is programming a lot with Claude Code, and this week he didn’t have time to use it because of his homework 😊. So I was allowed to spent his weekly limit. Unfortunately, it worked out quite well and I decided to unlock more of Code-Aster than I normally use. As a result, the MecwayAsterBridge grew quiet large in capabilities. You can find it here: https://github.com/trednuK/MecwayAsterBridge

I have added a lot of validation checks and documentation. However, since it is build by AI, it still needs human verification to find edge cases which only appear in daily use.

Enjoy using it and please let me know if you have any suggestions or find some bugs.

Kind regards,
Kundert

Comments

  • SergioSergio
    Amazing, will try to test it during this wekeend. These days the developers with the help of IAs has bring us several new tools for the FEA enthusiasts! Look for FEMaster, CCXView, and now MecwayAsterBrige!
  • SergioSergio
    Amazing, my first no lineal traction test:


  • FatmacFatmac
    wonderful bit of coding. Great to be able to couple all the benefits of Mecway GUI with another capable solver. Thank you for sharing ur creation. I have already managed to run several of the examples, neat. So far I have only being using version 34 of MW, and for the supplied examples it all appears to work just fine. However, I have run into some errors when I build my own models within MC. I get this error
    â•‘ â•‘
    â•‘ â•‘
    â•‘ Erreur de syntaxe dans AFFE_CHAR_MECA â•‘
    â•‘ â•‘
    â•‘ At least one argument of ('TOUT', 'GROUP_MA', â•‘
    â•‘ 'GROUP_NO', 'NOEUD') must be defined â•‘
    â•‘ â•‘
    ║ Exception détaillée ci-dessous. ║
    I did wonder if it is something to do with defining points or surfaces and played around but got now where. Is there something obvious I'm doing wrong? I have attached a sample of a simple model that i have got stuck on

  • joanmjoanm
    Kundert, thank you very much! :)
  • SergioSergio
    @Fatmac , I just remove the CCX custom card and apply the restrain to the defined face group (it was applied to the same faces but selected directly) and then works ok.
  • SergioSergio
    edited October 12
    @KundertdeWit , can you share some example using TIE on two shells (surface to suface)? I have make it work TIE with solid, but not with shells
  • FatmacFatmac
    Sergio
    1:11AM
    @Fatmac , I just remove the CCX custom card and apply the restrain to the defined face group (it was applied to the same faces but selected directly) and then works ok.

    thanks Sergio - that appears to be all that was wrong -that has open the door to more fun!
  • MishalMishal
    @KundertdeWit you are a beast of note!!! Can't wait to try this out!!!!
  • MishalMishal
    Is this an issue with laptop or is everyone elses interface looking like this?


  • SergioSergio
    @Mishal I have run in a notebook with basic resolution (1920X1080) and with scaled fonts without such problem.
  • FatmacFatmac
    My interface looks like the one shown by Mishal. I can't find a way to improve it. Dell Inspiron W11
  • MishalMishal
    It seems to be working fine on my end now. I was playing with the tool during a meeting and didn't have my extra screens with me. All is working perfectly now
  • KundertdeWitKundertdeWit
    @Sergio, regarding 'can you share some example using TIE on two shells (surface to suface)? I have make it work TIE with solid, but not with shells'

    I am not sure about TIE with shells. I will look it up for you, but give me some time.
    In the meanwhile, you could try using normal Code-Aster commands via #Aster-keywords (you can read about it in the help-documents of the bridge). Not sure if that will help, and did not test it myself up to now.
  • MishalMishal
    I have added some extra functionality for beam elements, offsets, geometric nonlinear analysis, fixed the oriantation issues.

    Please refer to the below link. I have not pushed it to my main brach as yet.
    @KundertdeWit, I am not an expert with Github (just a basic user) we can possibly merge all our changes at some point, I see that you have updated your repository once already, my fork of yours has had a few changes today.

    https://github.com/mishal0488/MecwayAsterBridge/tree/dev
  • SergioSergio
    @KundertdeWit and @Mishal thanks for this efforts! I´m running in Mecway v34, so maybe you could update the requeriments and add this version too.
  • KundertdeWitKundertdeWit
    edited October 16
    @ Mishal,
    I did the same :-), I was reading your post just now. I checked if my changes cover yours, which is not the case. I will add this to the next release, which will be available tonight I think
    Release 2026.2 is available just now, with some other improvements, including Mecway 34.
  • KundertdeWitKundertdeWit
    edited October 16
    @Sergio: in /TestFiles you can find an example with Tiecontact for plates
  • MishalMishal
    @KundertdeWit I will wait for your new release, merge it with mine and resolve any issues and then we canpossibly merge it back to your repository since that is the master.
  • KundertdeWitKundertdeWit
    edited October 16
    @Mishal, I have merged your work into my main branch. The new release 2026.3 is available now. Could you please check and test if it indeed covers your work?

    Could you also check the frequency analysis again (in another forum thread), regarding the orientation of beams.

    Thanks for your work and kind regards,
    Kundert
  • SergioSergio
    @KundertdeWit , I has tested the new release and it works very well, and run the modal analysis and found exactly the same results as Mecway. For some reason in the Code_Aster results the displacement/magnitud is not computed



    I have added some issues/feature request in the Github page, related to add some buttons in the convergence window to access directly to Code_Aster comm, mail and med result files.

    This new bridge is incredible, the way bc and results are translated directly is amazing.
  • MishalMishal
    @KundertdeWit Thanks for the merge. You may want to merge one more time from my branch. I have managed to get the end releases working for geometric nonlinear analysis of beam elements.

    I may not make any modification and changes for a while since my workload is currently high.
  • KundertdeWitKundertdeWit
    @Sergio, @Mishal,

    Many thanks for your valuable input.
    It has been added to version 2026.4, which is available now
    @Mishal: the functionality has been added, but a bit differently than you did it. Please check if this indeed does what it should do.
  • SergioSergio
    Thanks @KundertdeWit , have tested with an hyperelastic model and found that if the solver didn´t reach the full specified load/displacement, it doesn´t save the incomplete results.
Sign In or Register to comment.

Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Sign In Register