Cross-vendor interop
====================

You arrived at femorph-solver from somewhere else.  Maybe MAPDL,
maybe NASTRAN, maybe Abaqus, maybe LS-DYNA — three decades of FEA
practice has left every shop with its own dialect of "an
8-node solid element" or "a clamped boundary condition".  This
chapter is the migration bridge.

Two complementary paths:

* **Reading foreign decks.**  femorph-solver ingests MAPDL CDB
  decks, NASTRAN BDF, Abaqus INP, and Altair OptiStruct FEM
  through dedicated readers.  Pages
  :doc:`/getting-started/mapdl-interop` and
  :doc:`/user-guide/mapdl-compatibility` are the deep dives on
  the MAPDL format; the BDF / INP / FEM readers follow the same
  pattern.
* **Translating terminology.**  Most "I just learned a different
  word for the same idea" friction goes away once you have a
  Rosetta table.  :doc:`terminology` is exactly that — every
  concept, every vendor's name for it, in one place.

The cross-vendor :doc:`terminology` table is unique to
femorph-solver: no commercial-FEA vendor ships an
authoritative Rosetta because their proprietary boundaries
make it impossible.  We're agnostic; the table is part of the
public docs.

.. toctree::
    :maxdepth: 1

    terminology
    mapdl
    nastran
    abaqus
    lsdyna