FemLite
FemLite is a lightweight finite element solver with a Fortran core. It is used for structural dynamics, static and nonlinear analysis, shell/solid elements, contact, material nonlinearity and compact engineering benchmark development.
Current project version: 0.6.2.
v0.5.0 remains the fifth-version acceptance checkpoint. The 0.6.x line builds
on that baseline with nonlinear lifecycle diagnostics, restart diagnostics,
contact/solver/path output hardening and release stability checks. Version
0.6.2 is a stability release: it does not add new user-facing algorithms or
broaden the 0.6.1 feature boundary.
Current Baseline
FemLite currently includes:
- Explicit dynamics, linear static, nonlinear static and implicit Newmark paths.
- C3D4/C3D8/C3D10/C3D20 solid elements and S3/S4/S6/S8 shell elements.
- Elastic, J2/J2_JC and Mohr-Coulomb material paths with compact regression coverage.
- Internal CG, BiCGSTAB, GMRES and dense pivoting linear solvers with diagnostics and preconditioner options.
- Contact-pair, analytical-plane, mortar/AL, friction, cohesive and particle coupling diagnostic infrastructure used by the covered benchmarks.
- CSV, VTK, restart, Fortran API and C ABI output/query surfaces.
continuation_path.csv,nonlinear_lifecycle.csvand restart version 5 optional lifecycle diagnostics.
Deferred items remain explicit: complete industrial AL/mortar consistent tangents, generalized mixed-control continuation, cohesive contact mainline, DEM/FEM subcycling, complete shell preload/high-order geometric stiffness, nonzero harmonic cyclic solving and production roll-forming workflows are not claimed by 0.6.2.
Build
cmake -S . -B build-win-gcc-16 -G "MinGW Makefiles" -DCMAKE_BUILD_TYPE=Release
cmake --build build-win-gcc-16 --config Release
ctest --test-dir build-win-gcc-16 --output-on-failure
For the current local GCC build directory used during 0.6.x hardening:
cmake --build build-codex-gcc --parallel
ctest --test-dir build-codex-gcc --output-on-failure
Release Gate
The 0.6.2 stability release gate is:
cmake --build build-codex-gcc --parallel
ctest --test-dir build-codex-gcc -R "^source_size$" --output-on-failure
ctest --test-dir build-codex-gcc -R "^(nonlinear_lifecycle|solver_implicit|implicit_inp|restart|contact|contact_mortar_report|contact_multiplier_report|cohesive_contact|particle_acceptance|linear_solver_cg|c_api)$" --output-on-failure
ctest --test-dir build-codex-gcc -L v5_acceptance --output-on-failure
git diff --check
Documentation
- 0.6 development plan
- 0.6.1 development plan
- 0.6 benchmark matrix
- 0.6 acceptance report
- V5 benchmark matrix
- User manual
- Developer manual
- TODO
Development Rules
- Keep accepted V1-V5 behavior under regression.
- Prefer focused stability checks over broad solver rewrites in 0.6.2.
- Do not commit generated result files, large CSV/VTK outputs or temporary benchmark artifacts.
- New behavior should be paired with a small, repeatable test or checker.