What to expect
Model, problem, results
Section titled “Model, problem, results”An analysis in xfea has three parts, always in this order.
- The model is the structure: parts with their nodes and elements, materials, sections, supports, and the interfaces between parts. Nothing in it is written for a particular solver.
- The problem is what happens to the model: its steps, applied in order, each with its loads and the results it should keep. One model can have several problems.
- The results are read from the solver’s files into a results database and queried through field objects (displacements, reactions, stresses), the same whatever solver produced them.
model = Model(name="cantilever") # 1. the structureproblem = model.add_problem(Problem(name="tip_load")) # 2. what happens to itstep = problem.add_step(StaticStep(name="load"))disp = DisplacementFieldResults()step.add_field_outputs([disp])problem.analyse_and_extract(path="output") # solve, and read the resultsdisp.get_min_result("z") # 3. the answerThe first analysis fills this in, line by line.
Two ways to use it
Section titled “Two ways to use it”- Through your AI assistant. The MCP server,
xfea-mcp, gives the assistant tools to read the API reference, write and check a script, build the model and look at it, run the solver and show the results. You ask for a model; the assistant writes the Python below. - In Python. The scripts are plain Python: write them yourself, or read and change the ones your assistant wrote.
What runs where
Section titled “What runs where”- The model, the mesh, the solver and the results are on your machine.
- Turning a model into a solver’s input is done by xfea’s conversion service. It receives the model’s definition without its mesh, and returns how to write the input. You subscribe to the plugin for your solver on your account on app.xfea.ai: see What’s free, what needs an account.
One language for any solver has the full picture, and Solvers how to set it up.
What xfea checks, and what it does not
Section titled “What xfea checks, and what it does not”model.check()lists what a solver would get wrong without saying so. Every solve runs it and logs what it finds.- After a solve,
problem.solver_warningsholds what the solver warned about. - Every solve writes a run record (
run.json) and a report (report.html): the results you chose to keep, the convergence, the model’s make-up and the warnings. - xfea does not check units. Keep them consistent: see Basics.
How xfea’s results compare with known answers is on the Verification page.
Plugins
Section titled “Plugins”- Solvers: Translate models into a solver’s input file. They are xfea’s own: you subscribe to the ones for your solvers, and they run on xfea’s service (on your own server by agreement). See What’s free, what needs an account.
- Meshers: Turn a part’s geometry (lines, surfaces, STEP solids) into nodes and elements. Gmsh ships with xfea.
- Databases: Store the results and answer queries on them. SQLite ships with xfea.
- Viewers: Show models and results. A browser viewer and a ParaView launcher ship with xfea.
© 2026 Francesco Ranaudo · Text and pictures CC BY 4.0 · Code Elastic License 2.0 · how to reuse them