Files
FemLite/todo.md
T
2026-06-26 00:48:57 +08:00

10 KiB

FemLite V5 Remaining TODO

Status date: 2026-06-26

This file is the executable TODO list for the current 0.5.x development cycle. The phase status table is maintained only in docs/v5_development_plan.md.

Rules for closing an item:

  • Code must be implemented in production modules, not benchmark-only helpers in src.
  • Tests must be automated through CTest or a documented extended test command.
  • Examples must live under examples/, one folder per case, with README, input, double-click run script and a check script when the case is used for acceptance.
  • Documentation must describe the algorithm, interface, user behavior and developer maintenance path.
  • Large generated result files must not be committed.

V5.2 External Sparse Solver Backend

TODO V5.2-1: Add one real third-party backend

  • Target: SuperLU first, MUMPS or MKL Pardiso acceptable if easier on the current machine.
  • Implementation:
    • Add CMake option and detection for the selected backend.
    • Add a backend adapter module under src/solver.
    • Convert FemLite CSR metadata to the backend indexing and storage expected by the library.
    • Route LSOLVER_EXTERNAL to the backend without silent fallback.
  • Tests:
    • Add unavailable-path CTest when the library is not found.
    • Add enabled-backend CTest for a SPD matrix and a nonsymmetric matrix.
    • Add at least one static structural solve using the backend.
  • Acceptance:
    • linear_solver_get_external_info and C ABI report backend available.
    • Residual norm satisfies the same tolerance policy as internal solvers.
    • Failure returns explicit error/status, not a fallback solve.

TODO V5.2-2: Exercise external backend in structural workflows

  • Implementation:
    • Use the backend from linear static, implicit Newmark and one contact or nonlinear correction workflow.
    • Record backend name, residual and status in diagnostics.
  • Tests:
    • Add CTest labels or an extended test command for backend-enabled builds.
    • Keep default builds working without the third-party library.
  • Acceptance:
    • Static, implicit and contact/nonlinear cases complete with LSOLVER_EXTERNAL.
    • Documentation lists how to configure and run the backend build.

V5.3 Mortar / Augmented Lagrangian Contact

TODO V5.3-1: Promote two-block contact to nonmatching mortar benchmark

  • Implementation:
    • Create or update examples/contact_two_blocks_compression with nonmatching slave/master meshes.
    • Use mortar AL multiplier convergence diagnostics.
    • Output pressure profile, max gap, weighted gap and multiplier residual.
  • Tests:
    • Add check script for pressure distribution, max penetration and AL iteration convergence.
    • Add CTest smoke/regression entry that runs the check script.
  • Acceptance:
    • Pressure distribution error is within a documented tolerance.
    • AL iteration converges within the configured maximum iterations.
    • Example README documents reference metrics and limitations.

TODO V5.3-2: Promote sliding contact to large-sliding mortar-friction benchmark

  • Implementation:
    • Extend examples/contact_block_sliding or create a new dedicated folder for large sliding with mortar friction.
    • Couple normal multiplier history and tangential stick/slip history.
    • Include restart write/read across the sliding path.
  • Tests:
    • Check tangential reaction, slip accumulation, friction work and restart continuity.
    • Compare OpenMP 1-thread and multi-thread non-timing statistics.
  • Acceptance:
    • Stick/slip transitions are reported.
    • Frictional work is nonnegative within tolerance.
    • Restart continues multiplier and friction history without jumps.

TODO V5.3-3: Add shell/solid contact benchmark coverage

  • Implementation:
    • Add shell-solid and shell-shell contact examples or upgrade existing ones.
    • Use existing mortar force/tangent modules rather than a special-case path.
  • Tests:
    • Check contact pressure, gap, reaction balance and energy consistency.
  • Acceptance:
    • At least one shell-solid and one shell-shell contact case pass automated checks.

V5.4 Mohr-Coulomb And Strength Reduction

TODO V5.4-1: Finish material-point acceptance tests

  • Implementation:
    • Cover triaxial compression, triaxial extension, pure shear and tensile cutoff.
    • Record active branch or return-map mode for each test.
  • Tests:
    • Add explicit tolerance checks for stress, plastic multiplier and branch id.
  • Acceptance:
    • All material-point tests pass without substep explosion.
    • Tangent or algorithmic stiffness limitations are documented.

TODO V5.4-2: Replace strengthReduction placeholder with MC benchmark

  • Implementation:
    • Update examples/strengthReduction to use real Mohr-Coulomb material input.
    • Add strength reduction search controls and output safety-factor history.
    • Output plastic zone and displacement control probe.
  • Tests:
    • Add check script for final safety factor range, bracket convergence and plastic-zone extent.
  • Acceptance:
    • Safety factor lies inside documented tolerance.
    • Check script fails if the solve only runs linear elastic behavior.

