# contact_two_blocks_compression V5.3 nonmatching face-to-face mortar contact benchmark for two C3D8 elastic blocks. Purpose: - Exercise nonmatching slave/master face contact with explicit face labels. - Exercise contact property inheritance through `*SURFACE INTERACTION`. - Exercise active-set, mortar-weighted gap and augmented-penalty multiplier diagnostics. - Provide the compact two-body pressure-profile benchmark used by CTest. Model: - Lower block: 0.10 m x 0.10 m x 0.05 m, split into four C3D8 elements on the contact face. - Upper block: 0.10 m x 0.10 m x 0.05 m, one C3D8 element on the contact face. - The upper block starts with 0.001 m initial penetration into the lower top face so contact is active immediately after the first force evaluation. - Lower bottom face is fixed in z; all nodes are fixed in x/y. - Upper top face is prescribed downward by 0.004 m over 1.0E-3 s. - Contact property: penalty = 1.0E7, damping = 1.0E2, augment = 0.20. Run from the repository root: Double-click `run_case.bat` in this directory, or run manually: ```powershell New-Item -ItemType Directory -Force examples\contact_two_blocks_compression\results | Out-Null build-win-gcc-16\femlite.exe examples\contact_two_blocks_compression\two_blocks_compression.inp --output-dir examples\contact_two_blocks_compression\results --output-interval 10 --run ``` Check: ```powershell .\Python\.venv\Scripts\python.exe examples\contact_two_blocks_compression\check_contact_results.py examples\contact_two_blocks_compression\results ``` The checker verifies active contact, at least four contributing master facets, positive augmented multiplier history, bounded contact pressure, bounded mortar-weighted penetration and VTK output. It also writes `pressure_profile.csv` in the result directory with one row per contact output sample. 0.5.3 diagnostic checks also consume contact state/status fields, activation and release counts, active-set flip count, augmentation factor/lambda, failed projection count, mean gap and L2 gap. The numerical checks emphasize existence, sign, boundedness and internal consistency rather than exact large-path nonlinear matching. The double-click script writes repeatable output to `results\auto_run`.