Continue to Site

Eng-Tips is the largest engineering community on the Internet

Intelligent Work Forums for Engineering Professionals

  • Congratulations cowski on being selected by the Eng-Tips community for having the most helpful posts in the forums last week. Way to Go!

Search results for query: *

  1. Abaqus_FEM

    Element birth and death in Abaqus Implicit

    Maybe you don't need to consider element birth/death in your simulation at all. You could model the weld bead as a part in the beginning of the simulation but prohibit any interaction with the rest of the model via GAPCON and FILM subroutines until the torch has passed. Here's a short document...
  2. Abaqus_FEM

    Learning FEA

    @Erik +1: Just enrolled for the course. Thank you for the link. If anyone has any similiar stuff, maybe for Abaqus as well, let us know! :-)
  3. Abaqus_FEM

    How to solve "Geometric correction data seems to be inconsistent"-Warning?

    You were right about the surface smoothing. That was the reason. However, I made a calculation with and without surface smoothing and the results were the same. So, my results so far shouldn't be negatively affected. Thanks again!
  4. Abaqus_FEM

    How to solve "Geometric correction data seems to be inconsistent"-Warning?

    Thank you for the fast reply! Maybe I should have mentioned, that I am using C3D8R elements. To be honest, I have no idea what I could actually do about the orientation of their element faces (if they were wrong)?! With shells, I'd know what to do, but not in this case. Could you explain that in...
  5. Abaqus_FEM

    How to solve "Geometric correction data seems to be inconsistent"-Warning?

    Hello there, today I had a "problem" with a model using imperfections and general contact in Abaqus standard. When I do not use the *imperfection keyword, there are no major warnings in my model. But as soon as I add imperfections, I get the warning message: "THE GEOMETRIC CORRECTION DATA...
  6. Abaqus_FEM

    DFLUX SUBROUTINE

    Just for the record: Problems in compilation are usually written in the .log-file. On topic: You could add something like "write(6,*) FLUX(1)" to your subroutine. By doing that, the value of FLUX(1) for each increment will be written into the .dat-file. If the values there are zero, you know...

Part and Inventory Search