V5.5 Linear Buckling And Cyclic Symmetry

TODO V5.5-1: Add analytic buckling verification

  • Implementation:
    • Add a small column or beam benchmark with known Euler critical load.
    • Assemble prestress/geometric stiffness through the production path.
  • Tests:
    • Check first eigenvalue relative error.
  • Acceptance:
    • Relative error and mode normalization are documented.

TODO V5.5-2: Upgrade corrugated shell benchmark

  • Implementation:
    • Replace static-only smoke with buckling eigenvalue analysis.
    • Add cyclic sector model and full-model comparison when feasible.
    • Write mode shape output through modal output path.
  • Tests:
    • Check critical load range and cyclic/full consistency.
  • Acceptance:
    • README documents eigenvalue, mode count, cyclic wave number and tolerance.

V5.6 High-Fidelity Roll Forming

TODO V5.6-1: Add real roller kinematics to contact workflow

  • Implementation:
    • Ensure rigid roller rotation contributes to relative tangential velocity.
    • Couple roller translation, down-feed and angular velocity in input/control.
    • Output roller force, torque, contact pressure band and friction work.
  • Tests:
    • Unit test roller kinematics and relative velocity sign.
    • Example check for nonzero rolling traction and stable energy trend.
  • Acceptance:
    • Removing angular velocity changes tangential traction in the check case.

TODO V5.6-2: Add plastic forming and springback benchmark

  • Implementation:
    • Upgrade examples/roll_forming to include plastic workpiece and unloading.
    • Output residual displacement, plastic zone and springback metric.
  • Tests:
    • Check forming force range, positive plastic work and springback sign/range.
  • Acceptance:
    • Example is no longer only an elastic contact surrogate.

V5.7 Cohesive Adhesion / Decohesion

TODO V5.7-1: Add cohesive single-point acceptance tests

  • Implementation:
    • Cover loading, unloading, mixed-mode damage and complete decohesion.
    • Track damage, maximum opening, energy and status.
  • Tests:
    • Verify nonnegative dissipated energy and irreversible damage.
  • Acceptance:
    • Restarted state preserves damage and maximum opening.

TODO V5.7-2: Upgrade ball adhesion/decohesion example

  • Implementation:
    • Use cohesive law/state in examples/ball_adhesion_decohesion.
    • Output force-displacement curve, cohesive energy and decohesion area.
  • Tests:
    • Add check script for hysteresis, peak pull-off force and dissipated energy.
  • Acceptance:
    • Example fails if cohesive damage is not activated.

V5.8 Particle / Flexible Container Coupling

TODO V5.8-1: Complete particle acceptance primitives

  • Implementation:
    • Cover particle free fall, wall collision, particle-particle pile and particle-facet coupling with production modules.
    • Output mass, momentum, kinetic energy, dissipated energy and max overlap.
  • Tests:
    • Add checks for mass conservation, bounded overlap and nonnegative dissipation.
  • Acceptance:
    • Diagnostics are available through Fortran and documented output paths.

TODO V5.8-2: Upgrade dynamic grain container example

  • Implementation:
    • Replace pressure surrogate with real particles and flexible container two-way force mapping.
    • Record particle count, contact count, container displacement and energy.
  • Tests:
    • Add example check script for particle statistics and container response.
  • Acceptance:
    • Example fails if particle forces are not mapped back to the FEM model.

V5.9 Benchmark, Performance And Documentation

TODO V5.9-1: Build V5 benchmark matrix

  • Implementation:
    • Add a table mapping every V5 completed capability to an example directory, test name, reference metric and tolerance.
    • Keep smoke and benchmark tiers separate.
  • Tests:
    • Default CTest remains fast.
    • Extended benchmark command runs the V5 acceptance checks.
  • Acceptance:
    • No completed V5 capability relies only on a smoke test.

TODO V5.9-2: Refresh documentation after each capability closes

  • Implementation:
    • Update requirements, architecture, detailed design, algorithms, interface, test plan, user manual and developer manual only with factual implementation details.
    • Keep status markers only in docs/v5_development_plan.md.
  • Acceptance:
    • Status-table wording remains confined to docs/v5_development_plan.md.

V5.10 Acceptance And Release

TODO V5.10-1: Create V5 acceptance report

  • Implementation:
    • Add docs/v5_acceptance_report.md.
    • Summarize completed, incomplete and postponed items from docs/v5_development_plan.md.
    • Include exact test commands, environment and results.
  • Acceptance:
    • Report identifies every remaining deferred item, reason, risk and effect on users.

TODO V5.10-2: Final release hygiene

  • Implementation:
    • Ensure worktree is clean except intended release files.
    • Clean generated root result files.
    • Run default CTest and any enabled extended backend/benchmark tests.
  • Acceptance:
    • Release branch or main merge has reproducible test output.
    • README and version metadata match the release state.